SwiftSoft Labs

Thumbloop Access Control and Identity Management Policy

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

Access Control and Identity Management Policy

1. Who this document is from

This document is from SwiftSoft Labs LLC ("we", "us"). What the plan records about who can reach personal data.

Jurisdiction: Wyoming, United States (us-wy)

2. What the plan records

Data categories:

  • AI scores, headlines and experiment results
  • Account credentials (bcrypt password hash, email verification and reset codes)
  • Agency plan: your own Google OAuth client ID and encrypted client secret
  • Anchor Face photo (a face likeness you upload)
  • Anonymous page views
  • Billing customer ID, plan and subscription status
  • Connected YouTube channel, video titles and analytics (CTR, impressions, views)
  • Email address
  • Image credit usage
  • Name and profile picture (from Google sign-in)
  • Sign-in sessions and security logs (including IP address for rate limiting)
  • Uploaded images, generated thumbnails and prompts
  • YouTube OAuth tokens (encrypted)
  • ip address
  • request bodies
  • request url path and query string

Processors:

  • Google Cloud Vision (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
  • 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: Account data is kept until you delete your account in Settings, which deletes your account records and your stored images. Unlinking a channel deletes its stored tokens and channel records. Sign-in security logs are kept while the account exists. Billing records are kept as tax and accounting law requires.

Minimum age: 18

Sensitive data: User-supplied photos and face likeness (no face templates or identification)

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

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

3. Access the plan records

Account holders sign in with email and password (email code verification) or Google.

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: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 96b0b51f63d5720515453924a80a0e1ebe6489eccb4888b9e612b14ed39c1545 -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/thumbloop?version=1.0.0' | jq -j .signature.manifest > manifest.json
curl -s 'https://synlex.swiftsoftlabs.com/api/public/v1/swiftsoftlabs/thumbloop?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