SwiftSoft Labs

Meridian International Data Transfer Documentation

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

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:

  • AI signal classifications and intent scores
  • Account credentials (password, 2FA, passkeys)
  • Billing customer ID
  • Email address
  • Google sign-in account identifier
  • Hiring-manager name, job title and work email (public job postings, Apollo)
  • Integration credentials (Slack, Apollo, HubSpot, Salesforce)
  • Job posting details (title, description, company, location)
  • Name
  • Rep feedback notes on signals
  • Usage analytics
  • ip address
  • request bodies
  • request url path and query string

Processors:

  • Apollo, United States, transfer: Standard contractual clauses, agreement: https://www.apollo.io/dpa
  • Google (Gemini via OpenRouter) (Artificial intelligence), United States, transfer: Standard contractual clauses, agreement: https://business.safety.google/processorterms/
  • 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/
  • Twilio (Email and messaging), United States, transfer: Standard contractual clauses, agreement: https://www.twilio.com/en-us/legal/data-protection-addendum
  • 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 removes it from our database. Contact details of hiring managers collected from public job postings or returned by Apollo enrichment are kept until the person asks us to remove them at legal@swiftsoftlabs.com. Billing records are kept as tax and accounting law requires.

Minimum age: 18

Sensitive data: Not recorded.

Purposes: behavioral (Legitimate interests); operational (Contract for account holders; legitimate interests for sales intelligence)

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 11:28:05 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 e3ef6a21ff9c669d8668b370f11a4a59351f5021326f978cf0e656a2ecab7e3d -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/meridian?version=1.0.0' | jq -j .signature.manifest > manifest.json
curl -s 'https://synlex.vercel.app/api/public/v1/swiftsoftlabs/meridian?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