Privacy.

Workspace data

We store account identifiers, workspace membership, topics, scoring configuration, review decisions, billing state and reply records needed to operate the product. We also keep what you told us when you set the workspace up, any message you send us through the support form, a record of the analysis run for you and the notices we sent, and the follower counts we sample to estimate what a reply earned. Tenant access is fenced by workspace membership.

Public conversation data

Reply.Quest processes public X posts that match your topics. We keep the post, the context needed to explain why a signal was surfaced, and the full record our data provider returned for it, so a reply can be connected to later measurement.

Connected X accounts

The optional X connection requests scopes for reading tweets and users, posting replies, and offline token refresh. X asks you to approve them and you may approve only some, so Reply.Quest stores what actually came back and acts on that: Settings calls the connection "Publishing enabled" only where the posting permission was granted, and "Read-only access" otherwise. We asked for posting permission so a reply could one day be sent from here. No screen in Reply.Quest does that today: you write the reply here and send it on X, and nothing is posted automatically. Your tokens are encrypted at rest and are never sent to your browser.

Measurement

Measured X metrics remain separate from modeled follow estimates. Results labels which is which. Open a single reply and its impressions say which measurement they came from, beside a history of every capture and its source.

Service providers and retention

Infrastructure, payments, email delivery and X data providers each receive the part of your data their role needs. A content analysis service receives the most, so it is listed in full rather than as a category. To score a post, it is sent that post along with the rubric and the negative signals you wrote. To draft angles, it is sent the post, the conversation around it, the author's other recent public posts, and the positioning and goals you gave us. To polish a reply, it is sent your draft, the post, the angle you picked and a sample of your own past replies. It is also sent the answers you give while setting a workspace up, so a first draft of that workspace can be written, and the replied, skipped and vetoed decisions you make in review, so changes to your scoring can be proposed to you.

Workspace owners can disconnect X and delete the workspace from Settings. Deleting removes that workspace's topics, signals, replies, measurements and team access, and disconnects any X account connected to it. Payment, credit, checkout, subscription, purchased Pay As You Go window, collection-attempt, and Stripe event history is kept with the workspace link detached, so receipts, refunds, card disputes, and support questions can still be answered afterwards. Two other things are kept as well: what you told us when you set the workspace up, and any message you sent us through the support form. Those stay linked to your account rather than to the workspace. Nothing is removed after a set period, so deleting the workspace is how its other data goes. Deleting a workspace does not delete your Reply.Quest account, and Reply.Quest has no self-service data export.

Questions

Review the practical controls on the help page. This notice was last updated August 12, 2026. Documentation owner: Reply.Quest Support.