SwiftSoft Labs

ProtocolPad Account Deletion and Data Erasure

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

Account Deletion and Data Erasure

1. Who this policy is from

This policy is from SwiftSoft Labs LLC ("we", "us"). It explains how you ask us to delete personal data we hold about you.

Jurisdiction: Wyoming, United States (us-wy)

2. What you can ask us to delete

You can ask us to delete the personal data described in our Privacy Policy, including the data tied to your account.

You can also ask us to tell you what we hold and to correct it. Those requests use the same contact.

**Patients.** Patient records belong to the clinic that entered them. If you are a patient, ask your clinic to delete or correct your records. If you write to us, we pass your request to the clinic.

3. How to ask

You can delete your own account in Settings. We ask for your password, or for you to type DELETE if you sign in with Google or GitHub. If you are the only owner of a clinic that still has other members or patient data, transfer ownership first. Deleting your account cancels any paid subscription and removes your personal details. The clinic's records stay with the clinic.

You can also write to legal@swiftsoftlabs.com. Tell us the email address on the account and what you want deleted, so we can find it. A clinic that has closed its account can ask us in writing to delete its records.

We may need to confirm who you are before we delete anything. We will tell you if we need more information.

4. What we delete and what we keep

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.

When that period ends we delete the data or make it anonymous. We keep a record where the law requires us to, and we tell you if we refuse a request for that reason.

5. Providers who hold data for us

We will ask these providers to delete the personal data they hold for us when we delete it:

  • GitHub sign-in
  • Google Sign-In
  • InsForge
  • OpenRouter
  • PostHog
  • Vercel

Kelviq sells the service as merchant of record and keeps its own purchase records under its own privacy policy. Ask it directly to delete them: https://www.kelviq.com/buyer-privacy/

6. How long a request takes

Deleting your account in Settings takes effect at once. We answer written requests within one month, and we delete a closed clinic's records within 30 days of its written request. We will tell you when the request is done, and we will tell you if the law allows us longer and we need it.

7. Changes and contact

We may update this policy. Questions go to legal@swiftsoftlabs.com. Our address is 312 W 2nd St, PO Box 5309, Casper, WY 82601.

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