Privacy Policy

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.

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.

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).

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.

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 commercial API terms, do not use data submitted through their APIs to train their models. Google Gemini is enabled only for its Paid Services, with Cloud Billing confirmed. We send the minimum context needed for the task.

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.
• SendKit — transactional email (for example, notifying you that a channel was disconnected).
• Stripe — subscription payments. Stripe receives your billing details directly; we never store card numbers.
• 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.

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: instead of deleting a comment after a fixed period, we re-read it from YouTube at least every 30 days, updating its text and its author identity so that what we store is what YouTube shows. A comment leaves RespondEngage when it leaves YouTube: if its author deletes it, or the video stops being public, we blank the text and the author identity on the next check, keeping only the derived analysis and the identifier needed to fetch it again. We retain long-term the derived analysis (classifications and insights), the replies we generated for you, and comment identifiers. If a channel goes three months with no sign of an active relationship, we email you and, after that notice, delete that channel's stored archive of unanswered comments — the account, settings, persona, knowledge base and reply history remain. When you disconnect a channel, we immediately stop processing it and revoke our access with Google; the channel's data — including stored authorization tokens — is then deleted after a 14-day grace period, during which you can reconnect to cancel the deletion. You can also choose to delete everything immediately, without waiting for the grace period. To close your account entirely, write to the address in the Contact section and we will delete your data, except where we must retain limited records to meet legal obligations. You can request deletion of your data at any time through the same channel.

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.

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.

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.

For privacy questions or to exercise your rights, contact us at suporte@respondengage.com.