SwiftSoft Labs

ProtocolPad Privacy Policy

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

Privacy Policy

1. Who we are

SwiftSoft Labs LLC ("we", "us") decides how the personal data described in this policy is used.

  • Legal name: SwiftSoft Labs LLC
  • Legal form: Registered company (LLC, corporation or similar)
  • Jurisdiction: Wyoming, United States (us-wy)
  • Contact email: legal@swiftsoftlabs.com
  • Address: 312 W 2nd St, PO Box 5309, Casper, WY 82601
  • Data protection contact: legal@swiftsoftlabs.com

2. Whose data this covers

  • Account holders (practitioners and clinic staff)
  • Invited team members
  • Patients whose records a clinic enters
  • Website visitors

**Patients.** A clinic that uses ProtocolPad decides which patient data it enters and why. For that data the clinic is the controller, and SwiftSoft Labs processes it only on the clinic's instructions, to run the service for the clinic. If you are a patient, ask your clinic to see, correct or delete your records. If you write to us, we pass your request to the clinic and help it answer. A data processing agreement for clinics is available on request at legal@swiftsoftlabs.com.

3. The personal data we collect

We collect the following categories of personal data:

  • 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

4. Sensitive personal data

We collect the following sensitive personal data:

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

We use it only for the purposes in this policy.

Clinics enter this data about their patients. The app encrypts patient names, dates of birth and sex, uploaded lab files and protocol content before they are stored. ProtocolPad is not represented as HIPAA compliant, and SwiftSoft Labs does not sign business associate agreements.

5. Children

Minimum age: 18

The service is for people who are 18 or older. We do not knowingly collect personal data from anyone younger.

If you believe a person younger than 18 has given us personal data, write to legal@swiftsoftlabs.com and we will delete it.

6. Why we use personal data

  • Understanding how the service is used (behavioral). Legal basis: Legitimate interests. Anonymous page-view analytics on public marketing pages
  • Operating and providing the service (operational). Legal basis: Contract.

7. Marketing email

We do not send marketing email.

8. Who we share personal data with

We use the service providers below. Each one processes personal data on our behalf and under a data processing agreement where one is listed. They may use the data only to provide their service to us.

GitHub sign-in

  • Service: Sign-in and identity
  • Purpose: Sign in with GitHub (OAuth)
  • Data received: GitHub account ID, email, name, IP address, browser user agent
  • Location: United States
  • Data processing agreement: https://github.com/customer-terms/github-data-protection-agreement

Google Sign-In

  • Service: Sign-in and identity
  • Purpose: Sign in with Google (OAuth)
  • Data received: Google account ID, email, name, IP address, browser user agent
  • Location: United States
  • Data processing agreement: https://business.safety.google/processorterms/

InsForge

  • Service: Hosting and infrastructure
  • Purpose: Database, file storage for lab reports, and account emails (codes, password resets, team invites)
  • Data received: Account and profile data, encrypted patient fields, encrypted lab files and protocols, lab markers, access logs, email address
  • Location: United States
  • Data processing agreement: https://insforge.dev/dpa

OpenRouter

  • Service: Artificial intelligence
  • Purpose: AI gateway to Google Gemini 2.5 Flash-Lite for lab marker extraction and protocol drafts
  • Data received: Lab report text and page images (may show patient identifiers), marker summary, practitioner-typed symptoms and constraints
  • Location: United States
  • Data processing agreement: https://openrouter.ai/data-processing-agreement

PostHog

  • Service: Analytics
  • Purpose: Anonymous page-view analytics on public marketing pages
  • Data received: Random per-session ID, page URL, IP address, browser user agent
  • Location: United States
  • Data processing agreement: https://posthog.com/dpa

Vercel

  • Service: Hosting and infrastructure
  • Purpose: Hosting and content delivery for the website and app
  • Data received: All data sent to and from the service, IP address, browser user agent, cookies
  • Location: United States
  • Data processing agreement: https://vercel.com/legal/dpa

Purchases are made from Kelviq, which sells the service to you as merchant of record. The payment details you give at checkout go to Kelviq. It uses them as an independent controller, not on our behalf, under its own privacy policy.

Kelviq's privacy policy: https://www.kelviq.com/buyer-privacy/

**Independent services.** Some placeholder profile pictures in the signed-in app come from Lorem Picsum (https://picsum.photos/). Our image server fetches them, so Lorem Picsum receives the image address, which can contain a random record ID but no name or health data, and not your IP address. It is not our processor and acts under its own terms.

9. Transfers outside your country

Some providers handle personal data outside the country where you live. Where the law requires a safeguard for that transfer, we rely on the mechanism listed here.

  • GitHub sign-in: United States. Transfer mechanism: Standard contractual clauses.
  • Google Sign-In: United States. Transfer mechanism: Standard contractual clauses.
  • InsForge: United States. Transfer mechanism: Standard contractual clauses.
  • OpenRouter: United States. Transfer mechanism: Standard contractual clauses.
  • PostHog: United States. Transfer mechanism: Standard contractual clauses.
  • Vercel: United States. Transfer mechanism: Standard contractual clauses.

The safeguards we rely on:

  • Standard contractual clauses: the standard contractual clauses approved by the European Commission.

10. Cookies and similar technologies

The service uses cookies and similar technologies to run, to keep you signed in, and to keep the service secure.

We set these first-party cookies, all HttpOnly: `pp_access` keeps you signed in (15 minutes, renewed while you use the service), `pp_refresh` renews your session (30 days), `pp_mfa_pending` holds a two-factor sign-in in progress (5 minutes), and `pp_oauth_state` protects Google and GitHub sign-in (10 minutes).

During checkout we keep `protocolpad_checkout_open`, `protocolpad_checkout_needs_abandon` and `protocolpad_checkout_activating` in your browser's session storage.

Analytics provider PostHog counts page views on our public marketing pages with a random ID kept in your browser's session storage under `ssl-marketing-distinct-id`, which is cleared when you close the tab. It sets no cookies. We use no advertising cookies or pixels.

Our Cookie Policy lists them.

11. How long we keep personal data

We keep personal data only for as long as it is needed for the purposes in section 6, or as the law requires. When it is no longer needed we delete it or make it anonymous.

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.

12. Your rights

You can ask us to tell you what personal data we hold about you, to give you a copy, to correct it, and to delete it. Write to legal@swiftsoftlabs.com. We may need to confirm who you are before we act, and we answer within one month.

If you are a patient of a clinic that uses ProtocolPad, the clinic controls your records, so send your request to the clinic. If you write to us, we pass it to the clinic.

If you are in the European Economic Area, the United Kingdom or Switzerland, you also have the right to restrict our use of your data, to object to it (including use based on legitimate interests), to receive your data in a portable format, and to withdraw consent at any time without affecting earlier use. You can complain to the data protection authority where you live or work.

If you live in a US state with a privacy law, such as California, you have similar rights to know, correct and delete your data, and we will not treat you differently for using them. We do not sell personal data or share it for targeted advertising.

13. Security

We use technical and organisational measures that fit the risk to protect personal data against loss, misuse, and unauthorised access. These include controlling who can reach the data and limiting access to the people and providers who need it.

No system is completely secure. If a breach puts your rights at risk, we will tell you and the authorities where the law requires it.

14. Artificial intelligence providers

We use these artificial intelligence providers: OpenRouter, which passes requests to Google Gemini 2.5 Flash-Lite.

To extract lab markers and draft protocols, we send the provider lab report text (only when our own parser finds no markers), images of the first two pages of scanned lab reports, the marker summary, and the symptoms and constraints a practitioner types. Lab reports can show a patient's name and other identifiers, so this content may include them. We ask the model not to put patient names in its drafts. Every draft is for practitioner review.

No agreement was recorded that says these providers refrain from keeping that content. They may keep it for a limited time under their own terms.

SwiftSoft Labs does not use your content to train AI models. Our AI gateway, OpenRouter, does not store your prompts or responses or use them for training under its default settings. The model provider that answers a request handles it under its own policy and may keep it for a limited time to prevent abuse.

15. Changes to this policy

We may update this policy. When we make a material change we will update it here and, where the law requires, tell you.

16. Contact us

To use a right or ask a question, write to legal@swiftsoftlabs.com or to our data protection contact at legal@swiftsoftlabs.com.

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