SwiftSoft Labs

SpamRescue Privacy Policy

Version 2.0.0, effective 19 November 2026. Signature verified with key synlex-1.

Privacy Policy

1. Who we are

SwiftSoft Labs LLC ("we", "us") decides how the personal data described in this policy is used.

  • Legal name: SwiftSoft Labs LLC
  • Legal form: Registered company (LLC, corporation or similar)
  • Jurisdiction: Wyoming, United States (us-wy)
  • Contact email: info@swiftsoftlabs.com
  • Address: 312 W 2nd St, PO Box 5309, Casper, WY 82601
  • Data protection contact: legal@swiftsoftlabs.com

2. Whose data this covers

  • Account holders
  • People who use the contact form
  • Senders of emails in a connected spam or junk folder
  • Website visitors

3. The personal data we collect

We collect the following categories of personal data:

  • 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 (through Sentry)
  • request bodies (through Sentry)
  • request url path and query string (through Sentry)

4. Sensitive personal data

We do not ask for sensitive personal data, such as data about health, ethnic origin, political opinions, religion, sexual orientation, or biometric identity, and the service is not designed to collect it. Please do not send it to us.

5. Children

Minimum age: 18

The service is for people who are 18 or older. We do not knowingly collect personal data from anyone younger.

If you believe a person younger than 18 has given us personal data, write to info@swiftsoftlabs.com and we will delete it.

6. Why we use personal data

  • Understanding how the service is used (behavioral). Legal basis: Legitimate interests. Page analytics on public pages and error tracking to keep the service working
  • Operating and providing the service (operational). Legal basis: Contract.

**Google user data.** SpamRescue's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We use Gmail data only to scan your spam folder, show you likely leads, and move the messages you choose to your inbox. To score messages, the subject and part of the body are sent to our AI providers (Google Gemini through the InsForge AI gateway and OpenRouter), only for that purpose. We do not use Gmail data for advertising, do not sell it, and do not use it to train general AI models. No person reads it except with your permission, for security, or where the law requires.

7. Marketing email

We do not send marketing email.

8. Who we share personal data with

We use the service providers below. Each one processes personal data on our behalf and under a data processing agreement where one is listed. They may use the data only to provide their service to us.

Google

  • Service: Other service
  • Purpose: Google sign-in, Gmail spam-folder access, and Gemini AI lead scoring through the InsForge gateway
  • Data received: Account email and name, spam-folder email sender, subject and body, mailbox access token
  • Location: United States
  • Data processing agreement: https://business.safety.google/processorterms/

InsForge

  • Service: Other service
  • Purpose: Database, AI gateway, email delivery and scheduled scans
  • Data received: Account data, leads, encrypted mailbox tokens, email subject and body sent for AI scoring
  • Location: United States
  • Data processing agreement: https://insforge.dev/dpa

Microsoft

  • Service: Sign-in and identity
  • Purpose: Outlook sign-in and junk-folder access through Microsoft Graph
  • Data received: Account email, junk-folder email sender, subject and body, mailbox access token
  • Location: United States
  • Data processing agreement: https://www.microsoft.com/licensing/docs/view/Microsoft-Products-and-Services-Data-Protection-Addendum-DPA

OpenRouter

  • Service: Other service
  • Purpose: AI model routing behind the InsForge AI gateway, for lead scoring and suggested replies
  • Data received: Email subject, up to 2,000 characters of each scanned email body, your keywords
  • Location: United States
  • Data processing agreement: https://openrouter.ai/data-processing-agreement

PostHog

  • Service: Other service
  • Purpose: Page analytics on public pages
  • Data received: Pages viewed, device and browser, random session ID
  • Location: United States
  • Data processing agreement: https://posthog.com/dpa

Resend

  • Service: Other service
  • Purpose: Transactional email: sign-in codes, password resets and lead alerts
  • Data received: Email address, verification codes, lead sender and subject
  • Location: United States
  • Data processing agreement: https://resend.com/legal/dpa

Sentry

  • Service: Monitoring and error reporting
  • Purpose: Error tracking and performance monitoring
  • Data received: Error reports, IP address, request URL and body, device and browser
  • Location: United States
  • Data processing agreement: https://sentry.io/legal/dpa/

Twilio

  • Service: Email and messaging
  • Purpose: SMS lead alerts (Pro plan)
  • Data received: Phone number, lead sender and subject
  • Location: United States
  • Data processing agreement: https://www.twilio.com/en-us/legal/data-protection-addendum

Vercel

  • Service: Other service
  • Purpose: Hosting
  • Data received: IP address and request data
  • Location: United States
  • Data processing agreement: https://vercel.com/legal/dpa

Purchases are made from Kelviq, which sells the service to you as merchant of record. The payment details you give at checkout go to Kelviq. It uses them as an independent controller, not on our behalf, under its own privacy policy.

Kelviq's privacy policy: https://www.kelviq.com/buyer-privacy/

9. Transfers outside your country

Some providers handle personal data outside the country where you live. Where the law requires a safeguard for that transfer, we rely on the mechanism listed here.

  • Google: United States. Transfer mechanism: Standard contractual clauses.
  • InsForge: United States. Transfer mechanism: Standard contractual clauses.
  • Microsoft: United States. Transfer mechanism: Standard contractual clauses.
  • OpenRouter: United States. Transfer mechanism: Standard contractual clauses.
  • PostHog: United States. Transfer mechanism: Standard contractual clauses.
  • Resend: United States. Transfer mechanism: Standard contractual clauses.
  • Sentry: United States. Transfer mechanism: Standard contractual clauses.
  • Twilio: United States. Transfer mechanism: Standard contractual clauses.
  • Vercel: United States. Transfer mechanism: Standard contractual clauses.

The safeguards we rely on:

  • Standard contractual clauses: the standard contractual clauses approved by the European Commission.

10. Cookies and similar technologies

The service uses cookies and similar technologies, such as local storage and pixels, to run, to keep you signed in, and to keep the service secure.

Our Cookie Policy lists them and explains how to change your choices.

11. How long we keep personal data

We keep personal data only for as long as it is needed for the purposes in section 6, or as the law requires. When it is no longer needed we delete it or make it anonymous.

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.

12. Your rights

You can ask us to tell you what personal data we hold about you, to give you a copy, to correct it, and to delete it. Write to legal@swiftsoftlabs.com. We may need to confirm who you are before we act, and we answer within one month.

If you are in the European Economic Area, the United Kingdom or Switzerland, you also have the right to restrict our use of your data, to object to it (including use based on legitimate interests), to receive your data in a portable format, and to withdraw consent at any time without affecting earlier use. You can complain to the data protection authority where you live or work.

If you live in a US state with a privacy law, such as California, you have similar rights to know, correct and delete your data, and we will not treat you differently for using them. We do not sell personal data or share it for targeted advertising.

13. Security

We use technical and organisational measures that fit the risk to protect personal data against loss, misuse, and unauthorised access. These include controlling who can reach the data and limiting access to the people and providers who need it.

No system is completely secure. If a breach puts your rights at risk, we will tell you and the authorities where the law requires it.

14. Changes to this policy

We may update this policy. When we make a material change we will update it here and, where the law requires, tell you.

15. Contact us

To use a right or ask a question, write to info@swiftsoftlabs.com or to our data protection contact at legal@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 Thu, 19 Nov 2026 10:25:39 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-v2.0.0.tsr -digest 99fa9e17d713258598b0a421ba8d9f64c542a08cf478b9f23f99b2608aba4bf8 -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/spamrescue?version=2.0.0' | jq -j .signature.manifest > manifest.json
curl -s 'https://synlex.vercel.app/api/public/v1/swiftsoftlabs/spamrescue?version=2.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