Last updated: 2026-09-11
DekhAI is a local-first TV and movie tracking app. This policy explains, plainly, what data the app touches and where it goes. If anything here is unclear, that's a bug in the policy — not a hidden exception.
DekhAI has no backend server for your tracking data, no user accounts, and no analytics, advertising, or tracking SDKs.
Everything you track (shows, movies, ratings, watch history, lists) is stored only in a local database on your device.
The only things that ever leave your device are described below, and only when you take an action that requires them.
Search and metadata lookups (The Movie Database / TMDB). When you search for or add a show or movie, DekhAI sends that query to TMDB's API to fetch titles, posters, and details. These requests contain only the content query (e.g. a title you typed or a TMDB ID) — never your name, account, or tracking history. This is how the app gets show/movie information; it's required for search and metadata to work.
Fallback DNS lookups. If your network's DNS can't find a service the app needs (some internet providers block TMDB this way), DekhAI asks a public DNS resolver instead, over an encrypted connection: Google, Cloudflare, Quad9 or AdGuard, in turn. Only the service's hostname is sent (e.g. api.themoviedb.org), never your searches or anything about you. Where your normal DNS works, this never happens.
Watch-provider data (JustWatch via TMDB). "Where to Watch" availability is fetched from TMDB, which sources it from JustWatch. Same as above — only the title being looked up is sent, nothing about you.
Optional Google Drive backup. If you choose to back up to Google Drive, DekhAI encrypts your data on your device first (AES-256-GCM, key derived from a passphrase only you know) and uploads only that encrypted file to a hidden, app-only folder in your own Google Drive account (drive.appdata scope). DekhAI cannot read this file back without your passphrase, and neither can anyone else — including us. This only happens if you explicitly connect and back up; it never happens automatically.
Optional AI chat (bring-your-own-key). If you add your own Anthropic or OpenAI API key in Settings, the "Chat with AI" feature sends your message plus a short, aggregated summary of your local watch history (top genres, current/recently-watched titles, watchlist — never a full event-by-event history) directly from your device to the provider you chose, using your own key. DekhAI does not operate a server in this path, does not see this traffic, and does not store your chat messages — each chat session lives only in the app's memory while you're using it. This only happens if you add a key and use the chat feature.
Your show/movie tracking data, ratings, custom lists, and watch history.
Your backup encryption passphrase (never stored anywhere, including by us).
Any API key you add for the AI chat feature (encrypted at rest on-device using the Android Keystore; never transmitted to DekhAI, never logged).
No user accounts — there's nothing to create, and no DekhAI-owned database of users.
No analytics, telemetry, or crash-reporting SDKs.
No advertising SDKs.
No sale or sharing of any data, because we don't collect any to begin with.
DekhAI is not directed at children and does not knowingly collect data from children.
If this policy changes, the "Last updated" date above will change, and the new version will be published at the same location.
Questions about this policy: filestream01@outlook.com