SwiftSoft Labs

Broadbeam 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 prompts and generated text, images and video
  • Account credentials (password hash, email verification codes)
  • Affiliate partner profiles, referrals, commissions and payout records
  • Attribution visitor ID, channel, campaign and conversions
  • Audit log of workspace actions
  • Billing plan and Kelviq customer reference
  • Brand kit assets
  • Connected social account IDs, handles, profile names and pictures
  • Customers' email contacts: email, name, tags and consent record
  • Email send and delivery events
  • Error reports
  • Google or GitHub account ID, name and picture (sign-in)
  • IP address and browser details in technical logs
  • Marketing page views (random session ID, page URL, country)
  • Name and email address
  • Organization, project, workspace and role
  • Permissions granted to connected social accounts
  • Posts, drafts, schedules, media and publishing results
  • Social account access tokens and app passwords (encrypted)
  • Unsubscribe and bounce status of email contacts

Processors:

  • Amazon Web Services (SES) (Email and messaging), United States, transfer: Standard contractual clauses, agreement: https://d1.awsstatic.com/legal/aws-dpa/aws-dpa.pdf
  • GitHub Sign-In (Sign-in and identity), United States, transfer: Standard contractual clauses, agreement: https://github.com/customer-terms
  • 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
  • Resend (Email and messaging), United States, transfer: Standard contractual clauses, agreement: https://resend.com/legal/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 and content data: while the account is active; deleting it in Settings > Account removes your data and login. Social tokens: deleted on disconnect or revocation. Email contacts: until the organization deletes them; unsubscribed and bounced addresses stay suppressed. bb_vid cookie: 60 days. Billing and payout records: as tax and accounting law requires.

Minimum age: 18

Sensitive data: Not recorded.

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

Social account access tokens and app passwords are encrypted with AES-256-GCM. Passwords are hashed by our sign-in provider, InsForge.

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