Privacy Policy

What data ReelMind collects, how it uses it, and how it is stored and deleted.

Version 2026-06-17 • Updated 2026-10-04

English

1. Scope and Contact

This Privacy Policy explains how ReelMind processes personal data when you use the mobile application, related APIs, authentication flows, public legal pages, support pages, and feedback tools.

Privacy questions and data requests can be sent to privacy@reelmind.net. Support and account deletion questions can be sent to support@reelmind.net. Abuse or moderation reports can be sent to abuse@reelmind.net.

2. Data We Collect

We collect account data such as email address, password hash, username, language preference, social discoverability settings, app badge preference, and optional profile photo.

When you sign in with a social provider, we process provider identifiers, basic profile data returned by the provider, and the linkage between that provider account and your ReelMind account.

We process watchlist data, watched status, ratings, notes where available, shared movie or series URLs, provider metadata, and social provenance that you submit or generate through the app.

We process social feature data such as follows, contacts, invite token lifecycle records, activity events, opinions or reviews, discussion comments, mentions, spoiler labels, attached images and their technical metadata, discussion read or mute state, reports, blocks, and related snapshots needed to display activity and moderation context.

When you send feedback, we process the category, message, steps, expected result, route, app version, build number, platform, device and OS context, language, screen metadata, and optional screenshot you choose to attach.

If you choose to support the project through an external payment provider, that provider processes your payment details under its own terms. ReelMind does not receive or store your card, bank, or wallet credentials.

Depending on the payment provider, ReelMind may receive limited payment metadata such as amount, currency, receipt status, payer display name, email address, message, and transaction or payout identifiers.

When movie import fails, we may store limited diagnostic telemetry such as source host, pipeline stage, resolver name, fallback status, platform, app version, language code, ingress source, safe error summary, and query parameter names, without storing full sensitive query values.

We also collect limited product events: first app open, receipt of a shared movie link, completed registration, successful link import, saving a movie, and initial activation after saving three movies with at least one link import within seven days of registration. These records may include event time, a randomly generated app installation identifier, event and interaction identifiers, your account identifier when available, platform, app version and build, language, ingress source, and limited technical details such as sign-in method or import resolver. Product event records do not include movie titles, full shared URLs, or user-submitted text.

For security and authentication, we process session identifiers, refresh-token hashes, device identifiers, public biometric login keys, IP address, user-agent, and security audit events.

3. How We Use Data

We use personal data to create and secure accounts, authenticate users, sync user content, support biometric login, operate movie import, social, invite, feedback, and account-management flows, and respond to support or security issues.

We use social and moderation data to show contacts and activity, prevent unwanted interaction, process reports, enforce blocks, and investigate abuse.

We use feedback and import diagnostics to reproduce bugs, improve reliability, identify regressions by app version, and prioritize support work.

We use product events on ReelMind's servers for analytics: to measure initial use, registration, import and saving success, and feature effectiveness, and to improve the product. These events are collected automatically, including the first app open before sign-in, and the current app does not provide an analytics switch. We do not use them for advertising, share them with advertising partners, or track your activity across other companies' apps or websites.

We use voluntary support metadata for bookkeeping, provider reconciliation, fraud and dispute handling, and support requests related to a payment.

We also use limited technical data to detect abuse, investigate fraud, maintain service integrity, and comply with legal obligations.

We do not sell personal data.

4. Legal Bases and Disclosures

Where applicable, we rely on contract necessity to provide the service you request, legitimate interests for security and service reliability, and consent where a specific consent is legally required.

We may disclose data to infrastructure and service providers that process data on our behalf, to identity providers used by you, to platform services such as Apple or Google where needed for app functionality, or where disclosure is required by law, legal process, or a protected safety interest.

5. Security

We use reasonable technical and organizational safeguards, including encrypted transport, hashed credentials and tokens where applicable, access controls, and audit logging.

Biometric authentication in ReelMind is implemented with device-bound keys. Raw Face ID or Touch ID biometric templates are not transmitted to the backend by the current implementation.

6. Retention and Deletion

We retain account and content data for as long as your account is active, and for a limited period afterward where required for backup restoration, security review, fraud prevention, dispute handling, or legal compliance.

When you delete a comment or request account deletion, we delete, hide, or anonymize associated content as appropriate; limited tombstones, report snapshots, block records, or security records may remain where needed for discussion integrity, abuse prevention, disputes, or the reasons above.

Product events are stored beyond the individual request for product analytics. Account deletion removes their direct account reference; installation and event identifiers may remain. You can send a request concerning these records to privacy@reelmind.net.

7. Your Choices and Rights

You can review and update parts of your profile from the app, edit or delete supported user content, mute discussions, change social discoverability settings, block users, report users or content, and control the app badge setting where supported by your device.

You can request account deletion using the published deletion flow.

Depending on your location, you may have rights to access, correct, delete, restrict, object to, or receive a copy of certain personal data. We may need to verify your identity before fulfilling a request.

8. International Use and Updates

If data is processed across jurisdictions, we take reasonable steps to apply appropriate safeguards required by applicable law.

We may update this Privacy Policy when product, security, legal, or operational requirements change. When a material update requires renewed acceptance, the app will request it before continuing access to protected areas.


Other Legal Documents