Privacy notice
Updated 2 November 2026. Questions, requests and complaints can be sent to support@screenside.co.uk.
Hidden people and unwanted contact
Your account’s hidden-person relationships filter contributions and prevent replies between those accounts and access to each other’s hosted parties. We do not send a notification when you hide someone. Existing contributions and reports follow the usual retention rules. Other guests can still share a party and hiding does not prevent new accounts or conceal your public profile.
Information ScreenSide uses
When you sign in, the hosting service supplies a verified email address and may supply an account identifier. ScreenSide derives an internal identifier to connect your account with saved titles, viewing positions, comments, reactions, reviews, reports, feedback, parties and account settings. ScreenSide does not receive or store your password.
Comments, reviews and lounge posts include their text, display name, title and timestamps. Profile information can include a name, bio, favourites, avatar choices and an optional photo. Your display name is stored on your device and copied into future contributions. Reports and moderation decisions include the item, report reason, reporter identifier, receipt time, first-review time when a moderator starts review, and decision record.
Why we use it
We use this information to provide ScreenSide, protect community members, investigate reports, prevent abuse, operate watch parties, respond to support requests, and improve the service. Please do not include sensitive personal information in posts or feedback.
Who can see it
Other members can see the contributions and profile information you choose to share in the relevant ScreenSide community. Saved titles and viewing positions are private to your account. ScreenSide moderators can review reports, support requests and the stored data needed to operate and protect the service.
The original invited beta community remains separate from future public members. Beta profiles, photos, posts, parties and later changes to them are not published into a public community. An audience marker is retained to preserve that boundary.
Providers and title information
OpenAI provides hosting access and sign-in, with Cloudflare infrastructure used for the app, database and file storage. Film and TV searches use TVmaze and Wikimedia services. TV artwork may load directly from TVmaze and eligible film artwork may load from Wikimedia, which can receive usual image-request information such as IP address. Each provider has its own privacy practices. Provider infrastructure may process information outside the UK.
Photos, reports and safety
Photos are optional. They are cropped on your device and uploaded only when you choose to save them. New or changed photos are visible to authorised members of your ScreenSide community. Members can report photos for moderator review. Previously pending photos remain hidden until reviewed. Moderators may remove content, photos or accounts for safety reasons.
AI assisted report review
For reports of harassment, hate or abuse, and spam or scams, ScreenSide may send reported comment, review or lounge post text to OpenAI’s Moderation API to help moderators prioritize reports. Reporter and account identifiers are not sent with the text. Obvious email addresses, phone numbers and web links are redacted first, but text may still contain personal information. Reports about sexual or exploitative content, self-harm or eating disorders, privacy, spoilers, profiles or photos, and text caught by our sensitive-content safeguards are not sent to this AI check. Known or suspected child sexual abuse material is never sent. The AI result is stored as categories and status linked to the report by a one-way case key; submitted text and model scores are not stored in that result record. OpenAI says API inputs are not used to train its models by default; its abuse monitoring may retain request content for up to 30 days. AI results only help order the moderator queue and never remove content or suspend an account automatically. Moderators review reports and make all decisions. Automated text checks and request limits are limited safeguards; they do not replace human review.
Cookies, analytics and payments
Sign-in uses necessary session mechanisms. ScreenSide stores your chosen display name locally on your device. ScreenSide does not use advertising trackers. Optional first-party product analytics are off by default and use no analytics cookies or device identifiers. If you enable them in Account, ScreenSide links a random analytics identifier to your account and records event type, time and, where relevant, a title reference for visits, title views, shared-title referrals, viewing sessions, first contributions and returns. The owner sees aggregate counts only. Events older than 30 days are removed during later analytics activity or when the owner opens the analytics page; during inactivity, expired rows may remain until that cleanup. Turning analytics off deletes its linked events immediately, and account deletion removes them too. You can use Your data to export the retained event list. Paid membership is not currently open for customers. When it opens, Stripe will collect a billing address, payment details and tax location evidence for checkout, recurring payments, invoices and applicable tax. ScreenSide stores Stripe customer, checkout, subscription and invoice status identifiers, not your full card number. Contact support for billing records or corrections.
AI starter reactions
Where enabled, ScreenSide looks up title identifiers, episode numbers, language and release information through SubDL from the app server. It processes English subtitle text temporarily to create labelled conversation starters. Short excerpts from individual moments and the title are sent to OpenAI; your identity, viewing position and your own comments are not sent for this purpose. The subtitle file is not retained in the app database or sent to your browser. Generated prompts are checked for harmful content through OpenAI’s Moderation API. Each prompt uses one excerpt rather than the full film transcript, but AI can make mistakes and subtitle timings can vary by edition. Moderators can run private previews; these prompts are not saved to the shared member cache. Cached starter records include subtitle release information and cue-based times. Preparation status and retry records are removed on starter requests after 30 days. Cached reactions expire after 30 days; stale records are removed when any member next loads AI starter reactions. Without such a request, expired records can remain until later cleanup. Reporting a reaction removes it from the shared cache and sends it for moderator review.
Retention and your rights
Contributions and profile data remain until you delete them, close your account, or a moderator removes them. We aim to review inactive accounts after 12 months. Resolved moderation records are reviewed after 90 days, support correspondence after six months, and active suspension evidence after six months, unless there is an ongoing safety or legal reason to retain it. Provider backups follow provider arrangements and may not update immediately.
You can download your app records or close your account from ScreenSide. You can ask for access, correction, deletion, restriction, portability or to object to relevant processing by contacting support. We aim to respond within one month. You can also complain to the UK Information Commissioner’s Office.
Community rules and terms · Support and safety · Close your account