SwiftSoft Labs

Syndicate 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 review result for each submission (decision, confidence, rationale)
  • Account ID (member user ID)
  • Account credentials (bcrypt password hash, email and reset codes)
  • Crash and error diagnostics
  • Deal and salary submissions (brand, platform, deal value, agency fee, region)
  • Direct messages
  • Drop purchases, refunds and Kelviq customer ID
  • Email address
  • Google account ID, email and name (Sign in with Google)
  • Green Room and Parlor chat messages
  • Invitations (invite codes, invitee handles, who invited whom)
  • Member details (handle, bio, tier, follower band, invite and credit counts)
  • Moment likes and member follows
  • Name and display name
  • Screenshot strikes (member, channel, reason)
  • Sign-in audit log (action and time)
  • Social handles you type for Instagram, TikTok and YouTube
  • Waitlist application (handle, platform, follower count)

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/
  • 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 it at once. Deal and salary submissions stay in the Ledger without your name; a private log of which submissions your account made is not purged. Kelviq keeps order and payment records under its own terms. You can also ask by email to legal@swiftsoftlabs.com.

Minimum age: 18

Sensitive data: Financial data: creator deal values, agency fees and salary submissions

Purposes: operational (Contract, and legitimate interests in security and fraud prevention)

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

3. Access the plan records

Members sign in with email and password or with Google. The app keeps its session in the device's secure storage.

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 14:48:28 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 20004bbee732d12860a0caa6490d4eea3001d319f7f284e33aaf792d80910d1f -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/syndicate?version=1.0.0' | jq -j .signature.manifest > manifest.json
curl -s 'https://synlex.vercel.app/api/public/v1/swiftsoftlabs/syndicate?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