AWOL Data Anonymization and Pseudonymization Policy
Version 1.0.0, effective 18 November 2026. Signature verified with key synlex-1.
Data Anonymization and Pseudonymization Policy
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 document is from
This document is from SwiftSoft Labs LLC ("we", "us"). Whether the plan records a method for removing or replacing identifiers.
Jurisdiction: Wyoming, United States (us-wy)
2. What the plan records
Data categories:
Approximate location (city, rounded to about 11 km)
Country
Daily-rotating hashed network identifier
IP address (used for city lookup and rate limits, not stored)
Report status and excuse, chosen from fixed lists
Share-link referrer and campaign tags
Usage analytics
Workplace or school name (optional)
Processors:
InsForge, transfer: Standard contractual clauses, agreement: https://insforge.dev/dpa
Vercel (Analytics), US, transfer: Standard contractual clauses, agreement: https://vercel.com/legal/dpa
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.
No certification was recorded. A detected dependency is not proof that a control runs in production.
3. Anonymisation and pseudonymisation
Locations are rounded to 0.1 degrees (about 11 km). IP addresses are replaced with a keyed hash that changes daily. Workplace names are shown only after manual approval, with at least 5 reports, as a count rounded to 5.
4. Changes and contact
Questions go to info@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 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:
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.