Privacy Policy

ReplyKit (the Chrome extension and the replykit.eu/app web app) is built and maintained by Frédéric Legrand. This policy covers the extension, the web app and the supporting services on replykit.eu and api.replykit.eu.

Questions, requests or complaints? Email contact@replykit.eu.

The extension adds a panel under the reply box on X (Twitter), LinkedIn and Reddit. The Reply button lets the model pick the angle; the Funny, Insight, Agree and Push back chips steer it; Polish rewrites a draft you've started. In an empty composer it suggests a new post instead. ReplyKit puts the drafts in front of you and you decide what to post. It doesn't post, like, follow or message for you.

On X, Opportunity Radar marks posts worth replying to. It works inside your browser (see section 4).

The web app does the same from a phone: you paste or share a post, pick a tone, and copy the draft back into the app yourself.

a) The post you ask ReplyKit to answer. Every generation, on every plan, goes through our server at api.replykit.eu, which forwards it to Anthropic's API (a Claude Sonnet model) with our own API key. There are no personal API keys. The request contains the post you're replying to and its author's handle, the posts above it in the thread with their authors' handles, what you wrote in the Writing Style box (your expertise, interests or voice), your draft when you use Polish, and your style settings (length, emojis, hashtags, thread). Our server uses your token to check and count your allowance. It doesn't pass your email or IP address to Anthropic. In the web app, the request contains the text you pasted or shared, the platform and the tone.

b) Prompt and reply logs. When the extension finishes a generation, it sends a copy to our server: the full instructions sent to Claude (which include the post, the thread, the handles, your Writing Style text and your draft), every draft Claude wrote, your plan (anonymous, free or Pro), the platform, the tone, your style settings including your Writing Style text, and the extension version. We store this in our database to see which prompts work and fix the ones that don't. The record has no email, account token or IP address, but the text itself can contain the handles in the thread and anything you wrote in your settings or draft.

For each of these, the developer also gets a Telegram message with the plan, platform and tone, the first 700 characters of the prompt and up to 1,500 characters of the reply, to check draft quality as it happens.

c) Feedback. The Feedback link in the reply panel and the feedback form in the popup send your message to the developer on Telegram, along with your plan, where you sent it from, the extension version and, from the panel, the platform and tone. If you're signed in, your account email is added so we can answer. If you're not, you can type an email for a reply. In the reply panel, an “Include this post” box (“and the drafts” once you've generated) is ticked by default. While it's ticked, the post on screen and up to five drafts are sent too; the Telegram message shows the first 800 characters of the post and 300 of each draft. Feedback isn't saved in our database. It stays in the Telegram chat.

d) Free use without an account. When you install the extension (or open the web app), it asks our server for a random trial token. We store that token with the IP address it was requested from, how many replies it has used today and when it was created and last used. The IP address lets us cap how many trial tokens one network can create in 24 hours.

e) Your account (free or Pro). To sign in, you enter your email and we send you a six-digit code through Resend. The code is stored with your email until it's used or replaced, and expires after 15 minutes. Your account record holds your email, plan and status, an account token (which the extension keeps and sends with each request), your usage count, when the account was created, last updated and upgraded to Pro and, for accounts opened through email sign-in, the IP address you signed in from. That IP address caps how many new free accounts one network can open in 24 hours. Each sign-in sends the developer a Telegram message with your email and plan. If a signup is blocked by that cap, the message also shows the IP address.

f) Pro billing. You pay on Stripe's checkout page. Stripe tells our server your email address and Stripe customer ID, which we store on your account to unlock Pro, reset your monthly count when you renew and open Stripe's billing portal for you. Your card details go to Stripe, not to us. The developer gets a Telegram message with your email when you subscribe.

g) Usage and cost records. For each generation, our server records the plan, the model, the number of tokens used and the extension version, with no user identifier.

h) Product analytics. The extension sends usage events to Google Analytics 4 through our server: things like “panel shown”, “reply generated”, “reply inserted”, “upgrade clicked” and “feedback sent”, with details such as platform, tone, plan and a Radar score. Each install gets a random ID created by the extension. The events contain no post text, drafts, email or account token. Our server sends them on to Google, so the request Google receives comes from our server, not your browser.

i) Errors and performance. Our server reports errors, request timings and usage metrics to Sentry (EU region). We configure it to leave out request bodies, cookies, authorization headers, IP-address headers and user details. The site's pages, including the web app, also report browser errors and performance to Sentry. Our host, Netlify, keeps request and function logs; our own log lines record errors and a few events, such as the email address when a Pro subscription starts.

j) The website and web app. replykit.eu, including this page and the web app, uses Google Analytics (which sets cookies) to count page views. The web app keeps your token and, once you sign in, your email in your browser's local storage. If you share a post into the web app from your phone's share menu, its text passes through our server once to reach the page (our code doesn't store or log it), then sits in the part of the page address after “#”, which is never sent to a server. The page clears it from the address as soon as it loads; a Google Analytics page view recorded in that moment could include it.

k) Uninstall survey. When you remove the extension, Chrome opens a Google Form asking why. Answering is optional, and what you type goes to Google Forms.

• Settings (Writing Style, default tone, style options, Radar options and target accounts) are saved in Chrome's synced storage, so Chrome can sync them to other browsers where you're signed in to Chrome. Your Writing Style text and style options are sent with each generation and logged as described above. The Radar options and target accounts aren't sent to us.
• Tokens and account details: your trial token, account token, email, plan and usage counters, in the extension's local storage.
• Recent replies: a short memory of the posts you answered and the draft you picked, at most 10, trimmed to the last 24 hours whenever a new one is saved. It isn't sent anywhere.
• Your stats: reply counts per tone and per day, shown in the popup.
• Opportunity Radar: on X, ReplyKit reads data X's own page has already downloaded to get post authors' handles, follower counts and verified status. It makes no extra requests to X and doesn't change X's requests. Those numbers and the IDs of posts you replied to are kept in local storage and aren't sent to us. We only get the analytics events above (for example, “Radar opened” with the number of posts, or a badge clicked with its score).

• Anthropic writes the replies (what's sent: 3a).
• Supabase hosts our database: trial tokens, accounts, sign-in codes, prompt logs and usage records.
• Netlify hosts the website and our server.
• Stripe handles Pro checkout, billing and the billing portal.
• Resend sends the sign-in code emails.
• Telegram delivers the developer's notifications: generated replies, feedback, sign-ins and new subscribers.
• Google runs Google Analytics (extension events and site page views) and the uninstall survey on Google Forms.
• Sentry receives error and performance reports.

Each of them has its own privacy policy and keeps data under its own terms. We don't sell your data or share it with advertisers.

• storage: to save your settings, tokens and local stats.
• alarms: to show a badge when your daily free replies are back.
• Access to x.com, twitter.com, linkedin.com and reddit.com: to show the panel and Radar and read the posts on those pages. Post text leaves your browser only when you generate a reply or include it in feedback.
• Access to api.replykit.eu: our server (plain cross-origin requests; the extension asks for no site permission on it).

The extension doesn't request access to other websites, your browsing history, downloads, bookmarks or files.

• Nothing in our database is deleted on a schedule. Prompt logs, usage records, trial tokens (with their IP address) and accounts (email, Stripe customer ID, signup IP address) are kept until they're deleted on request.
• Cancelling Pro marks your account as cancelled. It doesn't delete it.
• A sign-in code is deleted as soon as you enter a code, right or wrong. An unused code stays until you ask for a new one.
• Telegram messages stay in the developer's chat until they're deleted.
• Anthropic, Stripe, Google, Sentry, Netlify, Resend and Supabase keep data under their own policies.
• Uninstalling the extension deletes what it stored in Chrome. It doesn't delete anything on our server.

• Leave the Writing Style box empty if you don't want that text sent to Anthropic and logged.
• Untick “Include this post” before sending feedback from the reply panel.
• Manage or cancel Pro from the extension popup (Manage subscription opens Stripe's billing portal).
• Uninstall the extension to remove its data from your browser.
• Ask for a copy of your data, or for its deletion, by emailing contact@replykit.eu. Give the email of your account if you have one. Prompt logs aren't linked to an account, so to find yours we need something to search for, such as the text of a post you answered. If you are in the EU or UK, you have the rights granted by the GDPR / UK GDPR.

If this policy changes in a material way, the “Last updated” date at the top will move and a notice will be posted on this page. Continued use after a change means you accept the new version.

For privacy questions, data requests or anything else, email contact@replykit.eu.