Privacy Policy

SalesRuns.com · Last updated: August 31, 2026

This Privacy Policy explains how [LEGAL_ENTITY_NAME] ("SalesRuns", "we", "us") collects, uses, stores, and protects personal data when you use the SalesRuns desktop application and related services (the "Service") at salesruns.com.

1. Data controller

Data controller: [LEGAL_ENTITY_NAME], registered at [REGISTERED_ADDRESS]. Privacy inquiries: [email protected].

2. What the Service does

SalesRuns is an AI sales assistant that helps business users manage outbound email campaigns and follow-up on replies. It connects to email accounts the user owns or is authorized to use, via standard protocols (IMAP/SMTP) or via the Gmail API and Microsoft Graph API under the user's explicit OAuth authorization.

3. Email permissions we request, and exactly how each is used

Permission (scope)	What we access	Purpose	What we do NOT do
`gmail.readonly` (Gmail API)	Message headers and bodies of emails in the user's inbox that match known outbound recipients/threads the user sent through SalesRuns	To detect customer replies to the user's outreach, classify them with AI, and generate follow-up suggestions	We do not read, store, or process emails unrelated to the user's tracked outreach. We do not scan the full mailbox. We do not use content for model training, advertising, or any purpose beyond the above.
`gmail.send` (Gmail API)	Send capability only	To send follow-up/reply emails that the user has reviewed and approved within the Service, on the user's behalf	We never send without the user's initiate/approval action in the app.
`Mail.Read` (Microsoft Graph, delegated)	Same as gmail.readonly above, for Microsoft 365 mailboxes	Same reply-detection and AI follow-up purpose	Same restrictions as gmail.readonly.
`Mail.Send` (Microsoft Graph, delegated)	Send capability only	Same as gmail.send	Same restrictions as gmail.send.
`offline_access`	Refresh tokens	To keep the user's connection active without repeatedly asking them to re-authorize	Refresh tokens are stored encrypted on the user's own device; the user can revoke access at any time (Section 8).
IMAP/SMTP (other providers)	Mail the user's credentials allow	Same reply-monitoring and sending purposes	Credentials are stored only on the user's device in the OS keychain (encrypted at rest).

4. Email content storage — local-first architecture

Email bodies processed by SalesRuns are stored on the user's own computer in an encrypted local database. The default data path keeps message bodies on the user's device; SalesRuns servers receive only non-content operational metadata (e.g., send/reply event timestamps, delivery status) needed for the AI follow-up suggestion pipeline.

Where the user opts into cloud sync of their workspace, synced items are transmitted over TLS and stored encrypted; the user can disable cloud sync and delete synced data at any time (Section 8).

5. What we collect from you directly

Account information: name, work email, company name (for Service provisioning and billing).
Payment information: processed by our payment providers (Stripe); we do not store card numbers.
Support communications you send us.

6. What we do NOT do

We do not sell personal data or email content to third parties.
We do not use the content of users' emails to train general-purpose AI models.
We do not access mailboxes of third parties who have not authorized the Service.
We do not request full-account scope (e.g. mail.google.com) and we do not use IMAP XOAUTH2 against Gmail.

7. Security measures

OAuth access/refresh tokens and mail credentials are encrypted at rest on the user's device (macOS Keychain / Windows DPAPI via Electron safeStorage).
All network transport uses TLS 1.2+.
Least-privilege design: the reply monitor only processes threads matching the user's own tracked outbound recipients; all other mail is ignored before any AI processing.
Access to production systems is restricted, logged, and MFA-protected.

8. Retention and deletion

Email content: retained only on the user's device; removed when the user deletes it in-app or uninstalls the Service.
Cloud-synced data: deleted within 30 days of the user disabling sync or closing their account.
Operational metadata: retained up to 24 months for abuse prevention and billing, then deleted or aggregated.
Revoking OAuth access: the user can revoke SalesRuns' authorization at any time via their Google Account security settings (myaccount.google.com/permissions) or Microsoft account (office.com → My account → Security → Apps), or via the "Disconnect" action in the SalesRuns app, which also deletes stored tokens on the device.

9. International data transfers

SalesRuns serves business customers internationally. Where personal data is transferred outside the EEA/UK, we rely on standard contractual clauses or equivalent mechanisms, and minimize transferred data as described in Section 4.

10. Your rights

Depending on your jurisdiction (GDPR, CCPA, PIPL and others), you may request access, correction, export, or deletion of your personal data, or object to processing. Contact [email protected]; we respond within 30 days.

11. Children

The Service is for business use and is not directed to persons under 16.

12. Changes to this policy

We will post any changes on this page with an updated "Last updated" date and, for material changes affecting email permissions, give at least 14 days' advance notice via the Service or email.

13. Contact

[LEGAL_ENTITY_NAME] · [email protected] · [REGISTERED_ADDRESS]