SwiftSoft Labs

SpamRescue Accessibility Statement

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

This is an earlier version. Read the current version, 2.0.0.

Accessibility Statement

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 statement is from

This statement is from SwiftSoft Labs LLC ("we", "us") about the service we offer to people.

Contact: info@swiftsoftlabs.com

2. What it covers

It covers the service people use. It does not describe a particular screen, and it does not come from a test of the running product.

3. Conformance

Conformance: No conformance level was recorded.

This statement does not name a standard, a level, or an audit. Those facts are not in the compliance plan.

4. How to ask for help

If you cannot use part of the service, write to info@swiftsoftlabs.com. Tell us what you were trying to do and what stopped you.

We will reply and tell you what we can change. We do not promise a change that the plan does not record.

5. Changes and contact

We may update this statement when we record a conformance level. Until then it stays as written. Questions go to info@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 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 abd1ef046a952af0bd6dcd511c44894408bdd8d58fc22455a3212d63d23d039f -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/spamrescue?version=1.0.0' | jq -j .signature.manifest > manifest.json
curl -s 'https://synlex.swiftsoftlabs.com/api/public/v1/swiftsoftlabs/spamrescue?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