SwiftSoft Labs

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

  • 1099 forms and e-file records
  • Account credentials (password, 2FA, passkeys)
  • Anonymous page views on public pages
  • Bank accounts and bank transactions (through Plaid)
  • Billing customer ID, plan and status
  • Business profile and onboarding answers
  • Collectives, split rules, ledger entries and payout records
  • Connected platform OAuth tokens
  • Contractor names, emails and W-9 status
  • Email address
  • Expenses, deductions and AI category suggestions
  • Google account ID (Google sign-in)
  • Income records from connected YouTube, Twitch, Patreon and Stripe accounts
  • Name
  • Support form messages
  • W-9 details: legal name, tax ID, address, typed signature, IP and browser
  • ip address
  • request bodies
  • request url path and query string

Processors:

  • 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: Kept until you delete your account in Settings, which deletes the account and its records (income, expenses, bank data, contractors, W-9 and 1099 records, payouts) from our database at once. W-9 and 1099 files in file storage are not yet removed automatically; ask us and we delete them within 30 days. Billing records are kept with your email replaced, as tax law requires.

Minimum age: 18

Sensitive data: Financial records: bank transactions, income and expenses (no payment cards), Government tax IDs (SSN, ITIN or EIN) on W-9 forms

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

Tax IDs and W-9 details, connected platform tokens, bank access tokens and 2FA secrets are encrypted with AES-256-GCM. Passwords are hashed with bcrypt.

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:02:48 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 394415099c09d19485ce150be9421d6eb3f0b0b4d3fdef94bbe73a2dff81cb5f -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/tenpay?version=1.0.0' | jq -j .signature.manifest > manifest.json
curl -s 'https://synlex.vercel.app/api/public/v1/swiftsoftlabs/tenpay?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