Social Response Agent
Privacy Policy
Updated October 11, 2026 · Version 2026-10-11-v1.3
About this service
The first-five customer pilot supports one business, one user and one eligible Facebook Page. It prepares comment-reply drafts for customer review; automatic replies, teammate access, Instagram, direct messages and additional Pages are not included. Separately enabled founder, legacy and restricted-preview workflows may process Facebook and Instagram comments, supported direct messages, YouTube or TikTok comments when the required platform access exists. Private-message keyword campaigns are a founder preview and are not available in customer workspaces until provider access and real delivery acceptance are verified. When one of those restricted workflows is enabled, we store the settings, platform identifiers, content and attempt records needed to operate it and prevent duplicate actions. Test workspaces are separate from connected social accounts.
Customer accounts and email choices
When email registration is activated, Auth0 handles your password, email verification and recovery. We store your verified email, display name, an opaque identity identifier and hashed session identifiers. Customer sessions last up to 12 hours; you can sign out all devices from your account. Connecting Facebook is a separate authorization step.
Team invitations are not included in the first-five one-user pilot. If team access is separately enabled for a legacy or future workspace, an owner can invite a teammate by verified email. An accepted teammate can see the information allowed by that workspace role, and the owner can remove access. Invitation links expire after seven days, and stored invitation tokens are hashed. We keep the invited email and membership record to administer access.
Weekly comment summaries, marketing emails and onboarding messages are separate optional choices, off by default. We record the choice, consent text version and time. If you separately opt in, this account may receive up to three event-based onboarding messages: a welcome, a notice when comments are ready and a notice when Brand Voice is ready. You can stop these emails using their unsubscribe link. Resend processes onboarding and report delivery when enabled. Reports contain aggregate counts from saved records, not private messages. Recipient-bearing queued report payloads are cleared after 30 days when the email worker runs. Unsubscribe links change only the selected email purpose. Delivery failures or complaints can pause email.
Deleting a customer account revokes app sessions and erases its email, preferences and queued reports. Minimal opaque identity and workspace identifiers remain to prevent deleted accounts and old sessions from returning and to track deletion. Hosted identity erasure and retained billing records require provider review; the deletion receipt remains under review until resolved.
Google Reviews and LinkedIn
These integrations are in development. If enabled for an approved account, the following handling applies. Connections require platform approval and your authorization. Google Business Profile reviews can be imported for review, sent to OpenAI to draft a response when you request it, and answered after you approve the text. Review content and drafts are temporary, with a maximum 30-day cache. We keep encrypted access credentials until you disconnect or delete your account.
LinkedIn Company Page comments are displayed for manual replies. Incoming LinkedIn comments are not used for AI reply generation or voice training. Cached comment text expires after 48 hours. Opaque identifiers may remain to prevent duplicate replies. You can disconnect either platform from its channel controls.
Test workspaces
The test workspace stores the sample business name, business facts, reply tone, draft edits and sample hide or send state you enter on our server. Please use sample information only. A secure browser cookie allows this browser to reopen the workspace; it does not verify your identity or sign you into a real social account. The public sample does not store a selected plan or simulated billing state. We do not collect card details or send test content to Meta, Stripe or an AI service.
Access expires 45 days after creation or the last saved change. Expired test records are deleted when a new test workspace is created. You can delete your workspace immediately using Start over. Hourly request counts and a rotating hash derived from the client IP limit automated creation; raw IP addresses are not saved in these records. Old test rate-limit records are removed on subsequent creation requests.
AI website helper
When you send a question through the website chat, your question and recent conversation are sent to OpenAI to generate an answer. The conversation stays in page memory and is not saved as a chat transcript in our database. New chat clears the conversation from this page; reloading also clears it. Avoid entering passwords, payment details or private customer information. OpenAI may retain processing records under its applicable service terms. The chat does not subscribe you to marketing emails or access your social accounts.
To limit automated requests, we store hourly request counts with a rotating hash derived from the client IP. Raw IP addresses are not saved in those counters. Old chat rate counters are removed on subsequent chat requests after approximately 24 hours. The email option opens your mail app; a message is sent only when you send it there.
Previous pilot applications
The application form is closed. Previously submitted contact details and consent records remain available only to the project owner for the original application purpose. Request correction or deletion at hello@socialresponseagent.com. An application did not create a subscription or newsletter signup.
Information processed
When a connected platform returns a comment or sends a comment event, the service may process the comment text, platform-provided comment and post identifiers, limited public author information made available by the platform, the related post context, timestamps, and the reply decision. It does not request passwords or information outside the permissions granted through the connected platform. When you explicitly enable messaging, we also store incoming message text, participant and message identifiers, timestamps, your reply drafts and delivery status. Private message replies are manually reviewed and sent; message text is not sent to OpenAI in this workflow. With ads access, we read ad identifiers and linked post comments to build your review queue. Payment card details are handled by Stripe when test checkout is configured, not stored by this app.
How information is used
Information is used to understand comments, draft or publish appropriate replies, prevent duplicate responses, enforce safety rules and rate limits, troubleshoot the service, and maintain an audit record. Information is not sold or used for third-party advertising. Ad-comment import is a founder preview and is not available in customer workspaces until provider access and real-account acceptance are verified.
Service providers
The service relies on Meta, TikTok and YouTube to provide comments and post context, OpenAI to help classify comments and draft replies, and secure cloud infrastructure to run the application and store operational records. These providers process data only as needed to deliver their services and under their own applicable terms and privacy commitments.
Retention and security
Except where the shorter platform-specific periods below apply, operational records, including enabled messaging conversations, remain until you request deletion or an applicable retention process removes them. The YouTube retention and revocation rules below take precedence for YouTube API data. Deleting your workspace removes attributable records and revokes stored access. Minimal deletion receipts and revocation markers remain to prevent data from being recreated. We also retain your platform account identifier and an eligibility timestamp to prevent repeated free trials after deletion; this record contains no comments, messages or access tokens. Unresolved historical records or billing reconciliation are clearly reported for review. Operational records are used to run, review, secure, and improve the comment assistant. Access credentials are stored as protected secrets, and reasonable technical measures are used to limit unauthorized access. No internet service can guarantee absolute security.
Your choices and deletion
You may delete your comment directly on the original platform. To ask whether the service holds information connected to your comment, or to request its deletion, email hello@socialresponseagent.com. Please include the Page post or comment link so the request can be located.
YouTube and Google data
This app uses YouTube API Services. With your Google authorization, we access and store your channel identifier and name, video identifiers, titles and descriptions, comment and reply text, public author names and identifiers, timestamps, and reply status. We use this information to display your comment queue, prepare relevant replies, check for duplicate replies, publish replies you approve or authorize through your settings, and troubleshoot delivery.
YouTube video titles, descriptions, comment text and public author information are sent to OpenAI to classify comments and create reply drafts for the channel owner’s requested workflows. AI drafts and confidence judgments are generated by this app, not YouTube. Authorized teammates can access channel data within their workspace role. Cloud infrastructure providers store and process records to operate the service. We do not sell YouTube API data or use it for third-party advertising. Google access and refresh tokens are encrypted and used to maintain the authorized connection; we do not collect your Google password.
Saved YouTube comments, drafts and related API-derived records are removed by the 30-day retention cleanup. Connection information is refreshed while the channel is in use; stale connections and their saved channel data are removed by the retention cleanup. These YouTube-specific limits override the general retention description above.
To revoke access through SRA, sign in as the workspace owner, open YouTube, select your channel, expand “Disconnect and delete saved YouTube data” and confirm “Disconnect and delete saved data”. A successful request revokes the Google token and deletes saved channel data immediately. If an error appears, retry or contact hello@socialresponseagent.com; in-app revocation requests must be completed within seven calendar days.
You can also revoke SRA’s access through Google security settings. We remove associated saved data when revoked authorization is detected, with deletion required within 30 calendar days of that revocation. Removing data from SRA does not delete comments or replies already published on YouTube.
You can request deletion or raise a privacy question or complaint at hello@socialresponseagent.com. Include the channel or comment URL so we can locate the records; never send passwords or tokens. See our data deletion instructions, the Google Privacy Policy and YouTube Terms of Service.
Updates and contact
This policy may be updated as the service changes. Questions about this policy or the service can be sent to hello@socialresponseagent.com.
