Privacy policy
Your data stays in your browser.
Replydex is a Chrome extension that helps you find LinkedIn and Threads posts to comment on, and walks you through them so you can write comments and replies yourself. This policy explains what data Replydex handles and where it goes.
The short version
- The Replydex extension has no server and no account system, and it doesn't collect analytics. (This website uses Google Analytics; see below.)
- Everything it stores stays in your browser, in Chrome's extension storage on your device.
- The only data that leaves your browser is sent to Anthropic, and only when you click Draft and have added your own Anthropic API key.
- We don't sell, share or rent your data, and we never see it.
What Replydex stores on your device
| Data | Why |
|---|---|
| Your topics and search settings | So you can run your saved searches |
| Your LinkedIn and Threads handles | To hide your own posts and recognise your own comments |
| Posts you've handled (post IDs, author names and profile links, and the time) | So you aren't shown the same post twice, and for the author cooldown |
| Authors you star or mute | To rank their posts higher, or hide them |
| The current queue (post text, author, engagement counts) | So your session survives closing the panel |
| Your recent comments and replies (up to 30 per platform) | As style examples for AI drafts |
| Your Anthropic API key, if you add one | To request AI drafts |
This data stays in chrome.storage.local until you clear it. You can remove it with Clear history in the side panel, by removing your API key in Settings, or by uninstalling the extension.
What Replydex reads
When you click Find posts, Replydex opens LinkedIn or Threads in your browser and reads the search results and post pages there, as you would see them yourself. It reads post text, author names, timestamps and engagement counts, and checks whether you've already reacted or commented. It never posts, comments, likes, follows or messages anyone for you.
What is sent to third parties
Anthropic (optional). Only when you click Draft in the side panel, Replydex sends the following to Anthropic's API (api.anthropic.com) using your own API key:
- the post's text, and its author's name and headline
- a few of the post's existing comments
- your writing-style notes from Settings
- up to 8 of your recent comments or replies, as style examples
Replydex can only contact Anthropic after you allow Chrome's optional permission for api.anthropic.com, which it asks for when you save an API key.
Anthropic processes this under its own terms and privacy policy. Replydex sends nothing else, to Anthropic or anyone else.
LinkedIn and Meta (Threads). Replydex works inside your normal signed-in browser session on those sites. Your use of them is covered by their own terms and privacy policies.
This website
The Replydex extension has no analytics. This website, replydex.com, uses Google Tag Manager and Google Analytics to understand how visitors find and use the site: pages viewed, how you arrived, and your approximate location, device and browser. These analytics only run if you click Accept analytics in the cookie banner. If you decline or ignore it, no Google script loads and no analytics cookies are set. You can change your choice any time with Cookie settings in the site footer. When accepted, Google sets cookies and processes the data under its own privacy policy. It's never used for advertising, and your choice doesn't affect the extension.
Limited use
The use of information received by Replydex adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.
Replydex's use of the data above is limited to providing its single purpose: helping you find posts and write comments and replies. The data isn't used for advertising, isn't sold, and isn't transferred to anyone except Anthropic as described above. No person reads it, and it isn't used to determine creditworthiness or for lending.
Children
Replydex isn't directed at children under 16.
Changes
If this policy changes, we'll update the effective date above and describe the changes in the extension's changelog.