SwiftSoft Labs

ProtocolPad 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 usage counts
  • Account credentials (password hash, email codes, TOTP 2FA, passkeys)
  • Billing customer ID and subscription status
  • Email address
  • Google or GitHub account ID (sign-in)
  • Lab reports (PDF files, collection dates, marker results)
  • Name
  • Organization, team membership and invites
  • Patient name, date of birth and sex
  • Patient record access log
  • Practitioner profile (clinic, specialty, NPI number, certifications, bio)
  • Protocol drafts and versions (supplements, doses, timing, lifestyle, cautions)
  • Safety review and feedback events
  • Symptoms and constraints entered by practitioners
  • Usage analytics

Processors:

  • GitHub sign-in (Sign-in and identity), United States, transfer: Standard contractual clauses, agreement: https://github.com/customer-terms/github-data-protection-agreement
  • 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
  • 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: Clinical records belong to the clinic and are kept while its account is open. After a clinic closes its account, we delete them within 30 days of its written request to legal@swiftsoftlabs.com. Deleting your own account in Settings removes your personal details but keeps the clinic's records. Billing records are kept as tax and accounting law requires.

Minimum age: 18

Sensitive data: Health data (patient lab results, symptoms and supplement protocols)

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 or Google or GitHub, with optional TOTP or passkey 2FA. Clinic data is visible only to members of that clinic's organization.

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:12 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 1747d06fbe5d40a5c677914bf4e2d98c90e57f5790baf05fd117d9ef464473e7 -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/protocolpad?version=1.0.0' | jq -j .signature.manifest > manifest.json
curl -s 'https://synlex.vercel.app/api/public/v1/swiftsoftlabs/protocolpad?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