Privacy policy.

What Remedy checks, and where it goes

Remedy only runs on the sites you’ve switched it on for, and never on banking, email, document, password manager, health or government sites. On those sites, as posts load, the extension sends to Remedy’s backend (hosted by Convex):

• The text of posts, with who posted them and, for replies, the post being replied to, so a reply is judged in context.
• The web addresses of images in posts. The AI provider fetches the image from that address to check it.
• A few still frames from videos (at most six per video), captured in your browser as the video plays.

The backend passes these to AI models through OpenRouter: a text model (Jev) and an image model (Gemma, an open model, run by hosting providers rather than by Google). Every request requires zero data retention, meaning the providers process it to give a verdict and don’t store it or use it for training, and only providers that don’t keep prompts for safety monitoring either are used. The backend doesn’t store the posts, images or frames either.

What the backend keeps is each verdict (the scores for each filter) under a SHA-256 fingerprint of the content and the filter wording. A fingerprint can’t be turned back into the post; it only lets Remedy recognize a post it has already checked, so it isn’t checked, or charged for, twice.

What stays on your device

• The list of posts Remedy removed, shown in the popup. It’s never sent anywhere.
• Your site lists and settings, which Chrome may sync between your own browsers through your Chrome sync, as it does for extension settings generally. Your site lists are never sent to Remedy.
• A random install ID, made when you install Remedy, which identifies this copy of the extension.

What Remedy stores on its servers

Your filter settings

Which filters you’ve switched on, how strict they are, and your own filter wording if you’ve written one, stored against your install ID so the backend can check posts against them.

Your account

If you sign in (needed for a plan), you sign in with Google. We receive your name, email address, profile picture link and Google account ID, and keep them, with a record of your sign-in sessions, to know which installs belong to you. We ask Google for nothing else.

Billing

Payments are handled by Stripe; your card details go to Stripe, never to us. From Stripe we keep your customer and subscription IDs, your plan, its status and renewal dates, your card’s brand and last four digits, and a card fingerprint Stripe provides (not your card number), used to allow one free trial per card. Stripe’s own use of your information is covered by Stripe’s privacy policy.

Usage

How much of your plan’s usage you’ve used each month: the cost of the AI checks and how many tokens they took, and any top-ups. Not what was checked.

How you heard about Remedy

If you answer the optional question at the end of setup, your answer (and, for “Somewhere else”, the few words you type), stored against your install ID, so we can tell which places bring people to Remedy.

Website analytics

This website (not the extension) uses Mixpanel to see how people use it: the pages you visit, where you came from (the referring site and campaign tags), clicks and scrolling, your device and browser, and an approximate location from your IP address. It keeps a random ID in your browser’s storage to connect your visits, and records sessions on the site with anything you type hidden. If you install Remedy, the welcome page links those visits to a one-way hash of the install, never your name or email.

Usage stats

Unless you switch it off in Remedy’s settings, the extension sends anonymous usage stats to Mixpanel: counts and clicks, such as how many posts were checked or removed in a day, which screens were opened, and the extension’s version. They’re tied to the random install ID, not to you, and never include what you see or write, or page addresses. The only site names in them are the well-known ones, like X or Reddit; any other site is sent as “other”. Mixpanel is told not to work out your location from your IP address.

Ads on our website

This website (getremedyapp.com), not the extension, uses X’s conversion pixel and Google’s tag to measure whether our ads on X and Google bring people to Remedy. When they’re on, X and Google are told when someone visits the site, clicks “Add to Chrome”, reaches the welcome page that opens after setup, or starts a plan. They can link that to the visitor’s X or Google account, as described in X’s privacy policy and how Google uses information from sites that use its services. The extension never sends anything to X, Google’s ad services or any other ad network.

It’s on for every visitor, except when your browser sends Global Privacy Control. You can turn it off for this browser: Turn ad measurement off in this browser

Separately, if you arrive from a tagged link (like an ad or a directory), the site remembers its campaign tags on your device for 30 days, so the “Add to Chrome” link can pass them to the Chrome Web Store. If you then start a plan, they’re saved with your subscription, so we can see which campaigns bring subscribers. They’re also part of the site’s own visit counts below, and aren’t sent anywhere else.

The site also keeps its own visit counts on our servers: how many visits arrive at a page from elsewhere, and how many “Add to Chrome” or “Email me the link” clicks there are, by the campaign tags or referring website and the kind of device (a computer that can install Chrome extensions, another computer, or a phone). They’re totals per day, with no cookie, ID or IP address, so nothing in them points to you, and they’re kept for a year.

If you remove the extension, Chrome opens a page here asking why. That page has no ad tags and isn’t counted. It sends only the reason you pick, any note you choose to write (we remove anything that looks like an email address or phone number), and the extension’s version and install type, with nothing that identifies you. Answers are kept for a year.

What we don’t do

• We don’t sell or rent your information, or use what Remedy sees for advertising.
• The extension doesn’t read your messages or browsing history, track you across sites, or share what you see with advertisers.
• We don’t use what you see to train AI models, and neither do the model providers.

Remedy’s use of information received from Chrome follows the Chrome Web Store User Data Policy, including its Limited Use requirements.

Who else handles it

• Convex hosts Remedy’s backend and database.
• OpenRouter, and the model providers it routes to, check posts under zero data retention.
• Google handles sign-in.
• Stripe handles payments.
• Mixpanel receives the extension’s anonymous usage stats, if they’re on, and the website’s analytics.
• X and Google receive ad-measurement events from our website (not the extension), if they’re on.

We may also disclose information when the law requires it.

How long it’s kept

Verdicts are kept while they’re useful for recognizing posts already checked. Settings, usage and account details are kept while you use Remedy and deleted when you ask us to delete your account. Billing records are kept as long as tax and accounting law requires.

Your choices

• Switch Remedy off for any site, pause it, or turn off usage stats, in the extension.
• Sign out at any time; your plan stays with your account.
• Uninstalling Remedy deletes everything it kept in your browser. To delete your account and what’s stored with it, or to get a copy of it, email support@getremedyapp.com from your account’s address.

Children

Remedy isn’t meant for children under 13, and we don’t knowingly collect information from them.

Changes

If this policy changes, we’ll update it here and change the date at the top. For a significant change, we’ll tell you in the extension or by email before it takes effect.

Contact

Questions about privacy: support@getremedyapp.com.