Privacy Policy
Last updated: September 17, 2026
IchnosTV is built around a simple idea: your data belongs to you. This policy explains what information the app uses, where it is stored, and who can see it. In short — your library and watch history are stored on your device and, if you enable sync, in your chosen personal cloud storage. We do not operate a library-storage database. We do collect device-linked diagnostics and usage data to fix bugs and improve the app, and operate a proxy that forwards catalog requests to TMDB. Diagnostics use persistent random identifiers; they are not anonymous.
Who we are
“IchnosTV”, “we”, “us”, and “our” refer to the developer of the IchnosTV mobile and desktop applications and this website (ichnos.tv).
The short version
- We do not operate any database or backend that stores your library or watch history.
- Your library (the shows, episodes and movies you track) is saved locally on your device. If you enable sync, a private copy is stored in your own Microsoft OneDrive, Apple iCloud, or Google Drive.
- We collect crash and error reports, technical context, feature-use events, sync duration, and tip-attempt tiers and outcomes. These records are linked by installation and session identifiers.
- We do not sell your data, show ads, or build advertising profiles.
- Cloud sync is optional. Microsoft and Google handle their own authentication; iCloud uses the account already connected to your device. We never see your password.
Information the app uses
The app stores the library locally. If you enable cloud sync, it also works with:
- Cloud authentication. Microsoft or Google provides the app with a token and basic profile information (such as your name or email) so it can access your private app folder. iCloud uses the device's existing iCloud session and does not provide IchnosTV with an Apple identity. Account profile fields and tokens are not deliberately included in our usage-event properties; error-report limitations are explained below.
- Your tracking library. The shows and movies you add, their watch status, and the episodes you mark as watched are stored locally. When sync is enabled, a copy is stored as a single private file in your cloud account's app folder. This copy includes library settings and device identifiers used to merge changes between devices.
- On-device cache. Show details, descriptions, cast information, and images are cached locally on your device so the app works offline. This cache lives only on your device.
Where your data is stored
Your library is stored on your device. If you enable sync, a private remote copy is stored with the provider you connect:
- Microsoft → a private application folder in your OneDrive.
- iCloud → your iCloud app container (used only on iOS).
- Google → a hidden application-data folder in your Google Drive (used only on Android).
These folders are scoped to the app. The app accesses them on your behalf; our catalog proxy and diagnostics service do not receive a routine copy of your cloud library. This does not prevent individual content details from appearing in catalog requests or error messages.
Diagnostics and usage data
To keep IchnosTV stable and to understand which features people actually use, the app sends diagnostic and usage information to Microsoft Azure Application Insights. Diagnostics are enabled in the app's standard configuration, including at startup before onboarding or cloud sign-in. There is currently no in-app diagnostics opt-out, and disconnecting cloud storage does not stop diagnostics. We use these records for bug diagnosis, performance and feature-use analysis, not targeted advertising.
What we collect:
- Crash and handled-error reports — error types, messages, inner errors and stack details when something goes wrong. Stack details can include file paths and line numbers when available.
- Usage and performance events — app launches, cloud connection and disconnection (including provider), completed syncs (including trigger and duration), TV Time import result counts, and show-completion actions without a title field.
- Tip outcomes — the selected tip tier and whether an attempt succeeded, is pending, was canceled, or failed. These events describe purchases or purchase tendencies, although they do not contain card details, receipt/transaction IDs or exact prices.
- Technical context — app version, platform, operating-system version, device model, event time and SDK context. The telemetry SDK also attempts to include a machine/host name; its value depends on the platform and can be identifying.
- Random identifiers — a persistent installation/device id and a new session id for each app run, allowing us to correlate records across sessions. The installation id is also used by the app's library/sync data.
Limits on these assurances: our explicit event properties do not include account names, emails, sign-in tokens, search text or library titles. However, the app forwards original error messages without a general personal-data redaction step. Errors may contain paths, URLs, library identifiers or account/provider information. We therefore cannot guarantee that diagnostics contain no personal or library data.
The installation id is randomly generated rather than taken from your cloud account, but it remains a device-linked identifier while app preferences survive. Reinstallation or restoring a device backup is not a guaranteed reset. A random id or limited retention does not make these records anonymous or impossible to link.
Network services receive an IP address when contacted. Application Insights normally derives approximate city, region and country before masking the stored IP address (Microsoft's documented behavior). IP masking does not by itself remove the derived location. The app does not request GPS coordinates for diagnostics.
Our infrastructure configuration specifies a 90-day telemetry workspace retention period. This is not a verified maximum for every deployed table, export, backup or service log. The configured ingestion endpoint is in Azure West US 2; Microsoft's service terms govern further processing. Contact us about retention or deletion of diagnostic records.
Third-party services
- Microsoft Azure Application Insights. Receives the device-linked diagnostics, usage and tip-outcome information described above. See the Microsoft Privacy Statement.
- The Movie Database (TMDB). Series, season, episode and movie information and
artwork are provided by TMDB. In the standard app configuration, catalog requests
(including search text, title identifiers and filters) pass through our Azure-hosted
ichnos.tv/api/tmdb/proxy to TMDB; image requests go directly to TMDB. The proxy uses IP-keyed counters across requests to limit abuse. Its default window is 60 seconds, with expired entries cleaned on subsequent traffic, not a guaranteed deletion timer. It logs operational warnings and upstream errors; hosting/network services may retain additional request logs. We have not verified all deployed log settings or TMDB's retention, so cannot promise that search or request data is never retained. This product uses the TMDB API but is not endorsed or certified by TMDB. See the TMDB Privacy Policy. - Cloud providers. Microsoft and Google handle authentication and cloud storage; Apple hosts iCloud data using the account connected to the device. Their own privacy policies apply.
- Apple services and external links. If you invoke Siri/Shortcuts, requested library information can be returned to Apple's assistant. Optional iOS tips are handled by StoreKit; we separately record the tip tier/outcome described above. Related-video links open YouTube outside the app. These services apply their own privacy terms.
What we do not do
- We do not use these records to build targeted-advertising profiles.
- We do not use our diagnostics to identify you or track you across other apps or websites.
- We do not sell or rent personal information. We disclose information to the service providers described in this policy to operate and improve the app.
- We do not serve advertising.
Deleting your data
You can remove tracked titles in the app, disconnect cloud storage to stop syncing, or use the Profile deletion flow to clear the library on this device and in the connected cloud account. You can also manage the app's cloud files through your provider. These actions do not erase diagnostics already sent to Azure or service logs, and the library-delete flow does not reset the diagnostics identifier. Device/cloud backups may retain their own copies. Contact [email protected] about diagnostic-data requests; do not send passwords or sign-in tokens.
Children's privacy
IchnosTV is not directed to children under 13 (or the equivalent minimum age in your country) and we do not knowingly collect personal information from them.
Changes to this policy
We may update this policy from time to time. Material changes will be reflected here with a new “Last updated” date.
Contact
Questions about this policy? Email [email protected].