Privacy Policy
Last updated October 9, 2026
This policy describes information handled by Watchlist's website and browser extension. It distinguishes information you publish from account and security information used to operate the service.
1. Account and profile information
Accounts use an email address, username, password handled by Supabase Auth, and email-confirmation/session information. Your email address and signup-security records are not part of public member listings. Public profiles can display your username, avatar, bio, selected title, backgrounds and badges, level, XP/progression, and rating activity.
Uploading an avatar makes that image accessible through the public profile-image storage bucket. Account deletion removes the uploaded image referenced by your profile when it matches Watchlist's storage naming rules, including when you have switched to a letter or preset avatar. Older replaced files, provider backups, and security or abuse-prevention records may remain. Contact us about remaining files. Avoid uploading private information or using a bio or username that reveals more than you want to publish.
2. Activity and content
We store ratings, reviews, lists and their contents/notes, submitted video information, and the activity needed for achievements and progression. Ratings, reviews, and public lists are community-facing and can appear with your username. A private list is not included in the public Lists browser; access remains subject to the service's authorization rules. Private does not mean hidden from the infrastructure or authorized administration needed to operate the service.
Social interactions include friend relationships and requests, blocks, notifications, profile reports, and direct messages. Direct messages store the message content, sender and recipient account identifiers, and creation time. Database access rules limit message reads to the sender and recipient; messages are not end-to-end encrypted. Authorized administration may access information when needed for security, abuse handling, support with your consent, or legal compliance.
Reports and support requests are processed to provide those features and handle abuse. The Contact form submits your name, email, subject, message, page URL, and browser user-agent through Watchlist's server endpoint to Supabase's feedback table, where they are stored with a record ID and creation timestamp. The form does not send an email; contacting the published email address is a separate option.
3. Authentication, browser storage, and the extension
Watchlist is intended for people age 13 and older. During signup, Watchlist collects your date of birth to determine eligibility and stores it as a private profile field; it is not included in public profile responses. Watchlist uses authentication cookies and temporary PKCE verification state to establish and recover sessions. Browser storage also holds preferences and local feature state, including some list backups and dismissed prompts. Clearing storage can remove that local state or sign you out.
The extension reads the current supported desktop YouTube watch-page URL only to extract its video ID. It sends that video ID to Watchlist to retrieve the community score and rating count, including before you connect an account. After connection, requests can also include your Watchlist session token, existing rating, and a rating you choose to submit. The extension does not scrape or transmit the page's title, description, comments, transcript, thumbnails, form contents, or general browsing history.
Rating an unknown video can initiate trusted catalog ingestion: Watchlist retrieves video and channel metadata from the YouTube API and may send the video title, description, creator name, and duration to OpenAI for classification. That classification request does not include your account password, session token, email address, username, or rating. Extension authentication takes place on Watchlist; session tokens are stored in restricted extension background storage, not supplied to YouTube content scripts. You can sign out and remove the extension through your browser.
4. Signup and abuse prevention
Signup protection hashes the request's signup IP before trusted persistence and rate-limit use; it does not store that raw IP in the signup hash field. Hashed network and email signals, attempt timestamps, and admission/reservation records help enforce short-term budgets and prevent abuse. A shared signup network is not a permanent one-account identity restriction.
Hashing is not a guarantee of anonymity. Hosting, authentication, CAPTCHA, email, and network providers can observe network information such as IP addresses while requests are in transit and may keep their own operational logs. Security and throttling history may remain after an account is deleted.
5. Infrastructure and API providers
- Supabase provides authentication, database, and file storage. Confirmation and recovery emails use its configured email delivery service, which can include Resend SMTP.
- Vercel hosts the website and server endpoints and processes requests and operational diagnostics.
- Cloudflare Turnstile processes browser/request signals for bot and abuse protection.
- YouTube and the YouTube API supply video/channel metadata, thumbnails, links, and playback. Loading that content can communicate with Google/YouTube.
- OpenAI is used server-side to classify supplied video title, description, creator name, and duration. Classification results are stored in the catalog; the classifier does not receive your account password or rating as its classification input.
These providers process information needed for their roles and have their own terms and privacy practices. See Supabase, Vercel, Cloudflare, Google/YouTube, OpenAI, and Resend.
6. Usage and diagnostics
Requests and errors can generate operational information used for reliability and security, including request time, requested endpoint, response status, network information such as IP address, and browser or device information made available in ordinary HTTP requests. The extension does not include advertising analytics or transmit general click, scroll, mouse-movement, or keystroke activity.
Optional growth analytics
Optional website analytics remain disabled unless Watchlist has approved their privacy configuration. When enabled, they require your explicit opt-in. Decline or withdraw permission using the analytics control on public pages. Supported Global Privacy Control and Do Not Track signals suppress collection. Your choice is stored in this browser; clearing storage resets it.
Optional Vercel Web Analytics measures aggregate page views and traffic sources. Watchlist groups public identifier routes and strips query strings and fragments. Authentication, recovery, extension connection, admin and private account/list routes are excluded. Collection is suppressed when the incoming referrer contains more than its origin. Origin-only referrer policy limits outgoing referrer information. Vercel can process request/device information as described in its analytics privacy documentation. No advertising pixels or session replay are used.
Separately, administrators can see aggregate growth estimates derived from existing confirmation, rating, review and list records. These reports do not display individual accounts, collect new browsing history, or change XP or achievements. Historical results are limited by deleted records and incomplete action history.
7. How information is used
Information supports authentication, public discovery and rankings, ratings/reviews, list management, profile customization, progression, recommendations, support, and abuse prevention. Providers receive information needed to deliver these functions. We may also respond to lawful requests or act to protect users and the service. Public content can be viewed, copied, or indexed by others.
8. Retention and account deletion
Watchlist retains information while it is needed to operate the service, maintain records, or address security and legal obligations. There is no single implemented retention period for all data. Provider logs, backups, and durable abuse-prevention records can have different lifecycles.
Account deletion in Settings removes the account and associated database records covered by Watchlist's deletion rules. Local browser data, backups, security logs, or provider records may persist for technical, security, or legal reasons. Contact us about remaining files or other deletion questions. Catalog videos are independent of an individual account, and Watchlist cannot delete the underlying YouTube content.
9. Security and your choices
Watchlist uses access controls, trusted server operations, and abuse protections, but no system is perfectly secure. You can edit supported profile fields and privacy choices, manage your content through available controls, clear browser storage, sign out, uninstall the extension, or delete your account. For access, correction, or deletion requests beyond those controls, contact us; we may need to verify your identity.
10. Chrome Web Store Limited Use
Watchlist's use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements. The extension uses information only to provide or improve its disclosed single purpose: showing Watchlist community rating information on supported YouTube watch pages, connecting a Watchlist account, and saving ratings the user chooses to submit.
We transfer information received through the extension only when necessary to provide or improve that purpose, to protect the service and users from abuse or security threats, to comply with law, or as part of a permitted business transaction with appropriate user protections. We do not sell extension data, use it for personalized, retargeted, or interest-based advertising, or use it for creditworthiness or lending decisions. We do not permit people to read extension data except when you give specific consent, when needed for security or abuse investigation, to comply with law, or when information has been aggregated and anonymized for internal operations. Service providers may process information for the disclosed functions under their own terms and privacy practices.
11. Changes and contact
Changes to this policy will be published here with an updated date. For privacy questions, including concerns about information concerning a child, use Contact or email support@joinwatchlist.com.