SwiftSoft Labs

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

  • Account credentials (password hash, verification codes, sign-in sessions)
  • Cover and line-skip passes
  • Crash reports and performance traces
  • Date of birth and age and identity verification result (from Sumsub)
  • Email address
  • Google or Apple account ID and email (social sign-in)
  • Government ID document photos (taken and kept by Sumsub)
  • Menu item photos uploaded by venues
  • Merchant Portal venue and staff details (staff names, hashed PINs, POS tokens)
  • Name and display name
  • Precise location (GPS) while the app is open, to find nearby venues
  • Purchase history: drink orders (items, prices, tip, fees, venue, pickup code)
  • Purchase records (Kelviq customer ID, plan, subscription status, refunds)
  • Selfie face scan for the liveness check (taken and kept by Sumsub)
  • Sign-in history and account security log

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
  • 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: Kept while your account is open. Deleting your account removes your account, verification record, sign-in methods and cover passes; orders are kept without the link to you, and billing records as tax law requires. Codes expire after 15 minutes. Sumsub holds the ID photos and selfie under our agreement with it; to have them deleted, write to legal@swiftsoftlabs.com.

Minimum age: 21

Sensitive data: Biometric data (selfie and face liveness check, processed by Sumsub), Government ID (ID document checked by Sumsub), Precise location (GPS, used while the app is open)

Purposes: operational (Contract)

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

3. Encryption the plan records

Data is sent over HTTPS. Passwords and staff PINs are hashed with bcrypt, refresh tokens are stored as SHA-256 hashes, and sign-in tokens are kept in the device's secure storage (SecureStore) where the device supports it.

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 15:02:36 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 39261a297363948792c31c664dddb263ffff5f1b485605c8d407d9d0a839148b -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.swiftsoftlabs.com/api/public/v1/swiftsoftlabs/sidedoor?version=1.0.0' | jq -j .signature.manifest > manifest.json
curl -s 'https://synlex.swiftsoftlabs.com/api/public/v1/swiftsoftlabs/sidedoor?version=1.0.0' | jq -r .signature.value | base64 -d > manifest.sig
curl -s 'https://synlex.swiftsoftlabs.com/.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