SwiftSoft Labs

Redline 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 and their team members
  • People named in listings or business data that users analyse
  • Website visitors

3. The personal data we collect

We collect the following categories of personal data:

  • AI chat messages about an assessment
  • Account credentials (password, 2FA, passkeys)
  • Anonymous page views
  • Assessment notes and reports
  • Billing customer and subscription IDs
  • Business financial figures entered or read from your Stripe account
  • Code scan metadata (file paths, hashes, counts; never source code)
  • Email address
  • Google or GitHub account ID
  • Listing URLs and listing data scraped from Acquire.com or Flippa
  • Name
  • Organization membership, roles and invites
  • Stripe restricted API key (encrypted)
  • Usage counts and audit records
  • 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:

  • Business financial data (revenue and balance figures; no card or bank numbers)

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 analytics 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.

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.

Apify

  • Service: Hosting and infrastructure
  • Purpose: Fetching public listing pages from Acquire.com and Flippa, and Google Trends data
  • Data received: Listing URLs and search keywords
  • Location: United States
  • Data processing agreement: https://docs.apify.com/legal/data-processing-addendum

GitHub Sign-In

  • Service: Sign-in and identity
  • Purpose: Sign in with GitHub
  • Data received: Email address, GitHub username and account ID
  • Location: United States
  • Data processing agreement: https://github.com/customer-terms/github-data-protection-agreement

Google Sign-In

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

InsForge

  • Service: Hosting and infrastructure
  • Purpose: Database, file storage and sending account emails (codes and invites)
  • Data received: Account, organization, assessment, chat, billing ID and encrypted key data; email addresses for account emails
  • Location: United States
  • Data processing agreement: https://insforge.dev/dpa

OpenRouter

  • Service: Artificial intelligence
  • Purpose: AI gateway to Google Gemini models for risk analysis, financial summaries and chat
  • Data received: Listing URLs and listing data, financial figures, code scan metadata, chat messages
  • Location: United States
  • Data processing agreement: https://openrouter.ai/data-processing-agreement

PostHog

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

Sentry

  • Service: Monitoring and error reporting
  • Purpose: Error 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 the website and app
  • Data received: Request data and logs (IP address, browser details, pages requested)
  • 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/

**Your own Stripe account.** If you connect your Stripe account, we use the restricted key you give us to read your balance, account and active subscription data from Stripe. Stripe is your provider, not ours: it acts under your agreement with it and its own privacy policy (https://stripe.com/privacy). We send Stripe nothing except those read requests.

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.

  • Apify: United States. Transfer mechanism: Standard contractual clauses.
  • GitHub Sign-In: United States. Transfer mechanism: Standard contractual clauses.
  • 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

Redline sets secure, HttpOnly cookies on its own domain to keep you signed in, to remember the organization you are working in, and to protect sign-in with Google, GitHub or two-factor authentication. Your browser also keeps a few values in local and session storage, such as the assessment you last opened and the state of a checkout.

We do not set analytics or advertising cookies. PostHog (analytics) counts page views on our public pages using a random ID kept in your browser's session storage, which is cleared when you close the tab. Sentry error reports use no cookies.

Our Cookie Policy lists each cookie and storage item 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, which deletes your data from our database. Billing and usage ledger records are kept with personal details removed, 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 requests to Google Gemini models (Gemini 2.5 Flash by default, and Gemini 2.5 Flash-Lite on the Basic plan).

When you run an analysis, ask for a report or use the assessment chat, the listing URL and listing data, financial figures (including figures read from your Stripe account), code scan metadata and your chat messages are passed to the provider so that it can return a result. Source code from the Redline CLI is never sent; only file paths, hashes and counts. Do not put personal data into such a feature 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 19:00:31 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 da0201dca28c7f2d353b78a00b4176fc5b9e68de8584df4927767d2e1acd7a3c -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/redline?version=1.0.0' | jq -j .signature.manifest > manifest.json
curl -s 'https://synlex.vercel.app/api/public/v1/swiftsoftlabs/redline?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