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 and LinkedIn posts that match your topics. We keep the post, the context needed to explain why a conversation was surfaced, and the public source record returned for it, so a reply can be connected to later results. If you share your public LinkedIn profile or company page during setup, we also read its public details and a limited set of recent posts to suggest topics. We keep the page address without its tracking parameters with your setup answers, not the complete page response.

Connected social 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.

LinkedIn account connection and direct posting are not currently enabled. Copy Reply and Open on LinkedIn keep the final send in LinkedIn. If account connection is enabled later, Reply.Quest will store only the approved account permission, encrypt its access material, and require your confirmation for each exact public reply. It will never post automatically.

Measurement

Measured X results remain separate from modeled follow estimates. Results labels which is which. Open a single X reply and its impressions say which measurement they came from, beside a history of every capture and its source. Optional LinkedIn reply tracking reports supported public reaction counts and replies to your reply. It does not report unavailable impressions, profile views, clicks, private messages, follows, or revenue attribution as zero.

Service providers and retention

Infrastructure, payments, email delivery and public-conversation services 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, plus public profile or company-page evidence you choose to share there, 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 connected social accounts and delete the workspace from Settings. Deleting removes that workspace's topics, signals, replies, measurements and team access, and disconnects any social 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. Collected X and LinkedIn conversations have no age-based expiration. Source corrections and removals still remove stale source material and the records derived from it. 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 13, 2026. Documentation owner: Reply.Quest Support.