Privacy Policy

Effective date: November 13, 2026 · Last updated: November 17, 2026

This Privacy Policy explains what information the Watchprism mobile app ("Watchprism" or "the app") collects, why, who receives it, and the choices you have. "We", "our" and "us" mean its developer (see Section 1). It applies to Watchprism for iPhone (App Store). Where a section also describes Android, it refers to the same app on Google Play, which keeps its own privacy policy at movie_db_privacy.html.

Watchprism was previously called The Movie DB. On Google Play it is listed as "Movie Database: Movies & TV" (package uz.fozilbekimomov.the_movie_db) until that listing is renamed Watchprism. It is the same app.

Watchprism is an independent app. It uses the TMDB API but is not endorsed or certified by TMDB (The Movie Database).

The short version

Contents

  1. Who we are and how to contact us
  2. At a glance
  3. Information you provide
  4. Purchases (Premium)
  5. Information collected automatically
  6. Data that stays on your device
  7. What we do not collect
  8. How we use information
  9. Legal bases (EEA, UK, Switzerland)
  10. Who receives your data
  11. International transfers
  12. How long data is kept
  13. Your choices: ads, tracking, notifications
  14. How to delete your data
  15. Your rights
  16. Notice for US state residents
  17. Children
  18. Security
  19. Changes to this policy
  20. Contact

1. Who we are and how to contact us

Watchprism is developed and published by Fozilbek Imomov, an individual developer based in Uzbekistan. He is responsible for the personal data described in this policy (the "controller" under the GDPR) and is shown as the developer on the app's App Store and Google Play pages.

For any privacy question or request, email fozilbekimomov@gmail.com. We do not have a separate data protection officer.

2. At a glance

DataWho receives itWhyOptional?
TMDB username and password TMDB only (sent directly, not to us) To sign you in to your TMDB account Yes. Only if you choose to sign in
Favourites, watchlist, ratings, custom lists TMDB (stored in your TMDB account) The account features you use Yes. Only when signed in
Search text, titles you browse (linked to your TMDB account when you are signed in), language, watch region TMDB To show movies, shows and where to watch them Needed to use the app
Purchase status (which Premium plan you own) Apple or Google process the payment; the app checks the result on your device To unlock Premium Only if you buy Premium
Purchase and subscription records (product, transaction and renewal details, store purchase data), a random RevenueCat ID, device and app info (including the IDFV on iPhone), tracking-prompt status (iPhone), IP address RevenueCat (from app version 3.3.0) To keep a record of Premium purchases and subscriptions and to analyse sales; not used to decide Premium access or for ads Purchase records only if you buy or already own Premium. A random ID, device and app info and your IP address are sent when the app starts and when you return to it, also without a purchase (see Section 4)
App usage events (including in-app purchases), device info, approximate location (from IP), app instance ID Google (Firebase Analytics, linked to Google Ads) To understand and improve the app and to measure our own ads; Google may also use it for ads, within the limits in 5.2 (on iPhone only if you allow tracking) Automatic (see Section 13)
Crash reports and device info Google (Firebase Crashlytics) To find and fix crashes Automatic
Push token Google (Firebase Cloud Messaging) and Apple's push service on iPhone To be able to deliver notifications Automatic. Created when the app starts, whether or not you allow notifications
Notification topics Google (Firebase Cloud Messaging) To send the notifications you allow Yes. Only if you allow notifications
Advertising identifier (IDFA on iPhone, Android advertising ID), ad interactions, approximate location Google AdMob (and, on Android, Meta Audience Network through AdMob) To show ads in the free version Premium removes ads. On iPhone, the IDFA is used only if you allow tracking
A random install ID, the IDFV on iPhone (the Android OS build ID on Android), app version, platform Our own server (hosted on Railway; stored in Google Cloud Firestore in the United States) To count installs, updates and reinstalls Automatic
History, follows, reminders, settings, stats Stored on your device; we do not upload it. Some items are used in requests to TMDB (see 3.3 and 6), and some actions are logged to Google Analytics (see 5.2) App features You can clear most of it in the app, or all of it by deleting the app

3. Information you provide

3.1 Signing in with TMDB (optional)

Watchprism does not have its own user accounts. You can skip sign-in ("Skip for now") and still browse, search, see where to watch, follow shows, set reminders and buy Premium.

If you choose to sign in, you type your TMDB username and password into the app. The app sends them over HTTPS directly to TMDB (The Movie Database, operated by Xperi Inc.) to create a TMDB session. The password is not stored on your device and is never sent to us.

After sign-in, the app keeps the following in its private storage on your device: the TMDB request token, the TMDB session ID and your TMDB account ID. It also loads your TMDB profile (for example your username and avatar) from TMDB to show it in the app. Of that profile, only the account ID is saved.

The app does not create TMDB accounts. On Android, the "Register on TMDB" link on the sign-in screen opens TMDB's website in your browser; the iPhone app has no such link. Your use of TMDB is governed by TMDB's privacy policy.

3.2 What you save to your TMDB account

When you are signed in, these actions are sent to TMDB and stored in your TMDB account, on TMDB's servers:

According to TMDB, your watchlist, favourites and rated lists are private by default, and you can choose to make them public on TMDB's website (TMDB account FAQ).

Custom lists are different. TMDB's developer documentation names private lists as a feature of its newer (version 4) list interface. Watchprism creates lists through TMDB's version 3 list interface, which has no privacy setting (TMDB: v3 or v4 lists). Treat a list you create in the app as public: other people may be able to see its name, description and titles on themoviedb.org, and the app's "Share" button shares a link to it. Do not put personal information in a list's name or description. You can delete a list in the app or on themoviedb.org.

3.3 Searches and browsing

To show results, the app sends what you type in Search to TMDB, together with the app's TMDB API key, your app language and, for streaming availability, a country code (your "watch region"). The watch region is the country you pick in "My services", or else the country of your device's region setting, or else a country based on your app language. TMDB also receives your IP address, as with any internet request. The app keeps your last 10 searches on your device; Google Analytics only receives the length of a search, not its text.

If you are signed in, opening a title also asks TMDB, using your TMDB session, whether that title is in your favourites, watchlist or ratings, so TMDB can associate the titles you open with your TMDB account. For You also loads your TMDB ratings and watchlist to choose recommendations.

To provide some features, the app also sends TMDB the IDs of items stored on your device: the shows you follow (to refresh episode data), recently viewed movies and the genres you picked during onboarding (to build For You), and your selected streaming services (for the "Only on my services" filter). See Section 6.

3.4 When you email us

If you contact us from the app or by email, we receive your email address and whatever you write. This includes a report you start with "Report to us" in a TMDB review's menu: your mail app opens a message to us that already names the review, the title it belongs to and a link to the review. We use your message only to answer you and, for a review report, to act on it.

4. Purchases (Premium)

Watchprism Premium is sold as a monthly or annual auto-renewing subscription or as a one-time lifetime purchase. Purchases are processed entirely by Apple (App Store) on iPhone or Google Play on Android. We never receive your name, card number, billing address or Apple ID / Google account details.

What the app receives and does:

4.1 RevenueCat (from app version 3.3.0)

RevenueCat (RevenueCat, Inc., United States) processes purchase data on our behalf, as our service provider. We use it to keep a record of Premium purchases and subscriptions and to see sales and subscription statistics. The app still completes every purchase with Apple or Google itself, and RevenueCat does not grant or block Premium: the app does not ask RevenueCat whether you have Premium.

RevenueCat describes its own handling of this data in the RevenueCat Privacy Policy.

Billing, renewals, cancellations and refunds are governed by Apple's or Google's terms. See Section 13 and our support page for how to manage or cancel a subscription.

5. Information collected automatically

The app includes software development kits (SDKs) from Google and others. They collect some data automatically when you use the app. We do not attach your name, email or TMDB account to the data that these analytics, crash and notification tools collect, and we do not set a user ID in them. From app version 3.3.0 this also applies to RevenueCat's SDK, which connects to RevenueCat when the app starts and when you return to it (see 4.1).

5.1 Device identifiers

IdentifierPlatformCollected byWhen
Advertising identifier (IDFA) iPhone Google Mobile Ads (AdMob) and Google Analytics for Firebase Only if you tap "Allow" on Apple's tracking prompt. If you do not, ads are requested as non-personalised and the IDFA is not available to the app.
Android advertising ID Android Google Mobile Ads (AdMob), Meta Audience Network (through AdMob), Google Analytics for Firebase Unless you delete it or opt out of ads personalisation in Android settings. Google says Analytics then gets a string of zeros instead.
Identifier for Vendor (IDFV) iPhone Google Analytics for Firebase; our install counter; RevenueCat (from app version 3.3.0) Automatically
Firebase installation ID, Crashlytics installation ID, Analytics app instance ID, push (FCM) token Both Google Firebase Automatically. These are random IDs created for this installation of the app.
Install ID (a random ID the app creates) Both Our install counter Automatically
RevenueCat ID (a random ID that RevenueCat's SDK creates) Both RevenueCat (from app version 3.3.0) Automatically, when the app starts and when you return to it (see 4.1)

5.2 Analytics (Google Analytics for Firebase)

Google Analytics for Firebase collects, on both platforms:

On iPhone, Analytics also collects the IDFV, and the IDFA only if you allowed tracking. On Android, it collects the Android advertising ID as described in 5.1.

Google Ads. Our Google Analytics property is linked to Google Ads, which we use to advertise Watchprism, and to AdMob. Google can therefore use analytics data from the app, such as app events and in-app purchases, to measure our ad campaigns and for ad personalisation. On iPhone this data includes your IDFA only if you allowed tracking; on Android it includes the advertising ID unless you deleted it or opted out (see 5.1). The app controls these uses with Google's consent mode, which tells Google Analytics whether it may use advertising storage and identifiers, send your data to Google for advertising, and use it for personalised ads (together, the "ad uses" of analytics data):

Your answer to the tracking prompt and your consent choices do not stop Google Analytics from receiving app events, including purchases, to measure how the app is used (see Section 9). Google may also combine data used for ads with information from Google accounts whose owners have turned on ad personalisation, where Google's settings allow it. You can limit how Google uses your data for ads in My Ad Center. Google describes this in Google's explanation of how it uses data from apps that use its services.

5.3 Crash reports (Firebase Crashlytics)

If the app crashes or hits certain errors (for example a failed start-up step or an image that does not load), Crashlytics sends a report with the stack trace, the state of the app at the time, the device model, the operating system version and the Crashlytics and Firebase installation IDs. We do not add your name, account or custom logs to crash reports.

5.4 Push notifications (Firebase Cloud Messaging)

When the app starts, Firebase Cloud Messaging creates a push token for this installation (on iPhone it is linked to Apple's push (APNs) token), whether or not you allow notifications. The token stays with Firebase; the app does not send it to our server. The app asks for permission before showing notifications. Notifications are shown only if you allow them, and only then does your device join these notification topics:

Topics reveal only that group membership, not who you are. To subscribe the device to topics, Firebase receives the device model, language, time zone, operating system, app identifier and app version. Notifications about the shows you follow and about release reminders are scheduled locally on your device. The list of shows you follow and your reminders are stored on your device. To keep new-episode alerts up to date, the app asks TMDB for the details of each followed show (by its TMDB ID). Following or unfollowing a show and setting a reminder are also logged to Google Analytics with the title's TMDB ID (see 5.2).

5.5 Remote settings (Firebase Remote Config and Installations)

On start, the app downloads settings from Firebase Remote Config. These include feature switches, update requirements, the "What's new" text and the "Our apps" list. To choose settings, Firebase receives the country code, language, time zone, OS version and app identifiers. It also uses the Firebase installation ID. The app sends no other data of its own to Remote Config.

5.6 Advertising (Google AdMob)

The free version shows ads from Google AdMob: an ad when the app opens, banners, full-screen ads between some screens and optional rewarded ads (for example, "watch a short ad to go ad-free for 20 minutes"). Android also shows native ads in some lists. Premium users see no ads. For them the app does not show the tracking prompt or the consent form and does not start the ads SDK.

According to Google, the Google Mobile Ads SDK may collect:

Google uses this data under its own policies.

Your ad choices on a device without Premium:

  1. iPhone: the app shows Apple's App Tracking Transparency prompt once, the first time it is in the foreground after you install it, normally before the first ad loads. If the app starts in the background (for example from a notification), ads may load before the prompt, which then appears when you next open the app. Until you answer, and if you do not allow tracking, the app requests non-personalised ads and the IDFA is not available. If you allow tracking, AdMob may use your IDFA to personalise and measure ads. Your answer also decides whether the ad uses of analytics data are on (see 5.2).
  2. Where the law requires consent (for example in the EEA and the UK), Google's consent message (Google User Messaging Platform, UMP) asks for your choices about ads. In some US states, Google's message may instead let you opt out of the use of your data for targeted advertising. You can change your choices later in Settings → About → Privacy options. This item appears when it applies to you. In the EEA, the UK and Switzerland, these choices also apply to the ad uses of analytics data (see 5.2; on Android from the versions after 3.2.0).

Android only: some ads may be served by Meta Audience Network through AdMob mediation. According to Meta, its SDK may process device identifiers, device attributes (such as device model, screen size, operating system and SDK versions) and ad performance information (such as impressions, clicks, placement and viewability). The iPhone app does not include Meta's SDK.

The iPhone app lists Apple SKAdNetwork IDs for ad networks. These let ad networks measure app installs that come from ads without using the IDFA.

5.7 Our install counter

Every time the app starts, it sends one small message over HTTPS to our own server. The server runs on Railway (a hosting provider) and stores its records in Google Cloud Firestore, in a United States multi-region location. The message contains:

The server keeps one record per installation: the install ID, the IDFV (iPhone) or OS build ID (Android), the platform, when the installation was first seen, the first and the latest app version, and when the latest version was first opened. It also keeps one record of the first open of each app version on that installation, with the same identifiers, the version, the time and whether it was a new install, an update or a reinstall. Later starts of the same version are not stored. To tell a reinstall from a new install, the server compares the IDFV (iPhone) or OS build ID (Android) with its earlier records.

The server does not store your IP address in these records and does not work out your location from it. Like any web server, it sees your IP address when the message arrives, and its request log writes that IP address to the hosting provider's (Railway's) request logs, which are kept under Railway's log retention. We use this data only to count installs, updates and reinstalls of the app. It is not linked to your name, email or TMDB account, and it is not used for ads.

5.8 Content the app loads

Each of these services receives your IP address and standard request information (such as the app's user agent), as any internet connection does.

"Where to watch" links, trailers, review links, the TMDB sign-up page (Android only) and store pages open in your browser or in another app. From then on, that service's own privacy policy applies. Where we use affiliate links for a streaming provider (Amazon or Apple TV), the link carries our partner tag so the partner can credit us. The app sends those partners no other data.

6. Data that stays on your device

The following is stored in the app's private storage on your phone. The app does not upload these lists to us. Some of it is used to request content from TMDB, as explained below.

To provide features, the app sends TMDB the IDs of some of these items: followed shows (to refresh episode data), recently viewed movies and onboarding genres (to build For You), and your selected streaming services (for the "Only on my services" filter). Some related events are sent to Google Analytics as described in 5.2 (for example, that you opened a title, followed a show or set a reminder, with the title's TMDB ID). Like other app data, this data may be included in your device backups (iCloud or Google) if you have backups turned on.

7. What we do not collect

8. How we use information

If you are in the European Economic Area, the UK or Switzerland, we rely on:

Collection of analytics and crash data does not depend on your answer to the tracking prompt or your choices in the ads consent form: Google Analytics keeps measuring how the app is used, on the basis of our legitimate interests. Those choices control the IDFA on iPhone and the ad uses of analytics data (see 5.2). On Android, in version 3.2.0 and earlier, and until Google's consent message has reported your status on your device (for example just after you install the app, or if you have Premium and were never shown the message), the app does not limit those ad uses. The app currently has no in-app switch to turn analytics off; you can object by email.

10. Who receives your data

RecipientWhat forTheir policy
Google (Firebase Analytics, Crashlytics, Cloud Messaging, Remote Config, Installations) Analytics, crash reports, notifications, remote settings Firebase privacy, Google Privacy Policy
Google (Google Ads, linked to our Google Analytics) Measuring our ad campaigns for Watchprism; Google may also use the data for ad personalisation. On iPhone only if you allowed tracking (and consented where required), never with Premium; on Android as described in 5.2 How Google uses data for ads, Google Privacy Policy
Google (AdMob, User Messaging Platform) Ads and ads consent How Google uses data for ads, Data from apps that use Google services
Meta Platforms (Audience Network), Android only Some ads, through AdMob mediation Meta Privacy Policy
TMDB (The Movie Database, Xperi Inc.) Movie data, search, sign-in and your TMDB account data TMDB Privacy Policy
Apple App Store purchases, push notification delivery (APNs), the tracking prompt Apple Privacy Policy
Google Play Google Play purchases and in-app updates on Android Google Privacy Policy
RevenueCat, Inc. (United States), from app version 3.3.0 Keeps a record of Premium purchases and subscriptions and provides sales statistics, on our behalf (see 4.1). Not used for ads RevenueCat Privacy Policy
Railway (hosting provider) and Google Cloud (Firestore database, United States) Host our install-counter server and store its records Process data on our behalf
Google Fonts, YouTube Fonts and trailer thumbnails Google Privacy Policy
Gravatar and other sites that host review avatars or our app icons Images shown in the app (see 5.8) Their own policies

For Firebase, Google says it generally acts as a data processor (service provider) for the app developer. RevenueCat acts as our data processor (service provider) and, according to its terms, may not sell or share the data. For advertising, Google and Meta also use data under their own policies.

We share data only with the service providers and partners listed above, and only for the purposes described in this policy. We work only with providers that are bound by their own terms and privacy policies and that give your data the same or equal protection as this policy and the App Store and Google Play rules require.

We may also disclose information if required by law, to protect rights and safety, or as part of a transfer of the app to a new owner, in which case this policy would continue to apply to your data.

We do not sell your personal data for money. For sharing with advertising partners, see Section 16.

11. International transfers

Google, TMDB (Xperi Inc.), Apple and our hosting provider may process data in the United States and other countries. Our install-counter records are stored in the United States (see 5.7). From app version 3.3.0, RevenueCat stores purchase records on Amazon Web Services servers in the United States and may also process them where it or its own service providers operate; its data processing terms use the EU Standard Contractual Clauses, with the UK Addendum and the Swiss adaptations, for transfers from the EEA, the UK and Switzerland. These countries may have different data protection laws than yours. Google states that Google LLC complies with the EU-U.S. Data Privacy Framework, the UK Extension to it and the Swiss-U.S. Data Privacy Framework. Google also says that some Firebase services, including Crashlytics and Cloud Messaging, may process data in any Google data center. The other providers describe their transfer safeguards in their own policies.

12. How long data is kept

13. Your choices: ads, tracking, notifications

Ads and tracking

Notifications

Analytics and crash reports

There is no in-app switch for analytics measurement or crash reports today. The ad uses of analytics data follow your tracking answer and consent choices as described in 5.2; where the app does not limit them, you can object by emailing us (see Section 15). Deleting the app stops all collection by the app.

14. How to delete your data

  1. Data on your device:
    • Clear search history in Search.
    • Clear recently viewed and the viewing log behind your stats in My Stats ("Clear History").
    • Clear My services, delete saved filters, unfollow shows, cancel reminders and remove favourite people one by one.
    • Show hidden review authors again in Settings → Hidden review authors ("Show all"), which clears that list.
    • Day-streak and badge history, "continue watching" progress and the genres you picked during onboarding have no separate clear option; deleting the app removes them.
    • Deleting the app removes all of it from the phone (except copies already in your device backups).
  2. Sign out: Settings → Log out. This asks TMDB to end your session and removes the session from your device. Your other on-device data stays until you clear it or delete the app.
  3. Your TMDB data and account:
    • Remove favourites, watchlist items, ratings and lists in the app or on themoviedb.org.
    • To delete the TMDB account itself, sign in on themoviedb.org, open your account settings and click "Delete Account" (TMDB account FAQ).
    • TMDB's privacy policy also lists privacyrequest@xperi.com for privacy requests.
    • We cannot delete TMDB accounts for you.
  4. Analytics, crash and install-counter data: email us at fozilbekimomov@gmail.com.
    • Because this data is not tied to your name, email or TMDB account, and the app does not show its identifiers, we usually cannot single out your installation. We will tell you what, if anything, we can locate and delete.
    • Deleting the app stops collection, and reinstalling it creates new Firebase installation and analytics identifiers and a new install ID.
  5. Purchases: Apple and Google keep purchase records under their own policies. Cancelling a subscription does not delete them.
  6. RevenueCat records (from app version 3.3.0): email us and we will ask RevenueCat to delete your record. The app does not show the random RevenueCat ID, so tell us what helps us find it, for example the order ID from the App Store or Google Play receipt; we will tell you what we could locate and delete. Deleting this record does not cancel a subscription; cancel it with Apple or Google (see Section 13). If you later restore or renew a purchase, a new record may be created.

15. Your rights

Depending on where you live (for example under the GDPR, the UK GDPR or US state laws), you may have the right to:

To use these rights, email fozilbekimomov@gmail.com. We may need information from you to find the data, as explained in Section 14. These rights also cover the data our service providers, such as RevenueCat, process for us; we will pass your request on to them. We will not discriminate against you for using your rights. You can also complain to your local data protection authority.

16. Notice for US state residents

This section is for residents of California and of other US states with similar privacy laws. In the last 12 months the app has collected these categories of personal information:

The sources, purposes and recipients are described in Sections 3 to 10.

17. Children

Watchprism is not directed to children under 13 (or the minimum age required by law in your country). We do not knowingly collect personal data from children. If you believe a child has given us personal data, email us and we will delete it.

18. Security

The app connects to TMDB, Firebase, RevenueCat and our server over encrypted HTTPS connections. Your TMDB password is never stored. Data on your device is kept in the app's private storage. No method of transmission or storage is completely secure, but we work to protect your information and limit what we collect.

19. Changes to this policy

We may update this policy when the app or the law changes. We will post the new version on this page and change the "Last updated" date. If a change is significant, we may also let you know in the app or in the store release notes.

20. Contact

Fozilbek Imomov, individual developer, Uzbekistan

Email: fozilbekimomov@gmail.com

Support: Watchprism support page

This product uses the TMDB API but is not endorsed or certified by TMDB.

© 2026 Fozilbek Imomov