Privacy Policy
Last updated: 2026-09-03 (test operation) · 한국어
1. Information we collect
- Email and name from Google sign-in (to identify your account)
- Your YouTube subscription list, read through the YouTube Data API, and the public information of those channels (title, description, recent upload titles, subscriber count, thumbnail, country, topic categories)
We do not read watch history, comments or likes. The only permission requested is youtube.readonly; we never add or remove subscriptions on your behalf.
2. How we use it
Only to categorize your subscribed channels into a taste code and interest tags, and to show shared interests and recommended channels with other users. The taste code, categories and tags are chchu’s own analysis, not data provided by YouTube.
3. Retention and deletion
- Your subscription list (authorized data) is deleted immediately when you disconnect the YouTube account or delete your account (“Delete account” at the bottom of the dashboard). Account deletion also erases your email, name, recommended channels and profile (YouTube API Services Terms III.D.2.3.a — within 7 days).
- If you revoke access from your Google Account settings instead, the connection and subscription data are deleted within 7 days.
- Public channel information is refreshed or deleted every 30 days (III.E.4.d).
- OAuth tokens are stored encrypted; on disconnect or account deletion we send a revocation request to Google and delete them.
4. Third parties
Channel categorization uses an external language-model API (Google Gemini via OpenRouter). Only public channel information (title, description, recent upload titles) is sent — never your email, your full subscription list or tokens. The API is used under terms where request data is not used for model training. We do not otherwise share or sell data.
5. Google API Services User Data Policy (Limited Use)
chchu’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We also comply with the YouTube Terms of Service and the Google Privacy Policy. You can also revoke access at the Google Account permissions page.
6. How we protect your data
Information received from your Google account (email, name, subscription list, OAuth tokens) is protected as follows.
- Encryption in transit: all traffic between your browser and our servers, and between our servers and Google APIs, is sent over HTTPS (TLS) only.
- Encryption at rest: OAuth access and refresh tokens are encrypted on the server with symmetric authenticated encryption (AES-128-CBC + HMAC, Fernet) before being written to the database; they are never stored in plain text. The encryption key is kept only as a server environment variable, separate from the database.
- Access control: the database lives on an internal network that is not reachable from the internet, and each user’s data can only be read through that user’s own signed session (JWT). The operator dashboard is restricted to designated admin accounts and does not expose any individual user’s subscription list or tokens.
- Data minimization: we request a single read-only scope and delete data without delay after the periods in §3, on disconnect, or on account deletion.
- Incident response: if we become aware of a data breach, we notify affected users by email without undue delay, ask Google to revoke the affected tokens, and delete them.
7. Cookies and device storage
chchu places cookies and browser local storage (localStorage) on your device only for the purposes below. We use no advertising or tracking cookies and no third-party analytics scripts.
- Sign-in session cookie (
chchu.session-token, httpOnly): keeps you signed in; removed on sign-out or expiry. During sign-in, Auth.js briefly sets CSRF and callback protection cookies. - Language cookie (
lang, 1 year): remembers your display language. - Local storage: display preferences such as dark mode (
theme), sidebar collapse (sidebar) and an admin-panel collapse state. These stay on your device and are never sent to our servers. - Our CDN/proxy (Cloudflare) in front of the site may set cookies for security and operational purposes.
Clearing cookies and site data in your browser signs you out and resets display preferences; it does not affect data held on our servers. We never store your subscription list, email or tokens in these browser storages.