PopcornMe Privacy Policy
1. Controller and contact
The controller of personal data is Łukasz Krajewski, a natural person operating the PopcornMe application from Poland.
Contact for privacy matters and exercising your rights: privacy@popcornme.app.
No Data Protection Officer has been appointed. Messages concerning personal data are handled by the controller.
2. What data we process and why
| Category | What it covers | Purpose | Basis in the EEA |
|---|---|---|---|
| Email account | email address, display name, internal account identifier and a password hash created using scrypt. We do not store the password in plain text. | creating, securing and operating your account | Art. 6(1)(b) GDPR |
| Google sign-in | Google account identifier and the data shared by Google during sign-in, in particular email address, name and — where available — the avatar address | signing in and linking the account | Art. 6(1)(b) GDPR |
| Settings | language, country and selected streaming services | tailoring the interface and title availability | Art. 6(1)(b) GDPR |
| Rooms and matches | room membership, room code, filters, the title pool, card decisions (“yes”, “no”, “seen it”, “not tonight”) and matches | the core function of the app — finding a title both people like | Art. 6(1)(b) GDPR |
| Hidden titles | titles you rejected or marked as seen, together with the reason and the date. The record is tied to your account, not to a single room, so it also applies in later rooms | so the same titles do not come back in later sessions. You can see the full list in the app (Settings → Titles you hid) and remove any entry from it | Art. 6(1)(b) GDPR |
| Age declaration and privacy choice history | the fact that a declaration of being 16 or older was made, its date, language and the version of the text shown; the history of granting or withdrawing consent for features that require it | enforcing the 16+ requirement and accountability | Art. 6(1)(b) and (f) GDPR; for consents — Art. 6(1)(a) |
| Push notifications | device identifier/token in Firebase Cloud Messaging, platform, language, date of last activity and the content of the notification sent | sending optional notifications | Art. 6(1)(a) GDPR |
| Reports and safety | who reported whom, the reason for the report and the data needed to handle it | preventing abuse and protecting users | Art. 6(1)(f) GDPR |
| Technical server logs | IP address and standard technical data of the HTTP request, without an account identifier in ordinary user logs | security, fault diagnosis and protection against abuse | Art. 6(1)(f) GDPR |
| Crash reports | error type, stack trace, app version, platform and language; no account, device or session identifier | diagnosing and fixing faults | Art. 6(1)(f) GDPR |
| App usage statistics | aggregate event counts (for example how many times the app was opened, how many sign-ups were started and completed), no account, device or session identifier | product development; collected only with consent, which can be withdrawn in settings | Art. 6(1)(a) GDPR |
| Own advertising statistics | aggregate impression and click counts, without a user identifier | measuring the performance of our own advertising campaigns | Art. 6(1)(f) GDPR |
We delete crash reports after 90 days. Usage statistics are aggregate and cannot identify a person, so they are not subject to access or erasure requests.
We do not collect precise location data, phone contacts, device contents, payment data, health data, Advertising ID or IDFA. We do not currently use behavioural analytics. We do not build an advertising profile or a taste profile of the user.
3. The privacy of your title decisions
The other person in the room does not see your individual “yes/no” decisions. A title becomes a match only once both people have liked it. The administration panel does not show the content of individual decisions.
The same applies to the summaries in the app (“Your summary” and the session summary). They contain only your own decisions and the number of shared matches. They do not show how many titles the other person liked or rejected, nor any figure from which that could be worked out.
As the person administering the infrastructure, I have technical access to the database, so during maintenance or while handling an incident access to data may be technically possible. Administrative access is limited to one person and is not used to look at users' preferences.
4. Providers and external connections
| Entity / service | What it receives or stores | Role |
|---|---|---|
| OVHcloud — server in France | production database and application data | processor |
| sldc.pl / LiveNet — Poland | outgoing email and encrypted database backups | processor |
| Google — sign-in | when you choose “Sign in with Google”, your device communicates with Google; we receive from Google the data needed for authentication | Google processes data on its side under its own rules; PopcornMe receives the sign-in result |
| Google Firebase Cloud Messaging | installation identifier/token and the content of the push notification | processor in respect of the data passed on by PopcornMe |
| TMDb | catalogue requests from the backend contain no user data; when posters and backdrops are downloaded directly, TMDb sees the device's IP address | external content provider |
| YouTube | when you play a trailer, the device connects to YouTube; YouTube sees, among other things, the IP address and technical information about the connection | external content provider |
This product uses the TMDb API but is not endorsed or certified by TMDb.
5. Where the data is and international transfers
The main database is located on an OVHcloud server in France. Backups are stored locally on the main server and at sldc.pl in Poland. The copy sent to sldc.pl is encrypted with AES-256 before it is sent.
Some Google services may process data outside the EEA. For Firebase, Google provides the transfer mechanisms described in its data processing terms, including — depending on the direction of the transfer — the EU-US Data Privacy Framework or standard contractual clauses. Direct connections to Google, TMDb or YouTube may likewise result in technical data being processed outside the EEA in accordance with those providers' rules.
6. How long we keep data
| Data | Retention |
|---|---|
| Account and preferences | until the account is deleted |
| Rooms, filters and the title pool | until the room expires, then in line with the app's clean-up mechanism |
| “Yes/no” decisions and matches | until the account is deleted; afterwards data about a shared match may remain with the other participant only in a form that does not identify the deleted user |
| Hidden titles | until you un-hide the title in the app or the account is deleted |
| Push token | until consent is withdrawn, you sign out, the token is invalidated or it is removed by the app's mechanism |
| Safety reports | 12 months after resolution, unless longer retention is needed to defend claims or comply with a legal obligation |
| Server logs containing IP addresses | 14 days, then automatic rotation/deletion, unless a specific entry has to be preserved for the duration of an incident analysis |
| Backups | 30 days; after data is removed from the production system it may remain in an existing backup until that backup is automatically overwritten |
| Aggregate data that does not allow a person to be identified | indefinitely |
7. Deleting your account
You can delete your account in the app: Settings → Delete account. You can also send a request to privacy@popcornme.app from the email address linked to the account.
Once deletion is confirmed, the account and the data linked to it are removed from the active system. Backups are not restored in order to recover a deleted account and disappear automatically as backups rotate, at the latest within 30 days of the data being removed from the production system.
8. Your rights
Where the GDPR applies, you have the right of access to your data, rectification, erasure, restriction of processing, data portability, and objection to processing based on legitimate interests. You may withdraw consent at any time without affecting the lawfulness of processing carried out beforehand.
Send your request to privacy@popcornme.app. As a rule we reply within one month.
In the EEA you may lodge a complaint with the competent supervisory authority. In Poland this is the President of the Personal Data Protection Office (PUODO).
9. Age of users
PopcornMe is intended for people who are 16 years of age or older. On first launch the user makes a declaration that this condition is met; we record the fact that the declaration was made, its date, the language and the version of the text shown. We do not ask for a photograph of an identity document or for biometric data.
If we learn that an account belongs to a person under 16, the account will be blocked and deleted.
10. Security
- connections to the backend are encrypted with HTTPS;
- passwords are not stored in plain text — we store only scrypt hashes with a salt;
- the session token on Android is stored in the secure system store;
- access to the administration panel is protected by an additional TOTP factor;
- administrative operations are recorded in an audit log;
- external backups are encrypted before being sent.
11. Advertising, affiliate links and future changes
The current version does not use AdMob or any other external advertising network and does not use personalised advertising. Our own advertising material may be selected contextually by placement, language and country, without a user profile.
If in the future we launch AdMob, advertising identifiers, affiliate links or another tool that changes how data is processed, we will first update the app, the consent settings (where required), the Google Play Data Safety form and this policy.
12. Users outside the EEA
PopcornMe is operated from Poland. If your local privacy law grants you additional rights, we will give effect to them to the extent that it applies to PopcornMe. We do not sell personal data and do not share it for behavioural advertising across different services.
13. Changes to this policy
We will give notice of material changes in the app. The date of the current version is at the top of this document.