Who operates ScreenLife
ScreenLife Community Team operates ScreenLife and is the controller of the personal data described here. Privacy and data-protection requests can be sent tosupport@screenlife.tv.
Data we process
ScreenLife stores your email address, display name, password hash, account and privacy settings, profile information, library, viewing, reading, play and listening events, ratings, reviews, comments, lists, notes, tags, imports, notifications, moderation records, consent records and signed-in device sessions. Passwords are hashed and are not stored in readable form.
Security and operational logs may include timestamps, IP addresses, browser or device information and requested routes. Uploaded profile images and import files are processed to provide the feature you request.
If you make a voluntary contribution, Stripe processes the checkout and payment details. ScreenLife stores the Stripe transaction identifiers, currency, gross amount, processing fee, net amount, status and time needed to reconcile the public operating-cost total. ScreenLife does not store your card or bank-account details.
Why we use it
We process this data to create and secure accounts, provide tracking and community features, remember privacy choices, synchronise devices, deliver transactional email, investigate reports, prevent abuse, comply with legal obligations and improve reliability. We do not sell personal data or use it for third-party behavioural advertising.
Public and member-visible information
Your profile, ratings, reviews, lists, diary entries and activity may be visible publicly or to other members according to the audience shown in the app. New community profiles and published activity are public by default. You can change profile, rating, diary, content and comment audiences in Settings. Blocks and moderation rules override audience settings.
Service providers and metadata sources
ScreenLife is hosted on infrastructure in European Union. Metadata searches and movie, series, book, comic, game, music, artist, or person identifiers are sent to configured catalog and availability providers such as TMDB, Google Books, Open Library, Kitsu, MangaUpdates, MyAnimeList, Metron, IGDB, MusicBrainz, the Cover Art Archive, or ListenBrainz when ScreenLife requests information; those providers do not receive your ScreenLife password. DNS and network providers process the technical information required to connect you to the service.
Stripe acts as the payment provider for voluntary contributions and processes payment and fraud-prevention information under its own privacy terms. ScreenLife receives signed payment-status notifications and limited transaction records, but does not publish individual donor details.
Cookies, local storage and offline data
A secure HTTP-only cookie keeps you signed in. ScreenLife stores cached application files, read responses and queued viewing actions on your device to support installation and limited offline behaviour. Signing out clears private queued actions for that browser where supported.
ScreenLife browser extension
The ScreenLife Watch Logger processes the current streaming-site hostname, visible page title and episode metadata, video duration and playback position, and completion or next-episode signals so it can identify what you finished watching. Detection and its bounded diagnostic history run locally in the browser. The extension does not capture video or audio, inspect passwords or cookies, bypass DRM, or download media.
ScreenLife receives title metadata when the extension searches the catalog. If you confirm an action, it also receives the selected catalog identifier, watch status, rating, and review text you choose to submit. Account linking uses a one-time code and an extension-only access token stored in extension-local browser storage. The token expires after 180 days and can be revoked from the extension or account settings.
Streaming-site access is optional and requested for one origin at a time. Extension data is used only to provide and secure the watch-logging feature, is not sold, and is not used for advertising or unrelated credit decisions. ScreenLife's use and transfer of information received from browser APIs complies with the Chrome Web Store User Data Policy, including its Limited Use requirements.
Imports, exports and deletion
Letterboxd, IMDb, Spotify and generic import files are used to prepare the preview or records you approve. Spotify imports use the extended streaming-history ZIP as a file upload and do not connect ScreenLife to a Spotify account. ScreenLife keeps the listening fields needed for the import and excludes export fields such as IP address, country, platform, user agent and incognito status. Successful Spotify uploads are deleted after processing; failed uploads expire through the configured temporary artifact-retention period.
You can export account data and diary CSV data from Settings. You can permanently delete your account in Settings or follow thepublic deletion instructions. Deletion removes the active account and associated database records. Residual encrypted backups, if present, are isolated from normal use and expire through the applicable backup-rotation schedule unless retention is legally required.
Your choices and rights
You can correct profile information, control audiences, delete individual records, revoke sessions, export data and delete your account. Depending on where you live, you may also request access, correction, restriction, portability or objection. Contact support from the account email so that ownership can be verified.
Age eligibility
ScreenLife is not directed to children under 16. Accounts belonging to people below the minimum age may be removed when identified.
Analytics and advertising
ScreenLife does not currently contain advertising or third-party marketing analytics. If that changes, this policy and the relevant store disclosures will be updated before collection begins.
Security and changes
ScreenLife uses encrypted network connections, access controls, password hashing and operational monitoring. No system can guarantee absolute security. Material policy changes will be dated here and, when needed, presented in the app for renewed acknowledgement.