Riposte is a LinkedIn engagement assistant for teams that runs inside Claude as an MCP connector. It watches public social media posts, ranks them by engagement velocity, and drafts replies that a human reviews and posts. This policy explains what data Riposte handles, why, and what your rights are.
The short version. We store your work email and name (for sign-in), the content your workspace creates (voice samples, tracked lists, engagement logs), cached public social media posts, usage metering, and a record of each visit to this website, without the IP address. We never ask for social media passwords, never post on anyone's behalf, never read private messages, and never sell data.
When you sign in, our authentication provider (Clerk) shares your name and work email address with us. We use these to match you to a seat in your team's workspace. Sign-in is OAuth 2.0 — we never see or store your password.
The same sign-in also opens the web dashboard at app.riposte.chat, where an admin can see the team, the lists and each tracked person, and change notes and list rules. There it is a browser session with Clerk rather than a connection from Claude; it reaches the same seat and the same workspace, and nothing on the dashboard is available to anyone without a seat.
A small number of workspaces created before OAuth was added still connect using a secret link containing a per-seat token. That token is the credential, so the link should be treated like a password. We are retiring this path; if your workspace uses one, we will move you to OAuth sign-in.
Riposte fetches publicly available posts, profiles, and comment threads via licensed third-party data providers — one per network, named in §4 — and caches them in our database so your feed loads quickly and repeat lookups don't re-fetch. We do not access private profiles, direct messages, or any content behind a login.
When you tell Riposte you posted a reply — or when the daily activity check described in §3 finds a comment of yours on a post by someone on your workspace’s watchlist — we store the comment text, the post it was on, and a link to the comment, so your engagement reports are about what actually happened. Each record notes whether you confirmed it or we detected it.
We meter tool calls, data-provider calls, and drafting tokens per seat and per workspace. This powers budgets, fair-use limits, and billing. Your workspace admin can see the same usage report we bill from.
When a page of this website is requested (riposte.chat and its guides, not the app), we keep a record of the visit, to see how much of our traffic comes from people, search engines, AI assistants and other automated software. A record holds the time; the page and the link it was opened with, minus the click identifiers that advertising and social platforms add; the page that linked to it, without its query; the browser's user agent and first language; the approximate location Vercel works out from the IP address (city, region and country); and the network the request came from (its number and owner, looked up in a public table). Each page also reports back once it has loaded, with the same details and whether the browser says it is automated, so a browser that ran the page can be told apart from software that only fetched it.
The IP address is used at the time of the visit for that network lookup, and to check visitors that say they are a known search engine, AI crawler or AI agent: against that company's published address lists, its network, a reverse DNS lookup, or the agent's published signing keys. It is not stored. We also check that a browser's request headers fit the browser it names, and keep only the result. Records are sent to, and stored by, a visitor-research service we use at mcval.org, hosted on Vercel like Riposte. We set no cookie for this, do not identify visitors, and do not combine these records with account data. You can stop your browser being counted at riposte.chat/_visits/me, which sets a cookie whose only purpose is to remember that choice.
We do not sell personal data, share it with advertisers, or use it for any purpose beyond operating Riposte.
| Provider | Purpose |
|---|---|
| Clerk | Authentication (OAuth 2.0 sign-in from Claude; the browser session on app.riposte.chat) |
| Supabase | Database (encrypted at rest) |
| Vercel | Application hosting, and storage of website visit records (§1) |
| Anthropic | AI draft generation and, on request, web search for target companies (API; not used for model training) |
| RapidAPI | Marketplace we call the social-data provider through |
Api G., publisher of the LinkedIn data API we use on RapidAPI (endpoint host linkedin-scraper-api-real-time-fast-affordable.p.rapidapi.com) | The licensed provider that retrieves public LinkedIn content. Configurable, so this page names the one in use; if we change provider we will update this page and the effective date. |
X Corp (api.x.com) | The X API, which retrieves public X content — a person’s public posts and replies, and their public profile and bio — for workspaces that have enabled X. We send it a public handle or the numeric id X assigns to it, and nothing else. Reached only once X is enabled for a workspace; until then no data goes to X. |
| Resend | Email delivery for the daily email. An email exists only for a person with a seat who has turned it on, and only on a day somebody is due; Resend then receives that person’s email address and the email’s content — the names of the tracked contacts it lists, why each is listed, and an excerpt of and link to each one’s public post. Those contacts did not opt in to anything: they are people the workspace already tracks, and their public posts are already processed as §1 describes; the email puts a few of them in front of one person who asked to be reminded |
| Sentry | Error monitoring. Receives error reports when something in Riposte breaks: the technical error, the tool or job name, and internal workspace/seat identifiers — never message content, drafts, or LinkedIn post data |
| GitHub | Source code hosting, and a manual fallback (run by hand, not on a schedule) that can trigger our refresh and sync endpoints; the schedule itself runs on Vercel |
Within your workspace, shared activity (contacts, engagement history, briefs) is visible to your teammates by design — that team awareness is the product. The contact watchlist is workspace-wide: it is shared by everyone on the team, not private to whoever added someone. Voice profiles are visible at workspace level too. A voice belongs to the person it sounds like: it can be changed by anyone set up to post as that person, or by a workspace admin, and deleted by whoever created it or an admin — a voice is somebody's own writing, and its sample comments are their own first-person experiences, so nobody can draft in a voice that is not theirs to speak in. Drafts are never written to Riposte's database — but they are produced by Anthropic's API and returned into your assistant conversation, so your host's retention policy and Anthropic's apply to them exactly as they do to the rest of that conversation.
Riposte processes publicly available social media content, which includes posts and profile details of people our customers choose to track. If you believe your public content is being processed and want it removed, contact us at the address below. We will remove your cached posts, your entry on any customer's watchlist, and your rows as a commenter on their posts — in every workspace that holds them, not just one. Three limits worth stating plainly, because we would rather be exact than reassuring. Where someone replied to a post and we did not capture a usable link to their profile, we hold a name and the text of the reply with nothing that identifies whose it is; we cannot single those out on request, and we will not guess, because guessing means deleting a stranger's words from a customer's record. We keep no suppression list, so if a customer tracks you again afterwards your public posts can be fetched afresh. And where a customer has recorded that they replied to one of your posts, that record is their own business activity, which we handle with them rather than delete unilaterally.
Depending on where you live (including under UK and EU GDPR), you may have the right to access, correct, export, or delete your personal data, and to lodge a complaint with a supervisory authority. Email us and we will respond within 30 days.
The riposte.chat website sets no analytics or advertising cookies. Signing in sets strictly necessary session cookies from our authentication provider; on app.riposte.chat that session cookie is what keeps you signed in to the dashboard, and there is nothing else.
Riposte is a business tool intended for users 18 and over. If we make material changes to this policy we will update this page and note the new effective date. Questions, or any request under this policy: hello@riposte.chat.