SwiftSoft Labs

TrueVehicle Record of Processing Activities

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

Record of Processing Activities

1. Who this document is from

This document is from SwiftSoft Labs LLC ("we", "us"). A record of the processing the plan names. It is not a completed register under any statute.

Jurisdiction: Wyoming, United States (us-wy)

2. What the plan records

Data categories:

  • 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
  • request bodies
  • request url path and query string

Processors:

  • Google Sign-In (Sign-in and identity), United States, transfer: Standard contractual clauses, agreement: https://business.safety.google/processorterms/
  • InsForge (Hosting and infrastructure), United States, transfer: Standard contractual clauses, agreement: https://insforge.dev/dpa
  • OpenRouter (Artificial intelligence), United States, transfer: Standard contractual clauses, agreement: https://openrouter.ai/data-processing-agreement
  • PostHog (Analytics), United States, transfer: Standard contractual clauses, agreement: https://posthog.com/dpa
  • Sentry (Monitoring and error reporting), United States, transfer: Standard contractual clauses, agreement: https://sentry.io/legal/dpa/
  • Vercel (Hosting and infrastructure), United States, transfer: Standard contractual clauses, agreement: https://vercel.com/legal/dpa

Merchant of record: Kelviq. It sells the service to buyers as an independent controller under its own terms, so it is not a processor or a subprocessor.

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.

Minimum age: 18

Sensitive data: Location of previous vehicle registrants (city, state and ZIP only)

Purposes: behavioral (Legitimate interests); operational (Contract)

No certification was recorded. A detected dependency is not proof that a control runs in production.

3. Activities in this record

InsForge Postgres and InsForge file storage, United States.

4. Changes and contact

Questions go to legal@swiftsoftlabs.com. Our address is 312 W 2nd St, PO Box 5309, Casper, WY 82601.

We may update this document. A change does not by itself mean a control was deployed.

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