SwiftSoft Labs

Redline Encryption and Key Management Policy

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

Encryption and Key Management Policy

1. Who this document is from

This document is from SwiftSoft Labs LLC ("we", "us"). What the plan records about protecting data with cryptography.

Jurisdiction: Wyoming, United States (us-wy)

2. What the plan records

Data categories:

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

Processors:

  • Apify (Hosting and infrastructure), United States, transfer: Standard contractual clauses, agreement: https://docs.apify.com/legal/data-processing-addendum
  • GitHub Sign-In (Sign-in and identity), United States, transfer: Standard contractual clauses, agreement: https://github.com/customer-terms/github-data-protection-agreement
  • 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, which deletes your data from our database. Billing and usage ledger records are kept with personal details removed, as tax and accounting law requires.

Minimum age: 18

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

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

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

3. Encryption the plan records

Stripe restricted keys and 2FA secrets are encrypted with AES-256-GCM. Passwords are hashed with bcrypt. Only Stripe restricted (read-only) keys are accepted.

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: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