My Films
Privacy Policy
This policy explains what data the My Films app collects, why, who receives it, and how you can delete it.
Updated: 7 October 2026
1. Who is responsible
Data controller:
FOP Maharyta L.L. (sole proprietor)
Ukraine, Uzhhorod
Email: office@markodesign.net
There is no EU representative. Privacy and support requests go to the same address.
The service is the My Films mobile app and the server at myfilms.markodesign.net.
2. What this policy covers
It covers your My Films account, data in the app and on our server, and this public page.
We do not sell data and we do not show personalised ads. There are no advertising SDKs and no advertising tracking (we do not use App Tracking Transparency).
3. What data we process
Account
- Phone number — login and account identifier. It cannot be changed in the app.
- Name and, optionally, a profile photo (stored on our server).
- Invite code for the cinema hall, interface language, notification settings.
Collection and taste
- Movie and series lists, ratings, watch status, “not interested”.
- A taste profile (genres, actors, directors, favourite titles) built from your collection.
- Cinema-hall friends and family (shared collection).
Phone contacts
If you allow access, the app reads contacts on the device to see who already uses My Films. Only phone numbers (in international format) are sent to our server, not your full address book. Numbers that are not My Films users are not stored as contacts. To prevent abuse we may keep hashes of looked-up numbers until the end of the day (not the list of names).
Camera, photos, microphone
- Camera / photos — search by a poster or still, and (separately) your profile photo.
- A search photo is sent to our server and then to Google Gemini for recognition. That photo is not stored on your account; a technical cache of the result (keyed by image hash) is kept for up to 30 days.
- Microphone and speech recognition — to dictate a title for search. On iOS, recognition is provided by Apple; we receive the query text, not the audio recording.
Notifications
A Firebase Cloud Messaging (FCM) device token so we can send pushes about the cinema hall, new seasons, and app updates (by interface language). You can turn off types of pushes in Profile. Once a day we send a silent technical push with no content to the token — the notification service’s reply tells us whether the app is still installed (so we stop pushing to removed devices and can measure churn).
Technical and security data
- IP address, a device identifier (for SMS limits), request times.
- SMS log: number, country, purpose (login / register / delete), delivery status — without the code itself.
- Verification codes are stored hashed and last about 10 minutes.
- Security events (for example, too many contact lookups).
- The app session token (about 60 days, or until logout / account deletion).
- Firebase Crashlytics — crash reports in release builds.
- Firebase App Check (iOS) — checks that the request comes from the official app.
Moderation: reports and blocks
When you block someone, we store the fact of the block (who blocked whom, and when) — without it blocking could not work. When you send a report, we store the category, your text, the date, and the moderator's decision. These records let us meet the App Store requirement to act on reports, avoid handling the same report twice, and spot systematic abuse; they live as long as the account does and are deleted with it. The person you report does not see your name, and a blocked person receives no notification.
Website testing feedback
If you send testing feedback from the landing page, we store your name, the message, optional email, page language, IP address, and User-Agent. We do not accept file uploads.
4. Why we use the data
- Create and protect your account (SMS code).
- Sync collection, friends, and family across devices.
- Search titles (including by voice and photo) and show catalogue, trailers, and where to watch.
- Remind you about new seasons and cinema-hall events.
- Limit abuse (SMS, contact lookup, and AI-photo caps).
- Fix bugs (crash reports).
- Read testing feedback submitted from the website form.
Legal bases under the GDPR (if you are in the EEA / UK): performance of a contract (the account and the service), consent for device permissions and optional features (camera, contacts, microphone, pushes), and legitimate interest in security, anti-abuse, and keeping the service reliable.
5. Who we share data with
We share data only with providers the service needs. We do not sell data to third parties.
- SMS Club (Ukraine) — sending the code to your number.
- TMDB (The Movie Database) — search and movie/TV metadata. Requests may include search text and title IDs, not your phone number.
- Google Gemini — photo recognition, search hints, taste summaries, “what to watch”, and sometimes season dates. Gemini may receive a search photo, short lists of titles/genres/actors, and query text. The Gemini key lives only on our server.
- Google Firebase — FCM (push token), Crashlytics (crashes), App Check (app attestation).
- Apple — speech recognition on iOS if you dictate a title.
- TVMaze, OMDb, Cinemeta, Wikidata, YouTube — season dates, IMDb ratings, trailers. Usually without your name or phone; film identifiers only.
Some providers (Google, TMDB, Apple) may process data outside Ukraine and the EEA, including in the United States. That is required for search, AI, pushes, and speech recognition to work.
6. How long we keep data
- Account and collection — until you delete the profile.
- SMS codes — about 10 minutes (hash); SMS send logs and security events — 90 days; unused OTP rows — 1 day.
- Login token — up to about 60 days, logout, or account deletion.
- AI photo cache — up to 30 days.
- Other AI caches (search, taste, “what to watch”) — from 12 hours to 7 days.
- Contact-lookup hashes — until the end of the day.
- Landing-page feedback — until we delete it after review.
After account deletion, the profile, server collection, cinema-hall friends, and family tied to that account are removed. Server backups may still hold remnants until they are overwritten.
7. How to delete your data
In the app: Profile → Delete profile, confirmed with an SMS code. This cannot be undone.
Step-by-step (including if you already uninstalled the app): myfilms.markodesign.net/en/delete-account.
If you already uninstalled the app, email office@markodesign.net from that same phone number and ask us to delete the account. We may ask you to prove the number is yours.
You can also remove the profile photo, turn off pushes, or revoke camera / contacts / microphone access in system settings — those features will then stop working.
8. Your rights (including GDPR)
You may request: access, correction, deletion, restriction of processing, objection to processing based on legitimate interest, withdrawal of consent (device permissions), and data portability where technically feasible.
Email office@markodesign.net. We will respond within a reasonable time.
Complaints: the Ukrainian Parliament Commissioner for Human Rights; if you are in the EEA, also your local supervisory authority. We have not appointed an EU representative.
9. Children and age
The app does not check age at registration. TMDB search runs with adult titles filtered out (include_adult=false), but posters and descriptions can still include mature themes.
My Films is not directed at children, and we do not knowingly collect children’s data. If you believe a child created an account, write to us and we will delete it.
11. Changes
If how we process data changes, we will update this page and the date at the top. Material changes may also be announced in the app.
12. Contact
Privacy, account deletion, and support: office@markodesign.net.
FOP Maharyta L.L., Ukraine, Uzhhorod.