Privacy Policy
Last updated: May 28, 2026
RespondEngage ("RespondEngage", "we", "us") is an audience-intelligence tool for YouTube creators. This Privacy Policy explains what information we collect when you connect your YouTube channel and use the product, how we use it, who we share it with, and the choices you have. By using RespondEngage you agree to this policy.
Who this policy applies to
This policy applies to creators who sign in to RespondEngage and connect a YouTube channel they own or are authorized to manage. We only access data for channels that have explicitly granted us access through Google's OAuth consent screen.
Information we collect
We collect the following categories of information:
- Account information: when you sign in we receive your name, email address and profile image from our authentication provider (Clerk).
- YouTube channel and video metadata: the connected channel's identity, and the titles, descriptions, thumbnails and publication dates of its videos.
- Comments: the text, author display name, author channel id, timestamps and reply structure of comments on the connected channel's videos.
- Authorization tokens: the OAuth access and refresh tokens issued by Google, which we store encrypted at rest.
- Derived data: classifications we compute for each comment (intent, sentiment, priority, risk and confidence) and the reply suggestions we generate.
- Technical data: basic logs and error reports needed to operate and secure the service.
YouTube and Google API data (Limited Use)
RespondEngage uses YouTube API Services. By connecting your channel you also agree to the YouTube Terms of Service (https://www.youtube.com/t/terms) and acknowledge the Google Privacy Policy (https://policies.google.com/privacy).
RespondEngage's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy (https://developers.google.com/terms/api-services-user-data-policy), including the Limited Use requirements.
We request only the scopes we need: read access to your channel's videos and comments, and the youtube.force-ssl scope, which is required to post, edit or delete replies on your behalf and to access captions. We do not use Google user data for advertising, we do not sell it, and we do not use it to build profiles unrelated to the service.
You can revoke RespondEngage's access at any time from your Google Account permissions page (https://myaccount.google.com/permissions).
How we use information
We use the information we collect to:
- classify your channel's comments and surface insights (themes, sentiment, priority, risk);
- generate suggested replies, and — only when you enable it — post replies on your behalf;
- operate, secure, debug and improve the service;
- communicate with you about your account.
We do not use your YouTube data for advertising or for any purpose unrelated to providing RespondEngage to you.
AI processing
To classify comments and generate reply suggestions, RespondEngage sends comment text and related context to third-party large-language-model (LLM) providers (currently Anthropic, and optionally Google or OpenAI depending on configuration). These providers process the data only to return a result to us and, under their API terms, do not use data submitted through their APIs to train their models. We send the minimum context needed for the task.
How we share information
We do not sell your personal information. We share data only with service providers (subprocessors) that help us run RespondEngage, under contractual confidentiality and data-protection obligations:
- Clerk — authentication and account management.
- Neon — managed PostgreSQL database.
- Vercel — application hosting.
- Inngest — background job processing.
- Anthropic, Google and/or OpenAI — LLM processing of comment text.
- Sentry — error monitoring.
- Google / YouTube — to read and, when you enable it, write comments on your behalf.
We may also disclose information if required by law or to protect the rights, safety and security of RespondEngage and its users.
Data retention
We keep your data only as long as it's needed to provide RespondEngage. Stored YouTube comment data is kept fresh under the YouTube API Services Developer Policies: a comment's text and author identity are deleted within 30 days of the comment being resolved (replied to, ignored, or otherwise handled), and comments still awaiting your action are periodically refreshed so they stay current. We retain long-term only derived analysis (classifications and insights) and the identifiers needed to re-fetch a comment from YouTube on demand. When you disconnect a channel, we immediately stop processing it and revoke the stored access token; the channel's data is then deleted after a 14-day grace period, during which you can reconnect to cancel deletion — or delete everything immediately. When you delete your account, we delete your data, except where we are required to retain limited records to comply with legal obligations. You can also ask us to delete your data at any time (see Contact).
Your choices and rights
You can:
- disconnect your YouTube channel from within RespondEngage at any time;
- revoke RespondEngage's access from your Google Account permissions page (https://myaccount.google.com/permissions);
- request access to, correction of, or deletion of your personal data by contacting us.
Depending on where you live, you may have additional rights under laws such as the GDPR or the LGPD.
Security
We protect your data with industry-standard measures. OAuth tokens are encrypted at rest, access is restricted, and traffic is served over HTTPS. No method of transmission or storage is perfectly secure, but we work to protect your information and to address vulnerabilities promptly.
Changes to this policy
We may update this policy from time to time. When we make material changes we will update the date at the top of this page and, where appropriate, notify you.
Contact
For privacy questions or to exercise your rights, contact us at suporte@respondengage.com.