SwiftSoft Labs

Traverse Privacy Policy

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

This is an earlier version. Read the current version, 2.0.0.

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
  • Website visitors

3. The personal data we collect

We collect the following categories of personal data:

  • AI Director chat messages
  • Account activity log (sign-in, sign-up and password changes)
  • Account credentials (password hash, email codes, 2FA, passkeys)
  • Billing customer ID, plan and subscription status
  • Email address
  • Google account ID and profile picture (Google sign-in)
  • Name
  • Usage analytics
  • World sessions: title, directing prompt, staging choices, source file names
  • ip address (through Sentry)
  • request bodies (through Sentry)
  • request url path and query string (through Sentry)

4. Sensitive personal data

We do not ask for sensitive personal data, such as data about health, ethnic origin, political opinions, religion, sexual orientation, or biometric identity, and the service is not designed to collect it. Please do not send it to us.

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 the pricing page and the cockpit home page, and error tracking to keep the service working
  • Operating and providing the service (operational). Legal basis: Contract.

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 (OAuth)
  • Data received: Google account ID, email address, name, profile picture
  • Location: United States
  • Data processing agreement: https://business.safety.google/processorterms/

InsForge

  • Service: Hosting and infrastructure
  • Purpose: Database for accounts, world sessions and billing status; sends sign-up verification and password reset emails; AI gateway
  • Data received: Email address, name, account credentials, world sessions, AI Director messages, billing status
  • Location: United States
  • Data processing agreement: https://insforge.dev/dpa

OpenRouter

  • Service: Artificial intelligence
  • Purpose: Routes AI Director requests to Google Gemini 2.5 Flash-Lite
  • Data received: Directing prompts, staging choices, source file names, session titles, AI Director chat messages
  • Location: United States
  • Data processing agreement: https://openrouter.ai/data-processing-agreement

PostHog

  • Service: Analytics
  • Purpose: Counts page views on the pricing page and the cockpit home page
  • Data received: Random session ID, page URL, IP address, browser details
  • Location: United States
  • Data processing agreement: https://posthog.com/dpa

Sentry

  • Service: Monitoring and error reporting
  • Purpose: Error and performance monitoring for the web app and its server routes
  • Data received: IP address, browser and device details, page URLs, error details
  • Location: United States
  • Data processing agreement: https://sentry.io/legal/dpa/

Vercel

  • Service: Hosting and infrastructure
  • Purpose: Hosts the web app and runs its server routes
  • Data received: IP address, browser details, request logs
  • 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/

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 four first-party cookies. They are HttpOnly, so scripts on the page cannot read them, and secure, so they travel only over HTTPS: `tv_access` keeps you signed in (15 minutes), `tv_refresh` renews your sign-in (30 days, or until you sign out), `tv_mfa_pending` holds a two-factor sign-in step (5 minutes), and `tv_oauth_state` protects sign-in with Google (10 minutes).

Your browser's session storage, which is cleared when you close the tab, keeps a random ID that PostHog uses to count page views on public pages, such as the pricing page, and on the cockpit home page (`ssl-marketing-distinct-id`). It also keeps three flags that track an open checkout (`ow_checkout_open`, `ow_checkout_needs_abandon`, `ow_checkout_activating`).

PostHog sets no cookies, Sentry error reports use no cookies, and we set no advertising cookies. Our Cookie Policy has the details.

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 and world sessions are kept until your account is deleted. The app has no delete button yet: email legal@swiftsoftlabs.com to ask, and we answer within one month. Email verification and password reset codes expire after 15 minutes. Billing records are kept as tax and accounting law requires.

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 AI Director requests to Google Gemini 2.5 Flash-Lite. We reach them through the InsForge AI gateway.

When you ask the AI Director to plan a scene, write a scene brief or answer in chat, your directing prompt, workspace mode, engine, staging style, environment, source file names, session title and chat messages (with recent chat history) are passed to the provider so that it can return a result. Do not put personal data into these fields unless you need to.

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 12:08:54 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 1399fa2e3869874dcaba684deae345c395316027fbf55051d2c43974d0932d20 -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.vercel.app/api/public/v1/swiftsoftlabs/traverse?version=1.0.0' | jq -j .signature.manifest > manifest.json
curl -s 'https://synlex.vercel.app/api/public/v1/swiftsoftlabs/traverse?version=1.0.0' | jq -r .signature.value | base64 -d > manifest.sig
curl -s 'https://synlex.vercel.app/.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