LAST UPDATED: 2 SEPTEMBER 2026

Privacy Policy

Signal is designed so that personal browsing records stay in your Chrome profile while the hosted service processes only the YouTube videos for which the extension requests an analysis.

Information Signal handles

Account information

When you sign in, Firebase Authentication processes your Google account identifier, email address, display name, profile image, authentication timestamps, and security tokens. Signal uses this information to confirm that your account is invited and to let you access the private beta.

YouTube analysis requests

For a video that Signal analyzes, the extension sends the hosted service the public YouTube video identifier and URL, title, channel name, and thumbnail URL. The service retrieves an available public caption track and processes transcript text, title, and thumbnail to produce the analysis.

Optional Chrome history

Signal asks for Chrome history permission only when you choose to import a report. The extension searches locally for YouTube watch-page visits from the preceding 30 days, filters and deduplicates them in Chrome, and requests analysis for up to 350 videos. Signal does not upload your full Chrome history or non-YouTube history.

Local product data

Recommendations shown, clicks, active watch seconds, score-detail opens, feedback, report state, and personal knowledge signals remain in chrome.storage.local in your Chrome profile unless you export them. You can delete this local data from Signal settings.

Service providers

Signal uses Google Firebase for authentication and hosting, Google Cloud for the API and stored analysis cache, Google Gemini for primary analysis, OpenRouter as a capacity fallback, and Supadata as an optional public-caption fallback. These providers receive only the information needed for the relevant request. Signal does not sell personal information or use it for advertising.

Storage and retention

The service stores reusable analyses and retrieved public captions so the same public video does not need to be processed repeatedly. A bounded operator audit may retain prompts, provider responses, usage counts, and public video-derived content for reliability and cost review. Authentication records remain in Firebase until the account is removed. Infrastructure backups are retained for up to 14 days. Local browser data remains until you delete the extension data or uninstall the extension.

Security and access

Functional API requests require a valid, short-lived Firebase ID token from a verified and invited Google account. Model and infrastructure credentials are kept in Google Secret Manager and are not included in the extension. No system can be guaranteed completely secure.

Your choices

You may decline optional Chrome history access and continue using live recommendations. You may export or delete local Signal data from Settings, sign out at any time, or request removal from the beta and deletion of your Firebase account through the support channel.

Children

The beta is not directed to children under 13, and testers must be old enough to consent to these practices in their jurisdiction.

Changes and contact

Material changes will be communicated to active beta testers. For privacy questions or deletion requests, contact signal-support@googlegroups.com.