Privacy

Last updated: September 18, 2026

This policy is for the Binged TV diary at this deployment (currently binged-ecru.vercel.app). It uses Auth.js (NextAuth) and Prisma Postgres. It is not the older recommendation app on www.binged.app, which uses a different stack (Supabase).

What we store

• Account: email, username, display name, an optional profile picture, and a hashed password. We cannot read your raw password.
• Diary: episode ratings, optional short reviews, watched marks, favorite shows, ranked lists, watchlist items, and who you follow.
• Catalog: TV titles and artwork fetched from TMDB when a server-side API key is configured.

What is public

Binged is built like a public diary. Usernames, display names, bios, profile pictures, ratings, reviews, watched counts, favorites, lists, watchlists, and follower lists are visible to anyone with the profile link. Email addresses and password hashes are not shown on profiles.

How we authenticate

Sign-in uses Auth.js with email and password. Sessions are stored in an HTTP-only cookie. There is no Supabase Auth in this app, and this codebase does not load a Supabase anonymous key in the browser.

Analytics and third parties

This app does not embed product analytics SDKs. Hosting (Vercel) and the database provider may process request logs needed to run the service. Show artwork and titles may be requested from TMDB.

Your choices

You can change your password while signed in at /account. To correct or delete your account data, contact the operator of this deployment. Self-serve account deletion is not built yet.