SwiftSoft Labs

SpamRescue Artificial Intelligence Use Notice

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.

Artificial Intelligence Use Notice

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 artificial-intelligence providers the plan names, and the uses it records.

Jurisdiction: Wyoming, United States (us-wy)

2. What the plan records

Data categories:

  • AI lead scores and suggested replies
  • Account credentials (password, 2FA, passkeys)
  • Billing customer ID
  • Connected Gmail or Outlook account and refresh token
  • Contact form messages
  • Email address
  • Email bodies (read for AI scoring, not stored)
  • Name
  • Phone number (SMS alerts)
  • Spam-folder email sender, subject and snippet
  • Usage analytics
  • ip address
  • request bodies
  • request url path and query string

Processors:

  • Google, transfer: Standard contractual clauses, agreement: https://business.safety.google/processorterms/
  • InsForge, transfer: Standard contractual clauses, agreement: https://insforge.dev/dpa
  • Microsoft (Sign-in and identity), US, transfer: Standard contractual clauses, agreement: https://www.microsoft.com/licensing/docs/view/Microsoft-Products-and-Services-Data-Protection-Addendum-DPA
  • OpenRouter, transfer: Standard contractual clauses, agreement: https://openrouter.ai/data-processing-agreement
  • PostHog, transfer: Standard contractual clauses, agreement: https://posthog.com/dpa
  • Resend, transfer: Standard contractual clauses, agreement: https://resend.com/legal/dpa
  • Sentry (Monitoring and error reporting), US, transfer: Standard contractual clauses, agreement: https://sentry.io/legal/dpa/
  • Twilio (Email and messaging), US, transfer: Standard contractual clauses, agreement: https://www.twilio.com/en-us/legal/data-protection-addendum
  • Vercel, transfer: Standard contractual clauses, agreement: https://vercel.com/legal/dpa

Retention: Account data is kept until you delete your account in Settings, which removes it from our database. Disconnecting a mailbox deletes its token and scan records; saved leads stay until you delete them or your account. Email bodies are not stored. Billing records are kept as tax and accounting law requires.

Minimum age: 18

Sensitive data: Not recorded.

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

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

3. Models and automated decisions

The subject, up to 2,000 characters of each scanned email body, and your keywords are sent to Google Gemini 2.5 Flash-Lite through the InsForge AI gateway (which uses OpenRouter) to score leads and draft replies.

No artificial intelligence provider was named.

No agreement was recorded that says these providers refrain from keeping that content.

Email content you scan is not used to train AI models.

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 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