SwiftSoft Labs

AWOL Information Security Policy

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

Information Security 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"). The security facts the plan records. It does not describe a control that was not recorded.

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.

Minimum age: 16

Sensitive data: Not recorded.

Purposes: behavioral (Legitimate interests); operational (Consent)

No certification was recorded. A detected dependency is not proof that a control runs in production.

3. Safeguards the plan records

Signed form tokens, a honeypot field, per-network rate limits, Vercel Firewall rate limits and a word blocklist.

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:

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