SwiftSoft Labs

CreditClock 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 coaching results and run logs
  • Account credentials (password, 2FA, passkeys)
  • Account holder identity from your bank (Plaid, Premium)
  • Billing customer ID and subscription status
  • Credit goals: target score and closing date
  • Credit scores and utilization
  • Disputes and notes
  • Email address
  • Google account ID and profile picture (Google sign-in)
  • ID verification status and Sumsub applicant ID (Premium)
  • Linked bank and card accounts, balances and limits (Plaid)
  • Monthly income and debts (DTI calculator)
  • Name
  • Notification settings and email delivery logs
  • Partner branding (name, logo, colour, support email)
  • Payment calendar and reminders
  • Referral code and the partner who referred you
  • Sign-in and audit logs (IP address, browser, login country)
  • Transactions: merchant, amount, date and category (Plaid)
  • Usage analytics (anonymous, public pages)
  • ip address
  • request bodies
  • request url path and query string

Processors:

  • AWS KMS (Hosting and infrastructure), United States, transfer: Standard contractual clauses, agreement: https://d1.awsstatic.com/legal/aws-gdpr/AWS_GDPR_DPA.pdf
  • 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/
  • Sumsub (Sign-in and identity), Germany, transfer: Standard contractual clauses, agreement: https://sumsub.com/files/data_processing_agreement.pdf
  • 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: While your account is active. Deleting your account in Settings erases it from our database; backups may keep it for up to 30 days. Copies held by our providers follow each provider's policy.

Minimum age: 18

Sensitive data: Credit information, Financial account data, Government ID and selfie (processed by Sumsub)

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

Plaid access tokens are encrypted with AES-256-GCM, with data keys wrapped by AWS KMS when it is configured. Passwords and 2FA backup codes 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 12:15:08 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 2e91af38e661dda6922fe11131d97698ec7235e8f0127e6b8f16079dcd8e4981 -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/creditclock?version=1.0.0' | jq -j .signature.manifest > manifest.json
curl -s 'https://synlex.vercel.app/api/public/v1/swiftsoftlabs/creditclock?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