Privacy policy
WhatsTheAnswer ("we", "us") is run by Stephen Riley, a sole proprietor in Florida, United States. Last updated: November 16, 2026.
What the extension does with a page
Only when you press the shortcut, click the toolbar icon, or press the button in the side panel, the extension reads the part of the page you can currently see: either the visible text (up to 20,000 characters) or a screenshot of the visible area of the tab (resized to at most 1600 pixels wide). It sends that, with your chosen model, to our server, which forwards it to Anthropic to produce an answer. The extension does not read pages in the background and has no access to other tabs.
A screenshot or the text can contain anything visible on that page, including personal information. Don't use the extension on pages showing information you don't want sent to Anthropic.
We do not store the question, page text or screenshot. Our server holds them in memory only while it handles the request; they are not written to our database, and our error logs record only metadata (model, status, request id), never page content. Anthropic receives the content to answer it; how long Anthropic keeps it is governed by Anthropic's own commercial terms and privacy policy, which limit how long it keeps API data and prohibit using it to train its models.
What we collect and store
- Email address, when you sign up or sign in. Used to identify your account and to email you sign-in codes, links and account notices. We also keep the IP address your first sign-up request came from, to stop people inviting or rewarding themselves.
- Sign-in codes and links. Stored only as one-way hashes, with the IP address that requested them, an expiry (codes 10 minutes, links 30 minutes), and a count of attempts (a code is burned after 5 wrong tries, and an account accepts at most 20 code guesses a day).
- Website sessions. A hashed session token (the browser keeps a cookie named
ss_session, marked HTTP-only; it lasts 30 days). - API keys. The extension signs in with a key we issue. We store only a hash and the first few characters (to show you which key is active), when it was created, where it came from (website or extension), and when it was revoked.
- Usage records for each answer: time, which model answered, input and output token counts, cost, credits charged, whether a second opinion was used, the confidence level the model reported (1 to 5), whether the question was unreadable (those are free, and we count them to apply the fair-use limit in the Terms), and your IP address. No question content.
- Extension version. The extension tells our server its version number; we record which version each account used on each day, so we know when an old version is no longer in use.
- "Was this right?" flags. If you press the thumbs up (right) or thumbs down (wrong) icon under an answer, we store that one-word verdict, linked to that answer's usage record and your account, with the time. It contains no question content, and you can change it for 7 days. We use it, in aggregate, to check and tune how accurate the answers are.
- Credit ledger: every change to your credit balance (purchases, usage, trial, grants, adjustments, refunds, disputes).
- Purchases: the pack, amount, status, and Stripe's session and payment identifiers, plus any refunded or disputed amounts. We never see or store your card number.
- Free-trial records (when a trial is on): a normalised form of your email, your IP address, and the date, used to limit one trial per person.
- Unusual-usage alerts: if an account's spend in 24 hours or answers in an hour pass a threshold (a sign that a sign-in key has leaked), we record the time and those two figures, and email you and the administrator.
- "Tell a Friend" invites (only while the feature is switched on): your invite code; when someone claims an invite with their email, that email in normalised form, the IP address it came from and an expiry (30 days); who invited whom and whether the reward was paid, refunded or blocked. To stop people rewarding themselves, we also ask Stripe for the card fingerprint of a qualifying purchase (a code Stripe derives from the card; it can't be turned back into the card number) and compare it with the inviter's purchases. Others only ever see a masked form of your email (for example jo•••@gmail.com), never what you paid.
- Stripe event ids we have processed, and, if you contact us, whatever you send us.
- Short-lived, in-memory rate limiting by account or IP address. It is not written to our database and resets whenever the server restarts.
Our hosting provider also keeps ordinary server and request logs (for example time, URL, status, IP address).
What stays in your browser
- Extension settings (browser local storage): your sign-in key, email, model choices, read mode, last known balance, the credit packs on sale, and small counters that decide when to show the invite and rating prompts. Signing out clears the key and email. Your Discreet mode choice (on or off, and how long the answer stays on the toolbar icon) is kept in the browser's synced extension storage, so it follows your browser profile if you use your browser's sync.
- Answer history (browser session storage): the last 25 answers (answer, confidence, reason, model, credits used, and the tab title). It is kept only until the browser closes, or until you choose "Clear history". Page text and screenshots are not kept.
Who processes data for us
- Anthropic (United States) — receives the question content (text or screenshot) to generate answers. Under Anthropic's commercial terms, this content is not used to train its models.
- Stripe (United States) — takes payment on its own hosted page as merchant of record (it calculates and pays the sales tax or VAT on your purchase). We pass it your email address and the pack you chose; it collects your card details, name and billing address under its own privacy policy, and we never see the card details.
- Resend (United States) — delivers our sign-in emails, so it receives your email address and the message.
- Vercel (United States, with a global edge network) — hosts the website and API, so requests (including IP addresses) pass through it.
- Neon (United States, AWS US East region) — hosts the database that holds the account data listed above.
These providers process data on our behalf and may use it only to provide their service to us. If you use the service from outside the United States, your information is transferred to and processed in the United States. Where the law requires a safeguard for that transfer, we rely on each provider's Standard Contractual Clauses or its certification under the EU–U.S. Data Privacy Framework.
The site loads no advertising or analytics scripts. We do not sell your personal information, and we do not share it for cross-context behavioral advertising or use it for targeted advertising, as those terms are defined under California and other U.S. state privacy laws.
How long we keep it
- Sign-in codes and links expire after 10 and 30 minutes, and website sessions after 30 days. Expired sessions, codes and links are deleted automatically, in small batches whenever someone signs in, once they have been expired for more than 7 days. So an expired record can remain for a little over 7 days, and longer if nobody signs in during that time.
- The credit ledger and administrator audit log are append-only by design: our system does not edit or delete their rows. Account records are kept while your account exists. Within 30 days after you ask us to close it, we delete your email address, sign-in records, your sign-up IP address, any pending invites for or from you, and the IP addresses linked to your usage; free-trial records keep only a one-way hash of your email (plus, if the trial was in the last 30 days, the IP address it came from), so the one-trial-per-person limit still works; usage records (model, tokens, cost and any Right/Wrong flag, never question content) are kept for cost accounting, no longer linked to you. Purchase, refund and credit ledger records are kept for 7 years after the transaction, because tax and accounting law requires it; after the account is closed they are no longer linked to your email address.
- Question content is not kept by us (see above).
Your choices and deleting your data
You can sign out in the extension (this revokes that browser's key), or press "Sign out every browser" on your account page to revoke every key and website session at once. To see, correct or delete your data, or to close your account, email support@whatstheanswer.app from the address on the account. We will reply within 30 days. Some records (for example payment and ledger records) may need to be kept for legal or accounting reasons, and we'll tell you if so. Depending on where you live (for example the EU, the UK or California) the law may give you further rights over your data; we honor these requests for everyone, wherever they live.
Children
The service is not directed to children under 13, and we do not knowingly collect their data. If you are under 18, you may use it only with a parent's or guardian's permission. If you believe a child under 13 has given us data, email support@whatstheanswer.app and we will delete it.
Changes and contact
We may update this policy and will change the date above when we do. Questions: support@whatstheanswer.app.