SwiftSoft Labs

Synlex International Data Transfer Documentation

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.

International Data Transfer Documentation

1. Who this document is from

This document is from SwiftSoft Labs LLC ("we", "us"). The provider locations and transfer mechanisms the plan names.

Jurisdiction: Wyoming, United States (us-wy)

2. What the plan records

Data categories:

  • Account credentials (password hash, authenticator secret, passkeys)
  • Billing details (plan, billing address, tax ID, PO number)
  • Consent records from customer websites (pseudonymous ID, choices, time)
  • Email address
  • GitHub App installation and repository details
  • Google or GitHub account ID (sign-in)
  • Name
  • Questionnaire answers and generated and signed documents
  • Repository files read during scans, and scan results
  • Security and audit log entries
  • Sign-in and session records (IP address, browser user agent)
  • Single sign-on and SCIM directory identities
  • Usage analytics
  • Workspace membership, roles and invitations
  • email and username
  • ip address
  • request bodies
  • request url path and query string
  • stack traces
  • url path
  • user agent
  • user id
  • user's ip address

Processors:

  • GitHub (Hosting and infrastructure), 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
  • Resend (Email and messaging), United States, transfer: Standard contractual clauses, agreement: https://resend.com/legal/dpa
  • Sentry (Monitoring and error reporting), United States, transfer: Standard contractual clauses, agreement: https://sentry.io/legal/dpa/
  • Vercel Inc. (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 and workspace data are kept while the workspace is active. An owner can delete a workspace in its Data settings; it is deleted for good 30 days later. To delete your personal account, write to legal@swiftsoftlabs.com; we delete it within 30 days. Consent records are kept for the period the customer sets (365 days by default). Billing records are kept as tax law requires.

Minimum age: 18

Sensitive data: Not recorded.

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

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

3. Transfers the plan names

Every provider named above has a transfer mechanism.

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 12:27:57 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 db50de992705c381c4c58c86ba1f71fdcded976c674f8a3ecf84b76a4dd3a91b -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/synlex?version=1.0.0' | jq -j .signature.manifest > manifest.json
curl -s 'https://synlex.vercel.app/api/public/v1/swiftsoftlabs/synlex?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