TeevyTime

TeevyTime

Privacy policy

Last updated: 5 August 2026

This policy describes the data TeevyTime uses, why it is used, and your rights.

Controller and contact

Data controller: Mehdi Chennoufi.

Privacy contact: teevytimeapp@gmail.com.

The publisher provides this service on a non-professional basis and keeps personal identification details with the host, in accordance with the applicable regime.

Data and purposes

TeevyTime processes the technical account identifier and identity data supplied by Google or Apple (email and, where provided, name), your library, viewing status, watched episodes, preferences and optional feedback. It provides account access, synchronisation, import/export, support and service security; it does not sell data, run behavioural advertising or make automated decisions with legal effects.

TV Time import and catalogue

The TV Time archive is read on your device. The extracted data required to match and apply the import are sent to the server; the raw ZIP file is not uploaded by this feature. TMDB provides movie catalogue data and TheTVDB provides series catalogue data. VOD availability is provided by JustWatch via TMDB.

Recipients, retention and rights

Necessary processors are Supabase (authentication, database and functions), Firebase App Hosting / Google Cloud (hosting), Google or Apple (sign-in), TMDB (movies and VOD availability), and TheTVDB (series). Account and library data are kept while the account is active; browser cache remains until cleared. Contact the publisher shown on this page to exercise access, correction, deletion, restriction, objection or portability rights. Account deletion is available from Settings. You may lodge a complaint with the CNIL.

Declared App Hosting region: Firebase App Hosting / Google Cloud — europe-west4 (Pays-Bas). Declared Supabase region: Supabase — eu-north-1 (Stockholm, Suède).

Security

Authenticated access is restricted by database rules and traffic uses HTTPS.

Transfers outside the EEA

Certain data necessary for the operation of the service may be processed by Supabase and Google/Firebase, including outside the EEA. Where processing involves a transfer outside the EEA, it is governed by the transfer mechanism under Chapter V of the GDPR applicable to the recipient and the relevant flow, including an adequacy decision or appropriate safeguards such as standard contractual clauses. The documents relating to these safeguards may be requested from the publisher.