SwiftSoft Labs

TrueVehicle Privacy Policy

Version 1.0.0, effective 20 November 2026. Signature verified with key synlex-1.

Privacy Policy

1. Who we are

SwiftSoft Labs LLC ("we", "us") decides how the personal data described in this policy is used.

  • Legal name: SwiftSoft Labs LLC
  • Legal form: Registered company (LLC, corporation or similar)
  • Jurisdiction: Wyoming, United States (us-wy)
  • Contact email: legal@swiftsoftlabs.com
  • Address: 312 W 2nd St, PO Box 5309, Casper, WY 82601
  • Data protection contact: legal@swiftsoftlabs.com

2. Whose data this covers

  • Account holders (buyers, dealers and adjusters)
  • People who use the enterprise enquiry form
  • Previous registrants of a vehicle (city, state and ZIP only)
  • Website visitors

3. The personal data we collect

We collect the following categories of personal data:

  • Account credentials (password hash, emailed verification and reset codes)
  • Account role, company and notification preferences
  • Billing customer ID, plan and report credits
  • DPPA permissible-use declarations (purpose, VIN, IP address)
  • Email address
  • Enterprise enquiry details (name, work email, company type, volume, message)
  • Error reports
  • Google account profile (email, name, picture, account ID)
  • Name
  • Previous registrants' city, state and ZIP (from vehicle history data)
  • Sign-in and security records (IP address, browser user agent)
  • Usage analytics (random session ID)
  • VINs and listing URLs you submit
  • Vehicle photos you upload (may show plates or people)
  • Vehicle reports and AI write-ups
  • ip address (through Sentry)
  • request bodies (through Sentry)
  • request url path and query string (through Sentry)

4. Sensitive personal data

We collect the following sensitive personal data:

  • Location of previous vehicle registrants (city, state and ZIP only)

We use it only for the purposes in this policy.

5. Children

Minimum age: 18

The service is for people who are 18 or older. We do not knowingly collect personal data from anyone younger.

If you believe a person younger than 18 has given us personal data, write to legal@swiftsoftlabs.com and we will delete it.

6. Why we use personal data

  • Understanding how the service is used (behavioral). Legal basis: Legitimate interests. Anonymous page-view counts on public pages (session storage only, no advertising cookies) and error tracking to keep the service working
  • Operating and providing the service (operational). Legal basis: Contract.

**Vehicle history and previous registrants.** A report on a VIN includes vehicle history from our data providers. That history can show the city, state and ZIP code where the vehicle was registered before. For each past registration we store only the city, state, ZIP code and dates, not names, street addresses or phone numbers. We use these locations only to build the report, to place them on the report's map and to estimate flood risk. We keep them by VIN, not by person, and refresh them when a new report runs on that VIN.

**Permissible use.** Before a full report, you choose your permissible purpose under the Driver's Privacy Protection Act (DPPA). We record that choice with your account, the VIN and your IP address, so we can show that each lookup had a permissible purpose.

**Photos.** Photos you upload are stored with your report and, if you ask for a photo check, sent to our AI provider. Photos may show license plates or people. Do not upload photos of people, and crop out plates you do not need.

7. Marketing email

We do not send marketing email.

8. Who we share personal data with

We use the service providers below. Each one processes personal data on our behalf and under a data processing agreement where one is listed. They may use the data only to provide their service to us.

Google Sign-In

  • Service: Sign-in and identity
  • Purpose: Sign in with Google
  • Data received: Google account email, name, picture and account ID
  • Location: United States
  • Data processing agreement: https://business.safety.google/processorterms/

InsForge

  • Service: Hosting and infrastructure
  • Purpose: Database, photo file storage, and sign-in and enquiry emails
  • Data received: Account data, VINs, reports, uploaded photos, DPPA and sign-in records with IP address, billing records, emails we send you
  • Location: United States
  • Data processing agreement: https://insforge.dev/dpa

OpenRouter

  • Service: Artificial intelligence
  • Purpose: AI gateway to Google Gemini 2.5 Flash and Flash-Lite for report write-ups and photo checks
  • Data received: Vehicle report data (VIN, vehicle, history, registration city, state and ZIP, market data) and up to 6 uploaded photos
  • Location: United States
  • Data processing agreement: https://openrouter.ai/data-processing-agreement

PostHog

  • Service: Analytics
  • Purpose: Anonymous page-view counts on public pages
  • Data received: Random session ID, page URL, IP address
  • Location: United States
  • Data processing agreement: https://posthog.com/dpa

Sentry

  • Service: Monitoring and error reporting
  • Purpose: Error and performance monitoring
  • Data received: ip address, request bodies, request url path and query string
  • Location: United States
  • Data processing agreement: https://sentry.io/legal/dpa/

Vercel

  • Service: Hosting and infrastructure
  • Purpose: Hosting and serving the web app
  • Data received: All request data, including IP address and browser details
  • Location: United States
  • Data processing agreement: https://vercel.com/legal/dpa

Purchases are made from Kelviq, which sells the service to you as merchant of record. The payment details you give at checkout go to Kelviq. It uses them as an independent controller, not on our behalf, under its own privacy policy.

Kelviq's privacy policy: https://www.kelviq.com/buyer-privacy/

**Independent services.** To build reports and show our pages, we also use the services below. They are not our processors. Each acts under its own privacy policy.

  • Vehicle data providers receive the VIN, and MarketCheck also the mileage and ZIP code of a listing: VINData (vehicle history and title records, https://www.vindata.com/privacy-policy), MarketCheck (market prices and listing history, https://www.marketcheck.com/privacy-policy) and MonroneyLabels (original build sheets, https://monroneylabels.com/pages/privacy).
  • US government services receive the VIN or a state code only: NHTSA (VIN decoding and recalls) and FEMA (disaster declarations for flood risk).
  • OpenStreetMap receives the city, state and ZIP of past registrations to place them on a map, and your browser loads its map tiles, which shares your IP address with it (https://osmfoundation.org/wiki/Privacy_Policy). Open-Elevation receives the map coordinates of those places to estimate flood risk (https://open-elevation.com).
  • Your browser loads an icon font from Google Fonts (https://policies.google.com/privacy) and some images from Unsplash (https://unsplash.com/privacy), Wikimedia (https://foundation.wikimedia.org/wiki/Policy:Privacy_policy) and SVG Repo (https://www.svgrepo.com/page/privacy-policy/). These receive your IP address and browser details.

9. Transfers outside your country

Some providers handle personal data outside the country where you live. Where the law requires a safeguard for that transfer, we rely on the mechanism listed here.

  • Google Sign-In: United States. Transfer mechanism: Standard contractual clauses.
  • InsForge: United States. Transfer mechanism: Standard contractual clauses.
  • OpenRouter: United States. Transfer mechanism: Standard contractual clauses.
  • PostHog: United States. Transfer mechanism: Standard contractual clauses.
  • Sentry: United States. Transfer mechanism: Standard contractual clauses.
  • Vercel: United States. Transfer mechanism: Standard contractual clauses.

The safeguards we rely on:

  • Standard contractual clauses: the standard contractual clauses approved by the European Commission.

10. Cookies and similar technologies

We set first-party cookies that keep you signed in and keep the service secure: `tv_access_token` (15 minutes) and `tv_refresh_token` (30 days), and, while you sign in with Google, `tv_oauth_state` and `tv_oauth_ctx` (10 minutes). All are HttpOnly.

Your browser's session storage keeps `tv_checkout_offer`, `tv_checkout_credit_baseline` and `tv_billing_checkout_activating` during checkout, and `ssl-marketing-distinct-id`, a random ID that PostHog (an analytics provider) uses to count page views on our public pages. Session storage is cleared when you close the tab.

We set no advertising cookies. PostHog and Sentry set no cookies. Our Cookie Policy lists them and explains how to change your choices.

11. How long we keep personal data

We keep personal data only for as long as it is needed for the purposes in section 6, or as the law requires. When it is no longer needed we delete it or make it anonymous.

Retention: Account data is kept until you delete your account in Settings. That removes your profile, reports, DPPA purpose records and sessions; billing and sign-in records are kept in anonymized form as tax and accounting law requires. To have uploaded photos removed from file storage, email legal@swiftsoftlabs.com. Vehicle history records are kept by VIN and refreshed on each new report.

12. Your rights

You can ask us to tell you what personal data we hold about you, to give you a copy, to correct it, and to delete it. Write to legal@swiftsoftlabs.com. We may need to confirm who you are before we act, and we answer within one month.

If you are in the European Economic Area, the United Kingdom or Switzerland, you also have the right to restrict our use of your data, to object to it (including use based on legitimate interests), to receive your data in a portable format, and to withdraw consent at any time without affecting earlier use. You can complain to the data protection authority where you live or work.

If you live in a US state with a privacy law, such as California, you have similar rights to know, correct and delete your data, and we will not treat you differently for using them. We do not sell personal data or share it for targeted advertising.

13. Security

We use technical and organisational measures that fit the risk to protect personal data against loss, misuse, and unauthorised access. These include controlling who can reach the data and limiting access to the people and providers who need it.

No system is completely secure. If a breach puts your rights at risk, we will tell you and the authorities where the law requires it.

14. Artificial intelligence providers

We use these artificial intelligence providers: OpenRouter, which routes requests to Google Gemini 2.5 Flash and Flash-Lite.

When you ask for an AI write-up, the service sends the vehicle report data (VIN, vehicle, history highlights, the registration city, state and ZIP, and market data). When you ask for a photo check, it also sends up to 6 of your uploaded photos. Your name and email are not sent. Do not upload photos of people.

No agreement was recorded that says these providers refrain from keeping that content.

SwiftSoft Labs does not use your content to train AI models. Our AI gateway, OpenRouter, does not store your prompts or responses or use them for training under its default settings. The model provider that answers a request handles it under its own policy and may keep it for a limited time to prevent abuse.

15. Changes to this policy

We may update this policy. When we make a material change we will update it here and, where the law requires, tell you.

16. Contact us

To use a right or ask a question, write to legal@swiftsoftlabs.com or to our data protection contact at legal@swiftsoftlabs.com.

Check these documents

Checking the signature in your browser…

Your browser computes the SHA-256 of each document on this page and compares it with the hash in the signed release manifest.

DigiCert, Inc. timestamped the manifest hash at Fri, 20 Nov 2026 19:00:34 GMT. Synlex checked the authority's signature, the hash, and its certificate chain to DigiCert Trusted Root G4, a root pinned in Synlex. To check the token yourself, download it from the footer and run:

openssl ts -verify -in release-v1.0.0.tsr -digest 2fb7efff1f37da25e4f68d598b3caa71022d2a5dac12740d63e9f384b2909bc1 -CAfile /etc/ssl/cert.pem
Check the signature yourself with OpenSSL 3

The JSON API publishes the signed manifest bytes and the signature; the keys file publishes synlex-1's public key and its window. Then check that the manifest's signedAt falls inside that window and that its document hashes match the documents.

curl -s 'https://synlex.swiftsoftlabs.com/api/public/v1/swiftsoftlabs/truevehicle?version=1.0.0' | jq -j .signature.manifest > manifest.json
curl -s 'https://synlex.swiftsoftlabs.com/api/public/v1/swiftsoftlabs/truevehicle?version=1.0.0' | jq -r .signature.value | base64 -d > manifest.sig
curl -s 'https://synlex.swiftsoftlabs.com/.well-known/synlex-keys.json' | jq -r '.keys[] | select(.id == "synlex-1") | .publicKey' | base64 -d > key.der
openssl pkeyutl -verify -pubin -keyform DER -inkey key.der -rawin -in manifest.json -sigfile manifest.sig