Privacy
Last updated 14 November 2026
TLDWatch turns YouTube videos, and the files and texts you give it, into Summaries you can read or listen to. This page says what TLDWatch processes, who else handles it, and how long it's kept.
Summaries of YouTube videos
- When you paste a YouTube link, the video is read by a third-party AI service to write its Summary. Its inputs may be reviewed by people at that service.
- A Summary of a YouTube video is shared: anyone who asks for the same video, or opens its link, sees the same Summary. It isn't tied to you.
- Translations into other languages are made by a third-party AI service from the Summary's text.
- Video details such as length and privacy come from the YouTube API Services. YouTube's use of data is covered by the Google Privacy Policy.
Uploads: your files and texts
- You can upload a video, an audio file, a PDF or an image, or paste a long text (a text file is read in your browser and sent the same way). Members and Guests alike can do this.
- It's processed by a third-party AI service to write its Summary, and may be reviewed by people there, so don't upload or paste anything private or personal.
- An uploaded file is stored privately only while it's summarized, then deleted from our storage and from the AI service, whether summarizing worked or not. A file that's never summarized is deleted within about a day. A pasted text isn't stored at all; only its Summary is.
- An Upload's Summary (and any translation of it) is private: only whoever made it can open it, and it's never shared.
- A Member's Upload Summaries appear in their History and are deleted with their account.
- A Guest's Upload Summaries are tied to the anonymous cookie in their browser, and are deleted automatically 30 days after they're made. Clearing your browser's cookies means you can no longer open them, but they're still deleted on schedule.
Guests
- To keep daily limits fair, TLDWatch sets an anonymous cookie (a random ID, lasting a year) and keeps a keyed hash of your IP address, never the address itself. They're used only to count new Summaries per day, and those counts are deleted after about two months.
- The cookie also marks your Upload Summaries as yours, so only your browser can open them (see Uploads).
Members
- You sign in with Google. TLDWatch receives your name, email address and profile picture from Google, and records when you confirmed you're 18 or older.
- TLDWatch keeps your History (the Summaries you've opened), your autoplay setting, and counts of your new Summaries per day.
- You can remove History entries at any time, and delete your account in Settings. Deleting it removes your profile, settings, History, Uploads and their Summaries, daily counts, and your sign-in.
- You can also remove TLDWatch's access to your Google account at any time in your Google account settings.
Listening
- The Standard voice runs on your own device; nothing is sent anywhere.
- The Natural voice sends the Summary's text to ElevenLabs to be spoken. The audio of a YouTube Summary is stored and shared like the Summary itself. Upload Summaries never use it; they're only read in the Standard voice.
Services that host and run TLDWatch
- Vercel hosts the site. It sees your IP address and country, which TLDWatch uses to block regions it can't serve and to keep out bots.
- Supabase stores the database (Summaries, Members, History) and uploaded files while they're summarized.
- Google provides sign-in for Members.
Cookies and storage in your browser
- The Guest cookie, and sign-in cookies for Members.
- Your browser also remembers settings such as autoplay, playback speed, your chosen voices and whether you've seen the welcome notice. These stay on your device.
Who TLDWatch is for
TLDWatch is for people 18 and over, and isn't available in the European Union, the EEA, the United Kingdom or Switzerland.