Privacy Policy

Last updated: 8 June 2026

This policy explains what data ReelWatch collects, how we use it, who we share it with, and the choices you have. We’ve written it in plain English.

Who we are

ReelWatch (“ReelWatch”, “we”, “us”) is the provider of the ReelWatch mobile app and is the party responsible for the data described here. There is no separate registered company. You can reach us at reelwatchsupport@gmail.com.

Account information

We use Clerk to manage sign-in and accounts. You can sign up with email and password, Google, or (on iOS) Apple Sign-In. Clerk stores your email address and a small amount of profile metadata. We store your chosen region in your Clerk profile metadata.

If you use Apple Sign-In, Apple may share your name and email with us the first time you sign in. The identity token Apple provides is verified on our server to confirm it’s genuine.

Data we store in our own database

ReelWatch keeps its own PostgreSQL database (hosted on Replit) containing:

Shared links and on-device processing

When you share a link from TikTok, Instagram, Facebook or YouTube Shorts (or paste a URL), that link is sent to our server so we can identify the title. Our server reads only public information from the linked page — such as the page title, the description or caption, hashtags, any quoted dialogue, the author/account name, and the thumbnail image.

For Instagram, the app reads the post’s public caption, author and thumbnail on your device and sends only those extracted details to our server. The raw page content does not leave your device.

AI processing (fallback only)

When our standard, non-AI matching isn’t enough to identify a title, we fall back to an AI provider, Anthropic (Claude Haiku), to help. Only in that fallback case do we send Anthropic: the source platform, the shared link, the page title/caption, the description/caption text (truncated), hashtags, any quoted lines, and the author/account name. For image-based identification we also send the post’s thumbnail image. We do not send your watchlist, account details, or contact information to the AI.

Third-party services we use

These providers may process data in countries outside your own (see International processing below).

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

Server logging

Our server keeps standard request logs recording the HTTP method, the request path (with query strings stripped out), the response status code, and a request id. Authorization and cookie headers are explicitly redacted from these logs. We do not sell your data.

How your data is linked to you

Your watchlist, selected services, and region are linked to your account. Event logs (detection, click and search) are linked to you when you’re signed in.

ReelWatch does not use third-party advertising or cross-app tracking, advertising SDKs, or device advertising identifiers. We do not use your data for advertising, and we do not sell personal data.

Deleting your account and your data

You can permanently delete your account at any time from the app: open the Settings tab and tap Delete account, then confirm. This permanently deletes all of your ReelWatch data — your watchlist, your selected services and region, and your detection, click and search event records — from our database, and deletes your Clerk sign-in identity. Local data on your device is also cleared.

You can also email reelwatchsupport@gmail.com to request deletion. We retain your data only for as long as your account exists; once you delete your account, your data is removed.

International processing

ReelWatch and the third-party services listed above operate internationally, so your data may be processed and stored in countries other than the one you live in.

Changes to this policy

If we make material changes to this policy, we’ll update the “last updated” date above.

Contact

Questions about your privacy? Email reelwatchsupport@gmail.com.