Privacy policy

Last updated 2 November 2026. Operator: Evolo Pty Ltd, Brisbane, Australia. Contact: ash.tiwari.ba@gmail.com.

Without an account

Likes and Watch later are stored only in your browser. We keep standard server logs (IP address, pages requested) for security and debugging. Videos play through YouTube's privacy-enhanced embed.

With Google sign-in

We receive your Google account ID, email, name and profile picture, and store them with your likes and Watch later list so they sync across devices.

YouTube data

If you connect YouTube we request read-only access (youtube.readonly) and read your liked videos and subscriptions once per connect. We store only: the IDs of liked videos that are in our catalogue, the IDs of subscribed channels that are in our catalogue, counts, and a numeric taste vector computed from titles. We do not store your access token, refresh token, raw liked-video list, subscription list, or titles. We do not share YouTube data with anyone or use it for advertising. HackerTube AI uses YouTube API Services; see the YouTube Terms of Service and the Google Privacy Policy. You can delete this data at any time from your account page, and revoke access at myaccount.google.com/permissions.

HackerTube AI's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Connected sources

On the Sources page you can give us a public username or link: GitHub, Hacker News, Bluesky, Mastodon, Stack Overflow, a personal site, or Discord servers through Discord's sign-in. We read public data from that service once, over its public API, when you flip the switch. We keep the username, a one-line summary (such as "120 starred repos"), and a numeric taste vector computed from the text. We do not keep the posts, comments, stars or page text themselves. If you turn on "Find my public profiles from my email", we look up your sign-in email on Gravatar and GitHub's public-email search and show you what we found before using it. Turn any switch off to delete that source's data.

Watch history uploads

When you upload a Takeout file we parse it in memory and keep only the catalogue videos it contains, the total count, and a taste vector. The file itself is not stored.

Payments

Payments are processed by Stripe. We receive confirmation of payment and your email; we never see your card details.

Storage and deletion

Data is stored in Google Cloud (United States). To delete your account entirely, email us from your sign-in address.