Privacy Policy

Seya — Chrome Extension · Last updated: February 25, 2026

What Seya Does

Seya is a Chrome extension that generates AI-powered knowledge extracts from YouTube videos and delivers them to your Slack or Telegram.

Data We Collect

When you click "Extract," the following data is sent to our servers:

• Video information — URL, title, channel name, and timestamp of the video you are watching
• Google account info — email address and display name (used for authentication only)
• Delivery preferences — your chosen delivery channel (Slack or Telegram) and the associated webhook URL or chat ID

We do not collect browsing history, video watch history, or any data from pages other than the video you explicitly choose to extract.

How We Use Your Data

• Authentication — Your Google account is used solely to identify you and protect access to your preferences. We use Supabase for secure authentication.
• Extraction — Video URL is sent to a transcript service, then the transcript is processed by OpenAI to generate a structured extract.
• Delivery — The extract is sent to your configured Slack channel or Telegram chat.
• Logging — We store a log of extraction requests (video URL, status, timestamp) tied to your user ID for debugging purposes.

Third-Party Services

Seya relies on the following third-party services to function:

• Google — Authentication (OAuth 2.0 sign-in)
• Supabase — User authentication, preference storage, and request logging
• Apify — YouTube video transcript extraction
• OpenAI — AI-powered knowledge extraction
• n8n — Workflow automation (orchestrates the extraction pipeline)
• Slack / Telegram — Extract delivery to your chosen channel

Each service processes data according to its own privacy policy. We recommend reviewing their policies if you have concerns.

Data Retention

• Preferences (delivery channel, webhook URL, chat ID) are stored until you delete them or uninstall the extension.
• Extraction logs (video URL, status) are retained for debugging and may be periodically purged.
• Video transcripts and extracts are not stored permanently — they are processed in real-time and delivered to your channel.

Data Security

• All communication uses HTTPS encryption.
• Authentication tokens are stored locally in your browser's secure extension storage.
• Database access is protected by Row Level Security — you can only access your own data.
• No passwords are stored — authentication is handled entirely through Google Sign-In.

Your Rights

• Access — You can view your delivery preferences on the extension's settings page.
• Modification — You can change your delivery channel and configuration at any time.
• Deletion — You can sign out and uninstall the extension to remove your local data. To request deletion of server-side data, contact us at the email below.
• Revocation — You can revoke Google Sign-In access from your Google Account permissions page.

Permissions Explained

• activeTab — Allows the extension to read the current YouTube page URL and title when you click the extract button. No other tabs or pages are accessed.
• storage — Stores your authentication session and preferences locally in the browser.
• identity — Enables Google Sign-In via Chrome's built-in authentication flow.
• Host permissions (youtube.com) — Required to inject the floating extract button on YouTube video pages.
• Host permissions (supabase.co) — Required to communicate with the authentication and preference storage backend.

Changes to This Policy

We may update this privacy policy from time to time. The "Last updated" date at the top will reflect the most recent revision.