LambdaWorx
// LEGAL
// PRIVACY POLICY

Privacy Policy

Last Updated: May 2026
// NOTICE — TEMPLATE LANGUAGE

This document is template language drafted by LambdaWorx and has not yet undergone licensed legal review. It is provided for informational purposes only and does not constitute legal advice. Final review by qualified counsel is pending before commercial launch. [TODO: counsel review]

LambdaWorx LLC is the parent company behind a small set of vertical software products — currently TuneView (automotive tuning), with MarineView and AgriView planned. This policy covers the LambdaWorx corporate site at lambdaworx.io and the kinds of conversations a holding company has with the outside world: prospects, partners, recruits, investors, journalists, vendors.

It does not cover data you give us inside a product. Each product runs on its own policy:

  • TuneView — see tuneview.io/privacy for anything you submit through the TuneView app, including datalogs, vehicle metadata, and account information.
  • MarineView / AgriView — separate policies will publish with each product.

If you're not sure which policy applies: product data → product policy; everything else → this one.

// 01

What We Collect on lambdaworx.io

We try to collect as little as we can get away with. Specifically:

  • Things you type into a form. If you fill in a contact form, request a demo, apply for a job, or send an investor inquiry, we get whatever you typed: usually a name, an email, a company, and a short note. We use it to write you back.
  • Things your browser sends. When you load a page, our hosting provider sees standard request metadata — IP address, user-agent string, referring URL, timestamp. We use it for security (rate-limiting, abuse detection) and basic operational logs.
  • Things analytics sees. Coarse traffic data — pages viewed, country-level location derived from IP, session counts. We do not collect names or identifiers from analytics. We do not run cross-site advertising trackers.
  • Cookies.Minimum cookies needed to make the site work (e.g., to remember a theme preference). No advertising cookies. If we add analytics that drops a cookie, we'll say so on this page and on a cookie banner.

We do not collect: sensitive categories of personal data (health, biometric, government ID, financial account numbers), data about minors, or precise location.

// 02

How We Use It

  • To reply. A contact-form submission is a request to talk. We use it to talk back, and to keep track of the conversation across email threads.
  • To run the site. Logs and security signals are used to keep the site up and keep bad actors off it.
  • To improve.Aggregate analytics tells us which pages are read and which aren't.
  • For recruiting. If you apply for a role, we use your application to evaluate you for that role and, with your consent, for future related roles.

We do not sell personal data. We do not share it with advertisers. We do not use corporate-site data to train AI models — product data inside TuneView is governed separately by the TuneView policy and terms.

// 03

How Long We Keep It

Data TypeRetention
Contact-form and inquiry dataActive conversation + up to 24 months archived; deleted on request or schedule
Logs and security data30–90 days; longer for active security investigations
Recruiting dataDuration of open role + up to 12 months for related future roles
AnalyticsAggregate; typically 14 months max
// 04

Who Else Touches It (Subprocessors)

We use a small set of vendors to run the site. They see only what they need to do their job:

SubprocessorPurpose
VercelHosting and edge infrastructure for lambdaworx.io
Vercel AnalyticsAggregate traffic analytics (privacy-respecting; no cross-site tracking)
Google WorkspaceBusiness email — replies and recruiting threads live here
Internal infrastructureForm submissions stored in our own systems; no SaaS CRM currently

Each subprocessor has its own privacy policy. We'll update this list when subprocessors change. If we adopt a SaaS form/CRM provider we'll name it here.

// 05

Your Rights

Wherever you live, we'll honor reasonable requests to:

  • See what we have about you
  • Correct it if it's wrong
  • Delete it
  • Opt out of any further contact
  • Take a copy in a portable format

If you're in a jurisdiction with a specific privacy regime — GDPR (EU/UK), CCPA/CPRA (California), PIPEDA (Canada), LGPD (Brazil), or similar — those rights apply in the way that law spells out, and we will act as data controller for the corporate-site data described above.

To exercise any of these, email info@lambdaworx.io. We aim to respond inside 30 days. A plain email is fine — no lawyer or form required.

// 06

Where the Data Lives

LambdaWorx is a U.S. company. The primary data location is the United States. Our subprocessors may process data in other regions (Vercel and Google operate globally). If you're in the EU/UK, transfers out of the EEA rely on the providers' Standard Contractual Clauses and equivalent safeguards.

// 07

Children

The corporate site is intended for a business audience. We don't direct it to children under 16 and we don't knowingly collect data from them. If you believe a child has submitted information through the site, email us and we'll delete it.

// 08

Security

We use reasonable administrative, technical, and physical safeguards — including encryption in transit, least-privilege access, and regular review of vendor security posture — to protect the data we collect. No system is perfect; if we ever have an incident that affects you, we'll tell you and the appropriate regulators in the time the applicable law requires.

// 09

Changes

We'll update this policy as the company changes. The Last Updated date at the top is the source of truth. Material changes get called out at the top of the page for at least 30 days.

// 10

Contact