SwiftSoft Labs

AWOL Account Deletion and Data Erasure

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

Account Deletion and Data Erasure

This draft is compiled from your compliance plan. It is not legal advice. Have a qualified lawyer review it before you publish it.

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

AWOL has no accounts. You can withdraw your own report at any time from your patient card, which deletes it at once. You can also ask us to delete a report, or to tell you what we hold and correct it.

3. How to ask

Use the Withdraw button on your patient card. If you can no longer reach it, write to legal@swiftsoftlabs.com with the card's number or link and roughly when you filed it.

4. What we delete and what we keep

Retention: Reports are kept while the map is online. A person can withdraw their own report at any time, which deletes it at once. Withdrawal records are deleted after 2 days. The report cookie expires after 60 days.

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:

  • InsForge
  • Vercel

6. How long a request takes

Withdrawing deletes the report at once. We answer written requests within one month.

7. Changes and contact

We may update this policy. Questions go to info@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 Wed, 18 Nov 2026 12:50:57 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 1f37936c78e2fac1f81cc8cf67c42b1707c61fa3c464c977be8d696d63efe6e1 -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/awol?version=1.0.0' | jq -j .signature.manifest > manifest.json
curl -s 'https://synlex.vercel.app/api/public/v1/swiftsoftlabs/awol?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