Privacy Policy

1. Overview

MultiMovies is designed to work primarily with data stored locally in your browser. If backend login/cloud sync is enabled for this deployment, selected account data is also processed by the configured backend API.

2. Data We Process

By default, data is stored in your browser's localStorage. If cloud auth is enabled, the backend stores only data necessary to run account, security, and moderation features.

• Account data: nickname, password hash, account creation date
• Session data: authentication tokens and session expiry
• App data: settings, watchlist, playback-related preferences
• Moderation data: account bans, audit logs, and timestamps

We do not require email verification to use accounts in the current deployment.

3. Purposes and Legal Basis (GDPR)

We process data for: (a) account login/session handling, (b) app functionality and optional sync, and (c) security and abuse prevention.

The legal basis is generally:

• Article 6(1)(b) GDPR (performance of a contract) for account/service operation
• Article 6(1)(f) GDPR (legitimate interest) for service security and moderation

Where local browser storage is strictly necessary for requested functionality, it is used on that basis.

4. Third-Party Services

MultiMovies may connect to external services needed to render content and metadata:

• TMDB API — movie/show metadata, posters, and search data
• OMDb API — external ratings and additional title metadata
• FebBox — streaming source/provider integration used by resolver flows
• TheIntroDB — optional intro/outro segment metadata
• Wyzie Subs — Multi-language subtitles and translations.
• Groq — inference platform used by the AI Assistant.

These services operate under their own privacy policies and terms. We recommend reviewing the policies for TMDB, OMDb, FebBox, TheIntroDB, and Groq directly if you use features that rely on them.

5. Cookies and Local Storage

MultiMovies uses technically necessary client-side storage (like localStorage) for user interface preferences and session authentication. We do not use advertising or tracking cookies.

To provide real-time occupancy statistics (Active Guests) without tracking IP addresses, the application uses an anonymous, randomly generated Client ID stored in your browser. This ID is not linked to your personal data.

If non-essential analytics or marketing cookies are introduced in a future release, this policy and consent flow will be updated accordingly.

6. Retention

We keep data only as long as needed for account operation, service reliability, and abuse prevention. Retention may vary by data type (e.g., session records vs. moderation logs) and may be adjusted where required by law or security obligations.

7. Analytics

This deployment does not use behavioral advertising trackers. If operational telemetry is enabled by the infrastructure provider, it is used for reliability/security, not ad profiling.

8. Your Rights (EU/EEA)

Subject to applicable law, you may request access, rectification, erasure, restriction, objection, and data portability where relevant. You may also object to processing based on legitimate interest.

9. Your Control

You can delete all stored data at any time by clearing your browser's localStorage, or by using the “Clear Everything” option in the Settings page.

For this deployment, data stored on our backend (Cloudflare D1) is deleted only when you use “Clear Everything” while logged into your account.

10. Contact

For privacy requests related to this deployment (including account deletion, access requests, or security concerns), please contact our security team:

For general support and other inquiries:

Community and quick updates: