Privacy Policy
What we collect, how we use it, and your rights. Plain English.
1. Who we are
EmailSavy is an email tracking service operated via a Chrome extension and the website emailsavy.com. Contact: connect@startuptalky.com.
2. Data we collect about YOU (the EmailSavy account holder)
- Account info: email, name (optional), bcrypt-hashed password, account creation timestamp.
- Technical and device data when you sign up: such as your IP address, approximate location (country, region and city, worked out from the IP address), browser, operating system, device type, language, time zone, screen size, the website you came from, campaign tags in the link, and whether your email is a work or a free address. We use it to run and improve the service, to spot abuse and fake signups, and to understand which channels bring real customers. This location lookup uses an offline database on our own server, so your IP address is not sent to a third party for it. We keep it with your account record and it is removed from our live service when your account is deleted. IP location data by DB-IP.com (CC BY 4.0).
- Tracked email metadata: for each email you send with tracking on — recipient address, subject line, send timestamp, the unique tracking ID we generated, the Gmail thread ID (if available), the version number of the extension that registered it, and the destination web address of each link we track.
- Sender network details: the network (IP) address and a hashed device fingerprint of the sender at the moment a tracked email is registered, used only to recognise and ignore the sender's own views and clicks.
- Reply check by the extension: while Gmail is open in your browser, the extension looks at the sender address and the date of the messages in your tracked conversations to find real replies and when they arrived. To do this it loads the conversation page inside your own browser, keeps only the sender address and the date, and discards the rest; apart from the reply preview described in the next item, message text, subjects and other recipients are never stored or sent. The only things sent to our server are the replier's address and the reply's arrival time. When the extension reads a conversation that we had flagged as replied and finds no reply in it, it sends only a note that none was found and how many messages the conversation holds.
- Reply preview: when a reply to a tracked email is detected (by the extension on your Gmail page, or by the optional Gmail connection), the first ~240 characters of that reply and the replier's address.
- Engagement events: opens, clicks, replies. Each event captures timestamp, IP address of the device that triggered it, User-Agent string, approximate location derived from the IP (city, region, country, latitude and longitude, and the network provider's name), and a hashed device fingerprint for de-duplication. The location is looked up by sending the IP address, unencrypted, to a third-party location service (ip-api.com, operated outside India); see section 6.
- Custom tracking domain config (Pro feature, optional): the subdomain you chose, DNS verification status.
- Webhook URLs (Pro feature, optional): Slack/HTTPS endpoints you configured for real-time notifications.
- Payment metadata (Pro subscribers): Razorpay subscription ID + customer ID. We do not store card numbers: Razorpay handles card data.
- Your list of recipients: for every person you sent a tracked email to, one summary row with their email address, how many emails, opens and clicks, their best-known location and an engagement score. This is built from your tracked emails; we do not read your Gmail or Outlook address book.
- Campaigns, sequences and templates (only if you use these features): the subject, the full message text you write, the recipient lists you upload and the merge fields you attach to each recipient (for example first name and company). Reminders store the follow-up note you type.
- Where you came from, once at signup: when you create an account we record the time, your network (IP) address, your browser string, the website and page you came from (hostname and path only, never the rest of the address) and any campaign tags (
utm_source,utm_medium,utm_campaign,utm_content,utm_term,src) in the address of the signup page. No script or cookie is used for this. It is kept with your account and deleted with it. - Product-use events: a record of the name and time of these moments: account created, extension first used, first tracked email, Gmail connected, campaign or sequence created, checkout started, first payment, subscription cancelled (not a plan that simply ran out). Each carries at most a few non-personal details (for example the number of recipients in a campaign, the number of steps in a sequence, the signup source tags). They are recorded by our server when the action happens: no script, cookie or browser storage is involved. Kept while your account exists and deleted with it.
- Milestone dates: the first time each of these happened: the extension was first used with your account, your first tracked email, your first successful subscription payment, and the date your subscription was last cancelled or ended. Kept with your account and deleted with it. For accounts created before 14 November 2026 the extension date is the first time we saw it after that day, and the first-tracked and first-payment dates are filled in from our existing records.
- Referrals: your referral code, and the email addresses of people who signed up with it (kept on your record).
- Install clicks on our site: when you click an install button on emailsavy.com we record where the button was, the website you came from (hostname only), your browser string and, if you are logged in, your account.
- Feedback and waitlist: what you type into the feedback box (rating, message up to 500 characters, the page, your browser string) and your email if you join the team-plan waiting list.
- Records of opt-outs and unsubscribes that your recipients make: see section 3A.
3. Things we do not currently collect
- The body of the emails you send from Gmail or Outlook with tracking on (we never read them). The only message text we keep is what you type into our own campaign, sequence, template and reminder tools, and the reply preview described above
- Attachments
- Your Gmail or Outlook address book (we keep only the list of people you actually sent tracked emails to, described above)
- Your browsing history outside of mail.google.com / outlook.com
- Credit card numbers or banking info (Razorpay handles those, never us)
- Behavioral analytics for advertising or third-party data sharing
3A. If you RECEIVED an email that is tracked by EmailSavy
The person who sent you the email chose to use EmailSavy. When your email program loads the invisible image or you click a tracked link, we store, for the sender and to run the service: your email address, the time, your IP address, a browser and device description, an approximate location worked out from the IP address (city, region, country, latitude, longitude and the network provider's name) and a hashed device fingerprint. If you reply and the sender's extension or Gmail connection notices it, we store your address, the time of the reply and the first ~240 characters of it.
How to stop it: block remote images in your email program (steps on our opt-out page); that stops open tracking from every sender. Click tracking is separate: a tracked link sends your browser through our server first, so we see the click if you follow the link. To have your data removed: email connect@startuptalky.com from the address concerned and we will delete or anonymise the records we hold about it and reply to confirm, aiming for within 30 days. Some links open a short "You are leaving EmailSavy" page that loads its styling from the Tailwind CDN, which therefore sees your IP address. If you use an unsubscribe or opt-out link, we keep a record of it so that you are not tracked or emailed again: your email address, the time, your IP address, your browser string and the reason you gave. We keep that record for as long as it is needed to honour your request; ask us to delete it too if you prefer, but then we can no longer stop the sender from emailing you.
4. Gmail API access (only if you connect Gmail)
Connecting your Gmail account is optional. You can use EmailSavy without ever doing this. If you choose to connect, we request read-only access via Google OAuth.
4.1 What scopes we request
gmail.readonly— read-only access to your Gmail messages and threads. Used to detect replies to your tracked emails server-side and fetch their content for the in-app preview.userinfo.email— your Google account email address. Used to display "Connected as <your-gmail>" in settings and to verify the connected account matches your EmailSavy account.
We never request: gmail.send (sending), gmail.modify (modifying labels/messages), gmail.compose (drafting), or any scope that lets us alter your inbox.
4.2 What we do with Gmail data
- We poll the Gmail API every 10 minutes for replies to emails you've already tracked.
- For matching threads, we fetch the most recent incoming message's body and store the first 240 characters as a "reply preview" so you can see the gist in the EmailSavy dashboard without opening Gmail.
- We store the canonical Gmail thread ID and reply timestamp on the corresponding tracked-email record.
- We do not read, store, or process emails that aren't replies to your tracked outbound mail.
- We do not read attachments.
- We do not share your Gmail data with anyone.
4.3 Limited Use disclosure (Google API Services User Data Policy)
EmailSavy's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Specifically:
- We use Google user data only to provide or improve user-facing features (server-side reply detection + reply preview + canonical thread IDs).
- We do not use Google user data to train AI/ML models or generalized models.
- We do not sell, transfer, or share Google user data with third parties for advertising, marketing, or any commercial purpose.
- We do not allow humans to read Google user data, except: (i) with your specific consent, (ii) for security investigations or to comply with the law, or (iii) when the data has been aggregated and anonymized.
4.4 Disconnecting Gmail
You can disconnect Gmail at any time from /dashboard/settings or via your Google account permissions page. On disconnect we immediately revoke our refresh token at Google and delete it from our database. Already-fetched reply previews remain on your tracked-email records (they're your data, not Google's), but no further polling occurs.
5. Where data is stored
All data is stored on AWS infrastructure (Mumbai, India region) in a MongoDB database. Refresh tokens for Gmail OAuth are encrypted at rest using AES-256-GCM. All connections use TLS 1.2+ (HTTPS).
6. Third-party services
We use the following third-party services strictly to operate EmailSavy:
- ip-api.com — IP location lookup. It receives the IP address of the device that opened an email or clicked a link, sent over an unencrypted connection, and returns the approximate location (city, region, country, latitude and longitude) and the network provider's name, which we store with the event. We send nothing else. ip-api.com is operated outside India. We may replace it with a location database on our own servers in future.
- Razorpay — processes Pro subscription payments. Razorpay receives the minimum necessary info (your email, plan name).
- Google Cloud (Gmail API) — only if you opt into the Gmail connection.
- OpenAI — currently NOT used by EmailSavy. Reserved for future opt-in features; if/when introduced, this clause will be updated and explicit consent collected.
- Sentry — error tracking. Only stack traces + request metadata, never email content or PII.
- An email delivery (SMTP) provider — receives your email address and name to send you account emails: welcome, verification, password reset, the daily digest, alerts and reminders.
- Tailwind CDN (cdn.tailwindcss.com) — the dashboard, password-reset and a few other pages load their styling library from this host, so it sees your IP address and browser details, as any website you open does.
- Google Fonts (fonts.googleapis.com, fonts.gstatic.com) — our public pages load their fonts from Google, which sees the visitor's IP address and browser details.
- Plausible — page-view counts on our public pages, only after you accept the cookie banner, run by us (see section 9).
- Webhook destinations you set (Slack or any HTTPS address) — receive the event notices you ask for.
- AWS / Let's Encrypt — hosting + SSL.
7. Data retention & deletion
- Tracked email records and their open and click events (including the IP address, approximate location and device of each event) are kept while your account is active and until you delete them. You can delete individual emails or your entire history from the dashboard.
- Opt-out, unsubscribe, consent and other activity records (for example a recipient's email address, IP address, browser string, time and reason) are kept so that we can keep honouring requests and run and improve the service. Our practice is to remove this data when you or a recipient asks us to (section 3A), or when the account that owns it is deleted, rather than on a fixed schedule.
- Account deletion: use /dashboard/settings → "Delete my account". We remove the data tied to your account, including your tracked emails with their open and click events, your recipients list, campaigns, sequences, templates, reminders, webhooks, custom domain, Gmail OAuth tokens, opt-out and consent records, install-click rows and waiting-list entries, and your email address in other users' referral lists. What we may keep: the payment record of a Pro subscription (plan and Razorpay identifiers), marked as deleted, for accounting and legal reasons; a deletion log (a one-way hash of your email address, the time and the IP address of the request) as proof that the deletion happened; payment notifications from Razorpay; and, if our staff ever opened your account to help you, a log of that.
- Gmail: when you disconnect it we revoke our access at Google and remove the token from our database.
- Backups: we keep backups of our database for disaster recovery. Data you delete may remain in backups for some time.
8. Your rights under the DPDP Act 2023 (India) and GDPR / CCPA
The Digital Personal Data Protection Act 2023 (India) grants you the following rights. You may exercise them directly from your dashboard or by contacting our Grievance Officer.
- Right to access (§11) — export your account data as JSON via GET /api/account/export (login required) or CSV from the dashboard.
- Right to correction and erasure (§12) — edit your account info in settings. To delete your account and all associated data, use the Delete Account option in your dashboard settings or call POST /api/account/delete (login required; you confirm with your current password).
- Right to grievance redressal (§13) — contact our Grievance Officer: Shubham Kumar, StartupTalky — connect@startuptalky.com. We aim to respond within 30 days.
- Portability — JSON and CSV exports cover your tracked emails and campaigns; ask us at connect@startuptalky.com for anything else we hold about you.
- Objection / restriction — email connect@startuptalky.com with your request.
9. Cookies
We use one essential cookie: mp_token, an HTTP-only session cookie that keeps you logged into the dashboard. We do not use tracking cookies, advertising cookies, or third-party analytics. If you accept the cookie banner on our public pages, we count page views with Plausible, which we run ourselves. It sets no cookies and builds no profile of you; your IP address is used briefly to count visitors and is not stored. The extension and the tracking links in your emails never load it.
10. Children's privacy
EmailSavy is not intended for users under 16. We don't knowingly collect data from minors.
11. Changes to this policy
If we materially change this policy, we'll email all active users at least 14 days before the change takes effect. Minor wording updates (typo fixes, clarifications) will be reflected on this page with the "Last updated" date refreshed.
12. Security
Found a vulnerability? Email connect@startuptalky.com with subject line "Security report". See our security.txt for full disclosure policy.
13. Contact
For privacy questions, data requests, or anything else: connect@startuptalky.com.