ReplyRisk — Privacy Policy
Last updated: 22 September 2026
ReplyRisk analyses one email conversation at a time — in Gmail or
Outlook on the web — only when you ask it to. It does not read your mailbox, and it does not keep your email.
What ReplyRisk does with your email
When you press Analyze this conversation, the extension reads the
conversation currently open in your Gmail or Outlook tab and sends it to the ReplyRisk
server, which passes it to an AI provider (OpenAI) to produce the analysis. The
same applies when you press Generate follow-up.
Outlook shows earlier messages of a conversation collapsed. To read the whole
conversation, ReplyRisk opens those messages on screen, reads them, and closes them
again — the same thing you would do by clicking them. Outlook access is optional:
your browser asks for it the first time you press Analyze in Outlook, and you can
withdraw it at any time in the extension's settings.
Nothing happens without that click. ReplyRisk does not scan your
inbox, does not run in the background, and never reads a conversation you have
not asked it to analyse. It has no access to your Google or Microsoft account — no
OAuth, no Gmail or Microsoft Graph API — only to what is on screen.
What is stored, and what is not
| Data | Stored? |
| Email content, subjects, senders, attachments |
No. Used for your request, then discarded. Never written to disk, never in logs. |
| Generated analyses and drafts |
No. They exist in the side panel until you close it. |
| Your email address, if you sign in |
Yes — to hold your account, quota and subscription. |
| Usage counts |
Yes — how many analyses you have run this month, to enforce plan limits. |
| Product statistics |
Yes, as daily totals only — how many installs opened the panel, pressed Analyze, ran an
analysis, signed in or started an upgrade, and whether they came from the Chrome or Edge
store. The panel also reports whether it was opened over a mail tab and, when Analyze could
not go ahead, which of a few fixed reasons stopped it — so we can tell a confusing first
screen from a broken one. The address of the page you are on is never sent: a mail tab is
reported as "a mail tab", and any other page is not reported at all. Your extension's random
id is kept only as a one-way hash with the first and last day it was seen, so that a
returning user is not counted twice. No email content, no address, no browsing history. |
| Server logs |
Counts and outcomes only: message count, character count, risk category, score. Never email text. |
| Feedback you send |
Yes — what you selected, your comment, and the verdict you are disputing. The conversation is not attached. |
Who else sees it
- OpenAI — processes the conversation to produce the analysis.
API data is not used to train their models.
- Railway — hosts the ReplyRisk server.
- Dodo Payments — handles subscriptions. ReplyRisk never sees
your card details.
- Resend — delivers sign-in emails.
Nobody else. Your data is never sold, rented, or shared for advertising.
Limited use
- Data is used only to provide the features you invoke: analysing a
conversation and drafting a follow-up.
- It is transferred only to the providers above, and only to deliver those
features.
- It is never used for advertising — personalised, retargeted,
interest-based or otherwise.
- No human reads your email. We cannot: it is not stored. Feedback you
choose to send is read, because you sent it.
What is kept in your browser
A session token (if you sign in) and your settings, in Chrome's extension
storage on your machine. Clearing them signs you out.
Deleting your account
Email privacy@wordscards.app and your
account, usage counts and subscription record will be deleted. Your email content
needs no deletion request, because it was never kept.
Changes
If this policy changes materially, the date above changes and the extension's
listing is updated.
Contact
privacy@wordscards.app