Privacy policy.
Remedy is a browser extension that filters your social feeds. To do that it has to look at what’s in them. This is exactly what it looks at, where that goes, and what’s kept.
The short version. Posts are checked by AI models run with zero data retention, so they aren’t stored or trained on. We keep a one-way fingerprint of each post and its verdict, never the post itself. What was removed from your feed, and the sites you’ve picked, stay in your browser. We don’t sell your data or show ads.
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 (Google’s Gemini). 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. 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.
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, page addresses or site names. Mixpanel is told not to work out your location from your IP address.
What we don’t do
- We don’t sell or rent your information, or use it for advertising.
- We don’t read your posts, messages or browsing history, or track you across sites.
- 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 anonymous usage stats, 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.