Privacy Policy
1. Data Practices and Account Access
Domain Sender is built with a privacy-focused, no-persistent-email-storage architecture. When you sign in with Google, we only request basic OpenID Connect scopes (openid, email, profile). We never request restricted Gmail API scopes to read or modify your inbox.
2. No Persistent Storage of Email Contents or SMTP Passwords in Our Databases
Your SMTP passwords are stored in your local Chrome browser storage (chrome.storage.local), rather than in our service database. Email subjects, bodies, recipients, and attachments are never written to our databases; they are relayed transiently in memory to your designated SMTP server and immediately discarded.
3. Chrome Extension Data and Processing
The Chrome extension handles sender addresses and names, SMTP connection settings and passwords, signatures, Google account email addresses, account pairing tokens, recipients, subjects, message bodies and attachments where necessary to send messages from a custom domain. Sender configuration, signatures, SMTP credentials and tokens are stored in Chrome’s local extension storage. Anyone with access to your browser profile or device may be able to access this local data; use caution on shared computers.
When you send a message, SMTP credentials and email data are sent over HTTPS to api.domain-sender.com (Cloudflare Workers), passed to a Tokyo-region AWS Lambda relay, then transmitted using TLS or a secure SMTP connection to your configured SMTP provider. The publicly distributed Chrome Web Store extension does not allow configuring any relay other than the official Domain Sender API. Sending requires linking your Domain Sender account, and server-side limits apply according to your subscription plan.
Automatic SMTP host suggestions may send your domain name and DNS queries to Google Public DNS. When you request a Gmail settings import, the extension reads the necessary account and signature details from Gmail’s settings pages. Google sign-in requests only the basic OpenID profile scopes.
When you choose to export settings, the extension creates a local JSON backup that may contain sender email addresses, signatures and SMTP host settings, but excludes SMTP passwords and API/authentication tokens. Import also excludes credentials. Keep your downloaded backup secure.
4. Metadata Stored for Quota & Billing
We store only your account email, subscription plan status, Stripe customer/subscription identifiers, free-trial first-success timestamp and lifetime send count (7 days / 20 total emails), paid-plan monthly send counts, domain-level delivery status logs (sender domain, timestamp, and success/error code), and keyed HMAC-SHA256 sender identifiers with first-free-test status/timestamps for registration and trial enforcement. These identifiers are pseudonymous, not fully anonymous. Sender addresses, SMTP passwords, message bodies and attachments are not stored in these quota/test tracking tables.
5. Third-Party Processors
Payments are handled by Stripe, Inc.; credit card numbers are not processed by our servers. Cloudflare, Amazon Web Services, Google Public DNS and your chosen SMTP operator may process relevant data as required to operate the service. Contact form notifications use our contracted hosting provider’s mail infrastructure.
6. Contact inquiries
The contact form collects your reply email, optional name, request category and message. Unlike outgoing email bodies, inquiry content is retained in D1 for support and legal disclosure requests, and is forwarded to the operator’s support mailbox as a notification. Tickets are scheduled for deletion within 180 days; records needed for ongoing lawful disputes may be handled separately.
Cloudflare Turnstile helps prevent automated submissions. We store an HMAC-based rate-limiting identifier instead of the visitor’s raw IP address in our inquiry database. Infrastructure providers may keep their own access logs. To request access to or deletion of inquiry data, use the contact form.
7. Limited Use and Data Sharing
Data accessed through the extension is used only to provide custom-domain sending, sender and signature selection, account linking, usage limits, customer support, security and abuse prevention. We do not sell user data or use it for targeted ads, credit scoring or lending. Data is shared with service providers only when necessary to operate these features or as required by law or for security. The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.
8. Access and Deletion Requests
To request access to or deletion of account or inquiry records, use our contact form. Some records may need to be retained for lawful billing, compliance or security reasons. Locally stored extension data can be removed by deleting the extension’s browser data.