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
- You can use Watchprism without an account. Signing in with a TMDB account is optional.
- If you sign in, your TMDB username and password go directly to TMDB over an encrypted connection. We never receive or store your password.
- Payments are handled by Apple or Google. We never see your card details.
- From app version 3.3.0, we use RevenueCat to keep a record of Premium purchases and subscriptions. It receives
your purchase and subscription details with a random ID, not your name, email or TMDB account. It does not decide
whether you have Premium, and it is not used for ads (see Section 4).
- We use Google Firebase for analytics, crash reports, push notifications and remote settings. We use Google AdMob for ads in the free version.
- Our Google Analytics is linked to Google Ads, which we use to advertise Watchprism. Google may use analytics data, including purchases, to measure our ads and for ad personalisation. The app limits this with Google's consent mode: on iPhone these ad uses stay off unless you allow tracking when the app asks and, in the EEA, the UK and Switzerland, also consent, and they always stay off with Premium. On Android (versions after 3.2.0) they follow your choices in Google's consent message in those regions and are not limited elsewhere (see Section 5.2). Usage statistics are collected either way.
- On iPhone, your advertising identifier (IDFA) is used only if you allow tracking when the app asks.
- Your history, follows, reminders and similar data are stored on your device; we do not upload them to our server. The app uses some of them in requests to TMDB, and some related actions are logged to Google Analytics (see Sections 5 and 6).
- We do not sell your personal data for money. Some data is shared with Google for advertising, which US state laws may call "sharing" (see Section 16).
Contents
- Who we are and how to contact us
- At a glance
- Information you provide
- Purchases (Premium)
- Information collected automatically
- Data that stays on your device
- What we do not collect
- How we use information
- Legal bases (EEA, UK, Switzerland)
- Who receives your data
- International transfers
- How long data is kept
- Your choices: ads, tracking, notifications
- How to delete your data
- Your rights
- Notice for US state residents
- Children
- Security
- Changes to this policy
- 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
| Data | Who receives it | Why | Optional? |
| 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:
- adding or removing favourites and watchlist items;
- rating movies and TV shows, or removing a rating;
- creating, editing or deleting custom lists (name, description, items).
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:
- From the store, the app learns which Premium product you own and the status of a purchase
(purchased, pending approval such as Ask to Buy, cancelled, failed, restored, refunded or revoked).
- On iPhone the app reads your App Store transactions through Apple's StoreKit 2 on your device. It asks the
App Store for a full re-sync, which may ask you to sign in to your Apple Account, only when you tap
Restore Purchase.
- The app stores on your device whether Premium is active and which plan you own. Whether you have Premium is
decided only on your device, from what the App Store or Google Play reports.
- Receipts and transactions are not sent to our own server or any other server we run.
- From app version 3.3.0, purchase records are also sent to RevenueCat, a subscription
service that keeps them for us. Versions up to 3.2.0 do not use RevenueCat, but once you run version 3.3.0 or
later, Premium purchases you made earlier are also sent to RevenueCat. See
4.1 below.
- Google Analytics receives Premium funnel events (for example: paywall opened, purchase button tapped, free
trial started (with the plan), purchase completed, cancelled, pending or failed with the store's error message,
restore completed, "Manage subscription" tapped (with your plan)). It also receives a
"premium: yes/no" property. Separately, Google Analytics automatically records in-app purchase events from
the App Store and Google Play, which include the product, its price and currency.
- If you allow notifications, your device joins a "premium users" or "free users" notification topic so that
announcements can be aimed at either group.
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.
- Who you are to RevenueCat: a random ID that RevenueCat's software creates and keeps on your
device. We do not give RevenueCat your name, email address, TMDB account or any other ID of ours. Apart from
your tracking-prompt status on iPhone, which RevenueCat's software adds by itself (see below), no other
information about you is added to your RevenueCat record. Deleting and reinstalling the app creates a new
ID.
- When you buy Premium: on iPhone, the app tells RevenueCat which product you bought, and
RevenueCat's software sends the App Store's signed record of that transaction (for example the product, the
transaction and its dates). On Android, the app sends RevenueCat the purchases Google Play reports for your
account, including the purchase token and order details. Later renewals and other subscription changes may also
be reported to RevenueCat.
- If you already own Premium, including a purchase made before version 3.3.0 or on another
device with the same Apple Account or Google account, the app sends RevenueCat that purchase record without a
new purchase. On Android this happens the first time version 3.3.0 or later starts and each time you tap
Restore Purchase: the app sends the purchases Google Play reports for your account, including
ones made with earlier versions. On iPhone, RevenueCat's software sends your most recent App Store transaction
that it has not sent before when the app starts or when you return to it, together with the App Store's signed
record of your app download.
- When the app starts and when you return to it, also if you never buy anything, RevenueCat's
software connects to RevenueCat. This sends the random ID, your IP address (as with any internet request), the app
version, your device model, operating system version, language settings and store country, and, on iPhone, the
Identifier for Vendor (IDFV) and whether you allowed tracking when the app asked (your answer to Apple's tracking
prompt, not the advertising identifier). RevenueCat may use it to load its own settings and to check for
purchases.
- RevenueCat is not used for advertising or tracking. The app does not send it your advertising
identifier (IDFA or Android advertising ID). RevenueCat states that it does not itself use purchase history to
track users across apps for advertising, and we do not connect it to any advertising integration. For this reason RevenueCat works whatever you answer to the tracking prompt or the ads consent
message.
- If there is a problem with a subscription payment (for example a card that needs updating), the App Store or
Google Play may show you its own message about it while you use the app.
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
| Identifier | Platform | Collected by | When |
| 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:
- an app instance ID, app version, device model, operating system and language;
- approximate location, which Google derives from a masked IP address (the app does not use GPS or location services);
- automatic events such as first open, sessions, screen views, OS updates, notification opens, and App Store / Google Play in-app purchases;
- events we define, for example:
- which movie, show or season you open, trailers you open, episodes you mark as watched, and changes to favourites, watchlist, follows and reminders. These events contain the TMDB ID of the title, not your name;
- that you searched, with the length of the search text and the tab, but not the search text;
- Premium paywall and purchase steps (see Section 4);
- ad events: impressions, clicks and the estimated ad revenue;
- settings changes, such as the theme you choose, notification preferences, how many streaming services you pick and the country you pick for them;
- that the app asked you, as a guest, to sign in with TMDB, and for which action (for example adding a favourite);
- user properties: Premium yes/no, the theme you use, and whether you are signed in to TMDB or using the app as a guest.
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):
- iPhone: the ad uses are off from the first start. The app turns them on only if you tap
"Allow" on Apple's tracking prompt and, in the EEA, the UK and Switzerland, you also consent in Google's consent
message (see 5.6); there each one follows the purposes you accepted. If you later turn tracking off in iOS
Settings or withdraw consent in the app, the app turns them off again: when you close the consent message, or
the next time the app starts or is opened again. With Premium they stay off, because Premium
users are not shown the tracking prompt or the consent message.
- Android (app versions after 3.2.0): in the EEA, the UK and Switzerland, the ad uses are off
while Google's consent message is waiting for your answer, and then follow the purposes you accepted, including
later changes in Privacy options. Premium does not change this. Elsewhere, and until the consent message has
reported your status on your device (for example just after you install the app), the app does not limit
them. Android version 3.2.0 and earlier does not limit them anywhere.
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:
- "all users";
- "new trailers" and "trending", which you can turn off in Settings → Notifications;
- one topic for your app language;
- "premium users" or "free users".
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:
- crash logs and performance data;
- a device ID (the advertising identifier or other app- or developer-scoped identifiers);
- advertising data (ads you have seen);
- coarse location, including location derived from your IP address;
- product interactions such as taps.
Google uses this data under
its own policies.
Your ad choices on a device without Premium:
- 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).
- 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:
- a random install ID that the app creates and keeps on your device;
- on iPhone, the Identifier for Vendor (IDFV); on Android, the Android OS build ID (a build label shared by all
devices running the same Android build, not a device identifier);
- the app version, the platform (iOS or Android) and the time.
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
- TMDB (api.themoviedb.org, image.tmdb.org): movie, show and people data, images, reviews and
where-to-watch information (provided to TMDB by JustWatch).
- YouTube (img.youtube.com): trailer thumbnails. Trailers open in the YouTube app or your browser,
where Google's terms apply.
- Google Fonts (fonts.gstatic.com): the app downloads some of its fonts the first time it needs them
and then keeps them on your device.
- Review avatars: TMDB review avatars may load from the address TMDB provides, such as Gravatar.
- Review images: images that authors embed in TMDB reviews are not loaded. The app
shows a link instead; it opens in your browser only if you tap it. Links in reviews open only if they are web
links.
- "Our apps": icons for our other apps load from addresses set in our remote settings.
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.
- Recently viewed titles (the last 20), "continue watching" progress and your last 10 searches.
- A viewing log for Stats and Year in Movies: titles opened, episodes marked watched and your ratings, with dates.
It covers the current year and the two previous years.
- Day streaks and badges.
- Shows you follow (with their next-episode data), release reminders and the notifications scheduled for them.
- Favourite people. These are local, not part of your TMDB favourites.
- The authors of TMDB reviews you chose to hide ("Hide reviews from …").
- Your streaming services ("My services"), saved filter sets, genres picked during onboarding, and your app
settings: language, theme, country and notification preferences.
- Premium status and plan, ad-free and unlock timers, and the install ID used by our install counter.
- From app version 3.3.0, the random RevenueCat ID and the data RevenueCat's SDK keeps on the device to work
(for example a cached copy of your purchase information).
- Your TMDB session (see 3.1).
- Cached images and fonts. Share cards are created on your device and are only shared when you choose to.
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
- Precise (GPS) location. The app does not use location services.
- Contacts, camera or microphone.
- Your photos. The app only asks for permission to add images to Photos, and only when you choose
to save a share card.
- Your payment card or bank details.
- Your TMDB password. It is sent to TMDB and not stored.
- Your name or email address, unless you email us.
8. How we use information
- To provide the app: search, browsing, where-to-watch, TMDB account features, follows, reminders and Premium.
- To keep a record of Premium purchases and subscriptions and see sales and subscription statistics (RevenueCat,
from app version 3.3.0; see 4.1).
- To send notifications you allowed.
- To show ads in the free version and measure them. Ads are personalised unless you do not allow tracking on
iPhone (or have not answered the prompt yet), do not give consent where it is required, opt out through Google's
message where your US state's law provides it, or delete your advertising ID or opt out of ads personalisation
in your Android settings (see Section 13).
- To measure and improve our own Google Ads campaigns for Watchprism, within the limits in 5.2 (on iPhone only
if you allow tracking, and never with Premium).
- To understand how the app is used and improve it (analytics).
- To detect, diagnose and fix crashes and errors.
- To count installs, updates and reinstalls of the app.
- To change settings and features remotely without an app update.
- To answer your messages.
- To comply with the law and protect the app and its users.
9. Legal bases (EEA, UK, Switzerland)
If you are in the European Economic Area, the UK or Switzerland, we rely on:
- Performance of a contract: providing the features you ask for, including TMDB sign-in and account
features, and providing Premium, including keeping a record of your Premium purchases (RevenueCat).
- Consent:
- personalised AdMob advertising and the ad-related storage that needs consent, collected through Google's consent message and, on iPhone, Apple's tracking prompt;
- the ad uses of analytics data through our Google Ads link (see 5.2), collected through the same consent message and, on iPhone, the tracking prompt;
- showing push notifications and joining notification topics, through your device's permission.
You can withdraw consent at any time (see Section 13).
Withdrawing does not affect processing that happened before.
- Legitimate interests: keeping the app stable (crash reports), understanding and improving it
(analytics measurement), counting installs, sales and subscription statistics and the RevenueCat connection at
app start and when you return to the app (RevenueCat, from version 3.3.0), creating a push token so that notifications can
be delivered, funding the free version with ads where consent is not required, and preventing abuse. You can object; see
Section 15.
- Legal obligation: where the law requires us to keep or disclose information.
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
| Recipient | What for | Their 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
- On your device: until you clear it in the app (where the app offers that, see
Section 14), sign out (TMDB session only) or delete the app.
- Crashlytics: Google keeps crash stack traces and the related identifiers for 90 days and then
starts removing them.
- Firebase installation IDs (used by Cloud Messaging and Remote Config): Google keeps them until they are
deleted. Google may delete an installation's ID after 270 days without activity. Once an ID is deleted, Google
says the data tied to it is removed from live and backup systems within 180 days.
- Google Analytics: user-level and event-level data is kept for up to 14 months; this does not
affect aggregated reports.
- Ads: Google and Meta keep data under their own retention policies.
- RevenueCat (from app version 3.3.0): purchase records are kept while we use RevenueCat, unless
we delete them earlier on request (see Section 14). RevenueCat does not publish a fixed
retention period; it keeps data under its own retention policy, which may include backups and records it needs
for legal reasons.
- TMDB account data: kept by TMDB until you delete it or your TMDB account.
- Our install counter: the records described in 5.7 are not deleted automatically. They are kept
while the install counter runs, and we delete them on request (see Section 14). IP addresses in
the hosting provider's request logs are kept under Railway's log retention.
- Emails to us: as long as needed to answer you and keep a record of the conversation.
13. Your choices: ads, tracking, notifications
Ads and tracking
- Premium removes all ads, and with them the tracking prompt, the consent form and the ads SDK.
It does not turn off Google Analytics measurement. On iPhone it also keeps the ad uses of analytics data off
(5.2); on Android it does not change them.
- iPhone: to change your answer to the tracking prompt, go to Settings → Privacy & Security
→ Tracking and turn tracking off for Watchprism. Ads will then be non-personalised, and the app turns off
the ad uses of analytics data (5.2) the next time it starts or is opened again
(Apple help).
- Android: open your phone's Settings → Privacy → Ads and choose
Delete advertising ID or Reset advertising ID
(Google help;
more ad privacy settings:
Google help).
- EEA / UK and other regions where it applies: go to Settings → About → Privacy options
in the app to review or change your ads consent. In the EEA, the UK and Switzerland your choices also apply to
the ad uses of analytics data (5.2): on iPhone together with your answer to the tracking prompt, on Android in
app versions after 3.2.0.
- US states: if the privacy law of your US state lets you opt out of targeted advertising or of the
sale or sharing of personal data, you can opt out in the app under Settings → About → Privacy options
where that item is shown, and with the iPhone and Android settings above. These cover ads in the app; the
Privacy options choice does not change the ad uses of analytics data. For those, see
Section 16.
- You can control Google's use of your data for ads in
My Ad Center.
Notifications
- Turn off "New trailers" or "Trending picks" in the app under Settings → Notifications.
- Turn off all notifications in your phone's settings: iPhone: Settings → Notifications → Watchprism;
Android: App info → Notifications. (Older Android versions of the app are called "The Movie DB" on your
phone.)
- Unfollow a show or cancel a reminder to stop its local alerts.
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
- 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).
- 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.
- 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.
- 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.
- Purchases: Apple and Google keep purchase records under their own policies. Cancelling a subscription
does not delete them.
- 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:
- access your data and receive a copy (portability);
- correct or delete it;
- restrict or object to its processing, including processing based on legitimate interests;
- withdraw consent at any time.
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:
- Identifiers: device and advertising identifiers, Firebase IDs, IP address.
- Commercial information: which Premium product you own and purchase events (including the in-app
purchase events that Google Analytics records), and, from app version 3.3.0, the purchase and subscription
records kept by RevenueCat as our service provider.
- Internet or other electronic network activity: in-app usage and ad interactions, and searches sent to TMDB.
- Approximate geolocation: derived from IP address.
- Account login: your TMDB username and password, sent directly to TMDB only to sign you in.
The sources, purposes and recipients are described in Sections 3 to 10.
- Selling: we do not sell personal information for money.
- Sharing and targeted advertising: California law calls it "sharing" when personal information is
disclosed for cross-context behavioral advertising, and other state laws speak of "targeted advertising". When the
free version shows personalised ads, Google (and, on Android, Meta through AdMob) receives your
advertising identifier and ad-interaction data to target ads. Because our Google Analytics is linked to Google Ads,
app events, including purchases, may also be used by Google to measure and target ads: on iPhone only if you
allowed tracking and do not have Premium; on Android without a limit set by the app outside the EEA, the UK and
Switzerland (see 5.2). This may count as "sharing" or targeted advertising. To opt out:
- Ads in the app: Settings → About → Privacy options, where that item is shown.
This covers ads in the app, not the ad uses of analytics data.
- On iPhone: do not allow tracking, or turn it off in Settings → Privacy & Security → Tracking.
This keeps your IDFA from AdMob and from Google Analytics, and the app turns off the ad uses of analytics
data (see 5.2) the next time it starts or is opened again.
- On Android: delete your advertising ID in your phone's Settings → Privacy → Ads. This removes the
ID; it does not stop app events from being used as described below.
- Premium removes ads, and with them AdMob's use of your data. On iPhone it also keeps the ad uses of
analytics data off. On Android it does not: app events, including your Premium purchase,
may still reach our linked Google Ads account.
- App events sent through Google Analytics on Android: the app has no in-app switch for their ad uses
today, and the choices above do not stop them (see 5.2). You can limit Google's use of your data for ads in
My Ad Center, and you can email
us to opt out. Because we usually cannot single out your installation (see Section 14),
we will tell you what we can do. Deleting the app stops all collection by the app (the store may still
report renewals of an active subscription to RevenueCat, see 4.1).
- Sensitive personal information: we use your TMDB login only to sign you in, not to infer anything about you.
- Children: we do not knowingly sell or share the personal information of consumers under 16.
- Your rights: you may ask to know, correct or delete your personal information by emailing us.
- Retention: see Section 12.
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.
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