Privacy Policy

1. Controller and contact

Watchmora is operated by Stanislav Sliuzar, a self-employed sole trader in the United Kingdom, trading as Watchmora. He is the controller of personal information described in this Policy unless a third-party service acts independently under its own privacy terms.

Watchmora is not a limited company. No data protection officer or formal UK or EU representative has been appointed because none has been confirmed as required for the current operation.

For privacy questions, rights requests or complaints, use the Privacy or Data Protection form in the Support Centre. Watchmora does not publicly expose the operator’s private destination mailbox or family residential address. A separate public business correspondence address will be added when established.

2. Who this Policy covers

This Policy covers visitors, account holders, people who submit comments or reports, rightsholders, support contacts and people whose publicly available professional information may appear in catalogue or editorial content.

The public catalogue can be browsed without an account. Accounts and account-only community features are intended only for people aged 18 or over.

3. Information we collect

Depending on how you use Watchmora, we may collect or generate:

• account information, such as name or display name, username, email address, password hash, email-verification status and account settings;
• Google account information provided through OAuth, such as a provider identifier, verified email, name and avatar metadata;
• legal records, such as the versions and times of your Terms agreement, Privacy acknowledgement and 18+ declaration;
• preferences and activity, such as watchlists, ratings, likes, dislikes, hidden titles, watched status, selected services, region, taste settings, saved searches and recently viewed items;
• search, audience and interaction information when the relevant analytics choice permits it, including page or surface events, search terms, result clicks and pseudonymous identifiers;
• comments, replies, usernames, moderation results, reports and appeals;
• support, privacy, copyright, legal and security case information, including messages, case history and evidence you choose to provide;
• device and technical information, such as IP address, user agent, request headers, session identifiers, security events and server logs;
• notification or device tokens where notifications are enabled;
• generated information, such as recommendation scores, similarity profiles, embeddings, moderation categories and AI-generated catalogue text;
• public professional information about films, television programmes and people obtained from catalogue providers or public sources.

Do not submit more personal information than is reasonably necessary for your request.

4. Where information comes from

We obtain information:

• directly from you when you register, configure an account, post, report, appeal or contact us;
• from your use of Watchmora, subject to your privacy choices and the operation of essential security logs;
• from Google when you choose Google registration, login or account linking;
• from catalogue, media and public-information sources, including TMDB and conditionally Wikipedia or Wikimedia where provenance is recorded;
• from automated systems that derive moderation, recommendation, similarity or editorial information from existing inputs.

5. Why we use information and our lawful bases

We use personal information for the following purposes:

### Providing your account and requested features

We use account details, preferences, watchlists, ratings, history and saved settings to create and operate the account and provide features you request. The usual lawful basis is performance of our contract with you under the Terms of Use.

### Security, abuse prevention and service integrity

We use technical logs, IP addresses, device information, verification results, rate limits, moderation records and case evidence to protect accounts, investigate abuse, prevent fraud, maintain availability and defend legal rights. The usual lawful bases are our legitimate interests in operating a secure service and, where applicable, compliance with legal obligations.

### Comments and community moderation

We use usernames, comment text, reports, moderation results and appeals to publish community contributions and apply the Community Guidelines. The usual bases are performance of the account contract and our legitimate interests in maintaining a safe and useful community.

### Recommendations and personalisation

We use catalogue data and, where enabled, your preferences and account activity to rank or suggest content. The usual bases are performance of requested account features and our legitimate interests in improving discovery. You can clear or change relevant account information and use the available privacy controls.

Statistical analytics and your choices

Last updated: 26 September 2026.

For reliably identified UK visitors, Watchmora operates its own limited statistical measurement by default. Its sole purpose is to produce aggregate statistics about use of Watchmora so we can improve the service. We rely on the statistical purposes exception in paragraph 5 of Schedule A1 to PECR, as amended following the Data (Use and Access) Act 2025. Prior consent is not required only where all conditions of that exception are met. We give clear information and a simple, free means to object through Privacy choices. An existing analytics rejection is respected.

For EEA visitors and any location we cannot reliably identify, this measurement is off until you expressly allow Site statistics. Interface language never determines this choice. For temporary information that is personal data, our UK GDPR basis in the UK is our legitimate interest in measuring and improving this service, with minimisation and a right to object. Where we ask permission, the basis is consent. We do not use these statistics to profile you, personalise recommendations or advertising, make individual decisions, monitor other services or send conversion data to advertising platforms.

We count page views, temporary sessions, landing and last-observed exit pages, approved referrer domains, source/medium, approved campaign/content/placement/term labels, approved campaign/ad-set/ad labels, route family, locale, device/browser/OS category and country where available from our trusted delivery service. We count searches without search text, title and collection opens, provider-link clicks, successful watchlist additions and a limited engagement signal. A provider click or watchlist-add is counted once per page and event type, not as an exact transaction count. The same session identifier is never reused for account features, recommendations, advertising or security. Unrecognised campaign values are grouped as “other”; click identifiers such as fbclid and gclid are not collected.

Statistical analytics does not store your name, email, password, payment information, account ID, authentication token, raw IP, full user-agent string, fingerprint, advertising identifier or cross-site browsing history. A random first-party analytics cookie lasts 30 minutes of inactivity. Temporary database state contains counters, initial acquisition dimensions and the last observed public path, not a browsing-event history. Closed sessions are aggregated every five minutes; active temporary records and retry markers are retired after 23 hours, within a 24-hour maximum under the scheduled cleanup. Long-term aggregates have no session identifiers and are retained for 24 months. Separate dimensional breakdowns are not joined into visitor profiles. These statistics can undercount when browsers block requests, visitors object or requests fail.

Site statistics and Google Analytics have separate controls in Privacy choices. Turning Site statistics off stops further statistical storage/access, removes the temporary analytics cookie and discards the current temporary session. Existing anonymous aggregates remain. Turning it on applies to future activity only, without reconstructing earlier visits. The necessary preference cookies contain only on/off values, are first-party, Secure, HttpOnly, SameSite=Lax and last 180 days. Essential sessions, CSRF protection, security logs and requested account features continue.

Google Analytics is optional

Google Analytics 4 runs only after separate explicit permission in Privacy choices, including in the UK. We do not rely on the UK statistical exception for GA4. There is no Google tag or cookieless measurement before that permission. Public page URLs sent by our code omit all query parameters, page titles are reduced to a route category, and our event code does not send raw search text or account identifiers. Google still receives connection/device information when you permit its service. Our tag denies ad_storage, ad_user_data and ad_personalization, disables Google Signals and advertising personalisation signals, and does not set User-ID. Property-side data sharing, linked services, enhanced measurement and retention are controlled in Google's account settings; their exact current values have not been verified in this release.

With permission, Google can use _ga and the measurement-specific _ga cookie as pseudonymous identifiers. Our tag requests a 180-day cookie lifetime without renewal on every activity. Google's standard property user/event retention choices are two or fourteen months; its aggregate reporting has different retention. These are not the first-party 24-hour raw-data rules. Declining Google Analytics prevents future Google measurement and removes accessible Google Analytics cookies. Google may process data internationally; its privacy information is at https://policies.google.com/privacy. Applicable contractual and transfer safeguards must be maintained with Google; we do not claim an unverified account configuration.

No Meta Pixel, Google Ads remarketing or other advertising tracker is installed by this release. Advertising technologies are outside the statistical exception and require their own consent. Campaign source labels describe arrivals at Watchmora for service improvement; they are not advertising IDs, cross-site attribution or permission for ad targeting.

Separate account and search functions

Existing account privacy controls, consent-based audience-ranking analytics and internal search-quality diagnostics are separate from this statistical layer. They do not receive its session identifier. Search diagnostics may retain search text for product debugging under the existing search controls; do not enter private information into public search. The new 24-hour statistical retention does not describe account, support, security, consent-based audience records or search-diagnostic records. You can use account privacy controls and the Privacy form for those functions.

### Support, privacy and rights cases

We use messages, evidence, contact details and case history to respond to support, data-protection, copyright, legal, moderation and security requests. The usual bases are our legitimate interests in handling requests and protecting rights, performance of our contract where relevant, and compliance with legal obligations.

### Legal records

We keep records of policy versions, acknowledgements, account actions and case outcomes where necessary to demonstrate the account relationship, comply with law, resolve disputes and establish, exercise or defend legal claims. The bases are legal obligation and legitimate interests.

6. Artificial intelligence and automated systems

Watchmora uses OpenAI or other automated systems for verified functions that may include:

• checking usernames and comments for safety or policy risks;
• enriching catalogue information;
• generating similarity profiles and embeddings;
• rewriting or translating catalogue descriptions where enabled;
• supporting recommendations;
• supporting future Journal drafting, rewriting, translation, summarisation, structuring and publication.

For username and comment moderation, the submitted username or comment text may be sent for automated analysis. The application was not found to intentionally add your account email or raw IP address to those moderation payloads. Catalogue processes generally use catalogue metadata and text rather than account email or raw IP address. Technical providers may still receive ordinary connection or service metadata under their own systems.

Moderation may allow a submission, hold it for review or block it. Recommendation systems may change the order or selection of content shown to you. These activities are not intended to make decisions that have legal or similarly significant effects. You can report an error or appeal an eligible moderation decision.

Watchmora will update this Policy before introducing a materially new use of personal information with AI.

7. Cookies and device storage

Watchmora uses cookies and similar storage for sessions, security, request protection, language, privacy choices and account features. Optional audience analytics follows the choice shown to you. YouTube is loaded only after you choose to play a trailer.

The Cookie and Storage Technologies Policy contains more detail and a verified inventory. You can change optional choices through Privacy Choices.

8. Recipients and service providers

Personal information may be processed by or disclosed to the following verified providers or categories where necessary:

These services may act as processors, independent recipients, licensors or data providers depending on the activity. Their exact legal role can differ. Watchmora does not sell personal information.

Inactive adapters or integrations must not be presented as active recipients.

9. International processing

Some providers operate in or access information from countries outside the United Kingdom. This can include global providers such as Cloudflare, Google, OpenAI and YouTube.

Where UK data-protection law requires a transfer mechanism, Watchmora expects the relevant provider arrangement to use an applicable adequacy regulation, contractual safeguard or other lawful mechanism. Contractual and transfer documentation is under review, so this Policy does not claim a specific safeguard where it has not been verified.

You may ask for available information about relevant safeguards through the Privacy form.

10. How long we keep information

We keep information only for as long as reasonably necessary for the purpose, security, dispute or legal requirement involved.

• Account information and account preferences are generally kept while the account exists and are processed through the account deletion workflow when you delete it.
• Google connection information is kept while the connection or account exists and is removed locally when disconnected or when the account is deleted.
• OAuth flow data is short-lived and normally expires within the configured session period.
• Watchlists, preferences, history, ratings and similar account data are kept until you clear them or delete the account, subject to limited backup and legal records.
• Comments and moderation information are kept while needed for publication, moderation, appeals, abuse prevention and legal evidence. Deleting a public comment may not immediately remove related security or moderation records.
• Support, privacy, copyright, legal and security cases are kept as long as needed to handle the matter, maintain an audit trail, prevent abuse and establish, exercise or defend legal claims.
• Evidence files are kept only while needed for the related case, security or legal purpose.
• Application, access and security logs follow operational security and server-rotation needs.
• Backups follow backup rotation. Deleted information may remain until overwritten and is restored only where required for disaster recovery.
• AI-generated catalogue profiles, embeddings and outputs may remain while the related catalogue record or operational purpose remains.
• Legal acknowledgements may be kept while needed to prove the account and policy relationship and are handled through the deletion workflow where applicable.

If no fixed period is stated, these criteria determine the period. We review retention mechanisms as the service changes.

11. Account export and deletion

Authenticated users can request an export of covered account information through the account privacy controls. Exports are designed to include the main account, preference, activity, comment and legal-acknowledgement categories handled by the export service.

You can request account deletion through the account privacy controls. The deletion workflow removes or disconnects covered account data such as social connections, sessions, preferences, watchlist, history, ratings, comments and personal recommendation records as implemented.

Some information may remain for a limited period in backups, security logs, anonymised support history, moderation evidence or legal records. We do not promise immediate deletion from every backup copy.

12. Your rights

Depending on the processing and applicable law, you may have rights to:

• receive information about our use of your personal information;
• access personal information we hold about you;
• correct inaccurate information;
• request deletion;
• request restriction of processing;
• object to processing based on legitimate interests;
• withdraw consent for optional processing;
• receive portable information where the right applies;
• complain about our handling of personal information;
• raise concerns about automated processing.

These rights are not absolute and can depend on the lawful basis, exemptions and the rights of other people.

Use the Privacy form to exercise a right. We may ask for information reasonably necessary to verify identity or authority. We will not request more evidence than is proportionate.

13. Data protection complaints

Use the Data Protection Complaint form if you believe Watchmora has handled personal information incorrectly.

We will acknowledge a data-protection complaint within 30 days of receiving it. Without undue delay, we will take appropriate steps to investigate, keep you informed where necessary and communicate the outcome.

You may also complain to the UK Information Commissioner’s Office. Information about making a complaint is available on the ICO website. We encourage you to contact Watchmora first so we can investigate directly, but this does not remove your right to contact the ICO.

14. Children and under-18s

Watchmora accounts and account-only community features are for adults aged 18 or over. The public catalogue can be browsed without an account.

We do not routinely collect date of birth, identity documents or biometric age data. Registration relies on an age declaration and does not guarantee that every account holder is an adult.

People under 18 should not create an account, post comments or submit personal information through account-only features. A parent or guardian can use the Privacy or Support form to report a suspected underage account.

More information appears on the Privacy for Younger Users page.

15. Security

We use access controls, password hashing, session security, request protection, rate limits, private evidence storage and other organisational and technical measures appropriate to the service.

No service can guarantee perfect security. Use the Security form if you discover a vulnerability. Do not send passwords, private keys or unnecessary personal information.

16. Changes to this Policy

We may update this Policy when the service, law or data flows change. We will publish the new version and effective date. Material changes may require account holders to acknowledge the updated Policy before continuing to use account-only features.

We will bring materially new uses of personal information to people’s attention before starting the new processing where required.

17. Contact

Use the Support Centre and select Privacy or Data Protection for questions, rights requests or complaints. Use the dedicated Copyright, Legal or Security route for those matters.

Watchmora does not currently publish a private residential address or private destination mailbox. A separate public business correspondence address and public domain contact aliases will be added only after they are established and verified.

For privacy questions or personal-data requests, use the privacy form in the Watchmora Support Centre or email [email protected].

Watchmora uses Apple iCloud+ Custom Email Domain for incoming human correspondence sent to its @watchmora.com mailboxes. Watchmora uses SMTP2GO to send automated and transactional service messages from [email protected]. Replies to automated messages are directed to the relevant human Watchmora mailbox.

Discovery, browser saves and trailer feed

Where available, explicit saved titles, Interested, Not for me and preferences are kept in this browser’s IndexedDB (wm.discovery.v1). These are distinct from ratings and watched status. Explicit saves are not evicted to free space; browser storage failure may limit use to the current session. You can remove individual saves or clear this browser’s discovery data in Privacy choices. Browser clearing does not delete account data.

Optional visited-title history is off until enabled separately. It is limited to 200 unique titles over 90 days; expired entries are removed when the feature is next used. Revoking history permission removes that history without removing explicit saves. Neutral navigation is not a dislike.

Recommendations send title identifiers, language, region and explicit preferences to Watchmora using private requests. Optional history is sent only when enabled. A session-isolated continuation cache expires after 15 minutes; it is not a permanent guest behavioural profile. A minimal session navigation position may be retained to return from details or switch views.

New registrations import browser saves and choices after the registration disclosure. Signing into an existing account asks for confirmation. Import merges saves without duplication and preserves existing account restrictions. Browser records are cleared only after acknowledgement of their unchanged revision. Failed or conflicting records remain available locally. Account import receipts retain deduplication identifiers and acknowledgements, not full browsing history, until the account is deleted.

Opening the trailer feed immediately loads the YouTube player and sends connection and playback information to YouTube under its own policies, like normal trailer embeds. Playback attempts to start with sound; if the browser blocks autoplay, the open native player remains available for manual Play. This does not enable analytics or optional visited-title history. Native YouTube controls remain available.