Privacy policy
Last updated 11 August 2026.
What we collect
- Account details — your email address, username, display name and password (stored only as a scrypt hash, never in readable form).
- What you create — diary entries, ratings, likes, reviews, tags, lists, watchlist, follows, clubs and club messages.
- Product analytics — a named set of events such as “film logged” or “vote cast”, tied to your account id, so we can tell whether the product works. We do not track time spent or build advertising profiles.
- Session data — a hashed session token and the browser user-agent, so you can stay signed in and revoke sessions.
What we do not do
- We do not sell your data.
- We do not run third-party advertising or tracking pixels.
- We do not read your private diary entries or private club discussions for analytics.
Who can see what
You control this. Profiles, diary entries, reviews and lists each support public, followers only, or private. Clubs are private by default and their discussions are only ever visible to members. These rules are enforced on our servers in the database queries themselves, not just hidden in the interface — private content does not appear in feeds, search results or API responses. See privacy settings.
Third parties
Film metadata and artwork come from TMDB. When you view a film page, your browser loads poster images from TMDB's image CDN. We do not send TMDB your identity or your ratings.
Deleting your account
You can delete your account from account settings. This removes your name, photo, bio, email and username, ends every session, and makes your profile inaccessible. Content that other people rely on — club screening history, and moderation records — is retained in de-identified form so shared club history and safety records survive.
Your rights
Depending on where you live you may have the right to access, correct, export or erase your personal data. Account deletion covers erasure; for anything else, contact us and we will respond within 30 days.
Security
Passwords are hashed with scrypt. Session tokens are stored hashed and expire. All traffic is served over HTTPS. Every mutation is authorised server-side, and we rate limit sensitive endpoints such as sign-in, signup, reporting and imports.