What we keep, and what we do not.

This page describes how Kino works today. The date above reflects the last substantive change.

1. Who is responsible for your data

Kino is run by Gijs Addas, a sole trader (eenmanszaak) established in the Netherlands and trading under the name Kino.

• Address: Marnixstraat 69a, 1015 VC Amsterdam, Netherlands
• Registered in the Dutch Commercial Register (Handelsregister), held by the Chamber of Commerce (KVK), under number 91722063
• VAT identification number: NL004910829B80
• Contact: privacy@kinoapp.eu

Under the General Data Protection Regulation we are the controller of the personal data described here. For anything about your data, including a question, a request or a complaint, write to privacy@kinoapp.eu. A person reads it.

Kino is small enough that the law does not require us to appoint a data protection officer, and we have not appointed one. Privacy questions go to us at privacy@kinoapp.eu. We are established inside the European Union, so we do not need a representative under Article 27 of the GDPR, and we have not appointed one.

2. What this policy covers

The Kino app (on iOS today, and on any other platform we release it for later), the website at kinoapp.eu including the share pages that open a preview of a film, list or review, the staff dashboard, and the emails and push notifications we send.

It does not cover other people's services. Sign in with Apple, Sign in with Google, the App Store, and The Movie Database each have their own policies, and section 9 explains where the lines are.

3. The short version

• We collect what the app needs to work, and not much else.
• No advertising, no ad identifiers, no third-party trackers, no analytics SDKs. None on the website, none in the app.
• We do not sell your data or your writing, and we do not hand it to data brokers.
• We do not train generative AI models on your reviews, ratings or viewing history, and we do not let anyone else do it either.
• Your diary, reviews and lists are visible to the audience you choose, and every item has its own private setting.
• Your address book never leaves your phone. Only hashed email addresses do, and we do not keep those.
• Location is off unless you set one, and it is a place you choose, not a trail we follow.
• You can export everything we hold about you and delete your account from inside the app, without asking us. Section 13 sets out what the export contains.

The rest of this page is the detail behind those lines.

4. What we collect, and why

4.1 Your account

To sign up you need an email address, a username, and a password. We store your password only as a bcrypt hash, so we never hold the password itself and cannot recover it, not for you and not for anyone who asks. Use a password you do not reuse elsewhere. If you only ever sign in with Apple or Google, we hold no password for you at all.

While Kino is in invite-only access, you also need an invitation link we email to your address before you can register. The invitation is single-use and tied to that one address.

You can also add a name, a bio, and up to three films on your shelf shown on your profile. Those are optional and public in the same way the rest of your profile is. There is no profile picture upload; profiles show the first letter of your display name instead.

We keep a flag for whether your email has been verified, and the verification codes and password-reset tokens we send you. We never store a code or a token in the clear: we keep only a bcrypt hash of each, at the same strength as your password. An email verification code lasts 15 minutes and a password-reset link lasts 24 hours; both are single use, both stop working after five wrong attempts, and asking for a new one cancels the old one. If you change your email address, we keep a record of that change.

There is no field for your date of birth, your phone number, or your address. We do not ask, so we do not have them.

Do you have to give us any of this? No law requires it. An email address, a username and a password are what an account is made of, so without those we cannot open one for you. Everything else on this page is optional: your name, your bio, your shelf, contacts access, a saved location, push notifications. If you leave those alone, the rest of Kino works exactly as it does now, only without the feature they belong to.

4.2 Signing in with Apple or Google

If you sign in with Apple or Google, we store the stable account identifier that provider gives us, the email address it passes along, whether that address is verified, and when the link was last used. We also keep the rest of the sign-in token as the provider sends it, in a single field on the same record, which for Google usually includes your name and the web address of your Google profile picture, and for Apple includes whether the address is a private relay.

Two specifics worth knowing:

• If you use Hide My Email, what we get is Apple's private relay address. That is the address we will use to reach you, and the one in our database.
• Apple sends your first and last name once only, on the first authorisation, and never again, so we save it then. If that sign-in created your account, the name also becomes the name shown on your profile, and you can clear it there at any time. Clearing it does not remove the copy Apple sent, which stays on the record of your Apple link until you delete your account.

We never receive your password for either provider.

4.3 Your film record

Most of what we store relates to your activity in Kino:

• watches: the films and episodes you have logged, when you watched them, whether it was a rewatch;
• ratings and reviews, including whether you flagged one as a spoiler, and the edit history of a review;
• lists you make, and lists other people invited you to work on;
• your watchlist and favourites;
• comments and likes, on your own content and other people's;
• who you follow, who follows you, and any pending follow requests;
• watch-together sessions, whether you started one or were invited, including who was invited and whether each person accepted, declined or has not yet replied;
• who you have muted, and which feed items or suggestions you have hidden;
• unfinished drafts, so a half-written review survives closing the app;
• the taste answers you gave during onboarding;
• quiet signals that shape what you are shown: how you swiped each For You card, kept even if you undo it, when you last opened your feed, and which suggestions you hid.

4.4 Your settings

Theme, language, how you like runtimes and ratings displayed, how your library is arranged, how lists are sorted, which notifications you want, your privacy switches, and your saved place. We store these so your preferences stay the same across devices.

4.5 Location, only when you set one

Kino does not track your location. There is no background location, no geofencing, and the app never asks for "always" access.

You can set a location in Settings, then Location, so we can show cinema showtimes near you and pick the right region for streaming availability. You can search for a city, or tap to use your current location. Either way, turning a place name or a coordinate into a city and country is done by Apple, on Apple's servers, using the system geocoder, and city search uses Apple Maps, so the text you type and the coordinate you use go to Apple under Apple's privacy policy, not to us.

What we then store is the resulting place: latitude, longitude, the label, the ISO country code, and a search radius. It sits in your settings until you change or clear it, and your saved place is what the server reads when it shows you showtimes.

4.6 Finding people you know

If you tap "Check contacts" in Find Friends, and only then, the app asks iOS for access to your contacts. This is how contact matching works:

• the app reads email addresses only. Not names, not phone numbers, not birthdays, not photos;
• each address is lowercased and hashed with SHA-256 on your device;
• only the hashes are sent to us, up to 2,000 at a time. Your address book never leaves your phone;
• we compare them in memory against hashes of the addresses of people already on Kino, return the matches, and discard the hashes. We never write them to a database or a cache. In normal running they are never logged either; the one exception is a server error, where our error log can capture the request body, and that record is deleted with the rest of our application logs after 7 days;
• someone only appears in your results if they have "Suggest my account to others" switched on. Having somebody's email address is not their consent to be found by it.

One important point: a hash of an email address is not anonymous data. Anyone holding the hash of an address they can already guess can confirm the match. We treat these hashes as personal data, which is exactly why we do not keep them.

4.7 Push notifications and devices

If you turn on push notifications, we store the APNs device token, the platform, the device name iOS gives us, the app version, and the time that device last checked in, which the app refreshes on launch. Since iOS 16 the device name we receive is the model, for example "iPhone", rather than a name you chose, but the record is tied to your account, so we treat it as personal data and it lets you tell one device from another. We delete the record when you sign out. If Apple tells us the token no longer works, we mark the record revoked and stop sending to it, and keep the row so the same device can register again cleanly.

Release-day reminders you set for a film are scheduled on your device and never reach us.

4.8 Purchases

Kino is free. If you choose to support it, the purchase happens in Apple's App Store, and we never see your card, your billing address, or your Apple ID. When you start a purchase, the app attaches your Kino account identifier to it so that a later message from Apple about that purchase can be matched to your account; Apple receives that identifier but nothing else about you.

What Apple sends us back is a signed record of the transaction, which we keep as Apple signed it. From it we read and store the product, the amount and currency, the purchase date, Apple's transaction identifiers, the environment, and, for subscriptions, the status, renewal date and whether auto-renew is on. Apple does not send this only once: for as long as a subscription runs, Apple's servers notify ours whenever it renews, lapses, is cancelled, is refunded, or you switch auto-renew on or off. We keep this so we can show your supporter badge, avoid double-counting a transaction, and keep our accounts straight.

4.9 Importing from Letterboxd

If you import a Letterboxd export, you are uploading a ZIP that we parse into your watched films, diary, ratings, reviews, watchlist, likes and lists. We keep the parsed content as your Kino data, plus a job record with counts, timing and anything we could not match to a film so you can fix it. Everything an import creates arrives private, so nobody else sees it while the import runs. When it finishes we ask whether you want to make it public, and your answer is applied to the reviews and the watches it created. Lists an import creates are always private, and you can change a list yourself at any time. Re-importing overwrites an existing review of the same film, including one you wrote by hand.

4.10 Reports and support

When you report a review, comment, list or profile, we record who reported what, the reason, and anything you wrote, so a person can look at it. When you email us, we have your email and whatever you tell us.

If you use the form on the contact page, we store the name and email address you enter, the topic you pick, and your message, and we email a copy to the inbox for that topic so someone can answer you. We do not store the IP address the form was sent from; it is used only to count requests against a rate limit, as described in 4.11. You can ask us to delete a message you sent at any time: see section 13.

4.11 Security and audit records

We keep two kinds of operational record, plus service metrics.

• Application logs. Our per-request log line records only the method, path, status, duration and a per-request identifier, and never your IP address or your user agent. A small number of other log lines do record your IP address: when a request is refused for hitting a rate limit, and when a password reset is requested or completed or a password is changed. Credentials that ride in a query string are stripped before anything is written, though a value that sits in the path itself, such as the push token used when a device signs out, is not.
• The audit trail. Changes to accounts and content are recorded together with the actor, the action, the affected record, and a full snapshot of what that record contained, which for a review or a list includes the text you wrote. These records also include your IP address and user agent, so we can investigate abuse, account takeover and our own mistakes. A password-reset request records the address it came from.

Authorisation decisions are logged separately: we record every refusal and everything done by an administrator, and sample ordinary approvals, and these records do not carry an IP address. Service metrics (request rates, errors, latency) are not tied to you.

Rate limiting. To stop one person or one machine hammering sign-in, registration and password reset, we count requests against the IP address they come from. The count lives in memory for the length of the window and then disappears.

4.12 The waitlist

If you enter your email address on the website to ask for a place, it is stored in our waitlist. We keep the address, where the sign-up came from (for the website, simply that it was the landing page), and where you are in the queue: waiting, invited, or declined. If we send you an invitation, we record that it was sent and when.

We use it for one thing, which is to offer you a place when one opens. We do not add you to a newsletter, we do not use it to market anything else to you, and we do not pass it to anyone else. It is kept until you are invited or until you ask us to remove it.

You can ask us to remove you at any time by writing to privacy@kinoapp.eu, and we delete the entry.

5. What we do not do

Stated plainly, because the absence is the point:

• No advertising, no ad networks, no ad identifier. The app cannot even ask for tracking permission, because the code to do it is not there.
• No third-party analytics. No Google Analytics, no Firebase, no Amplitude, no Mixpanel, no Segment, no Hotjar. Nothing on the website, nothing in the app.
• No crash-reporting or telemetry SDK in the iOS app. Not Sentry, not Crashlytics.
• No attribution or fingerprinting SDKs.
• We do not sell, rent or share your data with data brokers.
• No training generative AI models on your reviews, ratings or viewing history, and no supplying them to anyone else for that. Ranking inside Kino is a different thing, described in section 12.
• No reading your content except to run the service, which means moderation when something is reported and debugging when something breaks.
• No camera, microphone, photo library, health data, calendar or contacts-beyond-emails access. The app declares no permission for any of it.

If any of this changes, we will update this page.

6. Sensitive information

We do not ask for special-category data (health, beliefs, politics, sexual orientation, ethnicity) and we do not infer it.

But a film diary can reveal a great deal about a person, and a review is a place where people often write personal things. Where you publish something of that kind yourself, we handle it on the basis that you have made it public, which is what Article 9(2)(e) of the GDPR covers. Where you keep it private, that basis does not apply, so we rely on your explicit request instead: by writing personal material into a private review, watch or list you are asking us to store it for you, and you can withdraw that at any time by deleting the item or your account. Either way we do not analyse it or infer anything from it.

7. Why we are allowed to do this

Under Article 6 of the GDPR, each purpose needs a lawful basis. Ours:

Performance of our contract with you, Art. 6(1)(b). Creating and running your account; signing you in; storing your watches, reviews, lists and follows and showing them to the audience you choose; the social features; imports; building your data export; recording your supporter status.

Your consent, Art. 6(1)(a). Access to your contacts, setting a location, push notifications, and optional emails. Each is a separate switch, off until you turn it on. Turning one on does not turn on any other, none of them is a condition of having an account, and turning one off later is exactly as easy. We keep a record of what you turned on and when. You can withdraw any of them at any time in the app or in iOS Settings, which stops the processing from then on without unpicking what was lawful before.

Our legitimate interests, Art. 6(1)(f). Keeping Kino secure and available; preventing abuse, spam and account takeover; rate limiting; the audit trail; diagnosing faults; moderating reported content. Two operations run on this basis and deserve naming: personalised recommendations, worked out from what you have logged, rated, skipped and hidden, which you can object to at any time by writing to privacy@kinoapp.eu; and the internal analytics copy described in section 10, kept so we can understand how Kino is used without querying the live system, with your email address, username, name, bio and password hash excluded from it. We have weighed these against your interests: the data is limited, the retention is short, and none of it is used to profile you commercially or shared outside Kino.

Legal obligation, Art. 6(1)(c). Keeping records we are required to keep, and responding to lawful requests from authorities.

8. Who can see what you post

Kino has two controls, and the more restrictive setting always applies:

• your account is public or private;
• each item, a review, a logged watch, a list, is public or private.

A private item is visible only to you, whatever your account says, with two exceptions you create yourself: if you invite someone to work on a private list, they can open it, and if you tag companions on a watch, they are told which film you tagged them on. Everything else marked private stays with you. A public item follows your account: visible to anyone on Kino if your account is public, and only to followers you have approved if it is private. New items default to your account's setting, decided on our servers rather than trusted from the app.

Lists carry their own switch, separate from your account. The create-list form starts a new list public, so unless you change it before saving it is public straight away; you can make it private at any time, and on a private account a public list still only reaches followers you have approved. Comments and likes inherit whatever they are attached to. Your watchlist, favourites and follows follow your account setting. Drafts are only ever yours.

Switching your account to private narrows the audience for everything already public, without changing a single item. Switching it back to public widens it again, and you will be asked to confirm first.

Two things stay visible either way: your account can still be found by name, so people can ask to follow you (turn off "Suggest my account to others" if you would rather not appear in search and suggestions), and anything you already published may have been seen, saved or screenshotted. We can change what our servers will serve. We cannot retrieve what someone already read.

One more control, and it points the other way. Muting someone removes their activity from your feed. It hides nothing of yours from them, they are not told, and it is not the same as unfollowing. Kino has no block feature yet. If you need someone kept away from your account, make your account private so only approved followers see anything, remove them as a follower, and report them to us.

Share links. A share link is meant to open a small preview page for a public item, so anyone with the link can see it and the link-preview bots of whatever you shared it into (Messages, Slack, WhatsApp, Discord) can cache a title, description and image. That preview is currently switched off: the share page asks our API for the item without signing in, and the API requires a signed-in caller, so a share link returns nothing whether the item is public or not. When we turn previews on, treat anything you share as public, because those bots keep their own copy. We ask search engines not to index those pages, but that is a request, not a control.

9. Who else your data reaches

We use a small number of outside services, and they fall into two groups.

Working for us. These act only on our instructions, under a written agreement that says what they may do with your data and forbids everything else.

• Hetzner (Germany). Runs the machines that hold the application, the database and the caches. Hetzner provides the infrastructure and does not use your data.
• Our own mail server. Account, security and notification emails are sent from no-reply@kinoapp.eu through a mail server we run ourselves, not a third-party email company.

Acting for themselves. These decide for themselves what they do with what reaches them, and each has its own privacy policy.

• Apple. Sign in with Apple, if you use it; delivering push notifications; App Store purchases, if you support Kino; and Apple Maps and the system geocoder if you search for a city or use your current location on the Location screen.
• Google. Only if you sign in with Google, and only for that.
• The Movie Database (TMDB). Our catalogue comes from TMDB, fetched by our servers with our own key, so we send them nothing about you. But posters and stills load directly from TMDB's image servers in the iOS app, on our share pages and in the staff dashboard, so your device's IP address and the image request reach TMDB in those places. The public pages of our website show no TMDB imagery, so nothing about them reaches TMDB.

We also share with:

• Link-preview bots, when share previews are on, as described in section 8.
• Authorities, where we are legally required, or where we ourselves have reason to suspect a serious threat to someone's safety, in which case we may contact them first. We will tell you unless we are forbidden from doing so.
• A future owner, if Kino is ever sold or merged. We would tell you before your data moved, and this policy would keep applying until a new one was published.

Other Kino users see whatever your privacy settings allow, which is the point of a social product but worth stating in a list of recipients. Cinema showtimes come from Cineville and geocoding for cinema addresses from PDOK, but that is us fetching data about cinemas; nothing about you goes to either.

If you are not on Kino. Some of what passes through Kino is about people without an account: a hashed email address from someone's contacts, a report that names you, or a public review that mentions you. Where data about you came from someone else, the rights in section 13 are still yours. Write to privacy@kinoapp.eu and say enough for us to find it.

10. Where your data is kept

Kino is hosted within the European Union.

The application, the database, the caches, and our logs, traces and metrics run in a data centre in Falkenstein, Germany. File storage, including the archives we build when you export your data, and our internal analytics store run on a separate machine we operate, also in the EU (Amsterdam). Traffic between the two travels over an encrypted private tunnel.

We mirror most of the database into that internal analytics store on our own hardware, so we can understand how Kino is used without querying the live system. Your email address, username, name, bio and password hash are excluded from that mirror; your reviews, watches, lists, comments and follows are in it, keyed to an account identifier.

International transfers. We do not send your data outside the EEA ourselves; everything we run is in the EU. Some of the companies in section 9 are based in the United States, and where your device or our servers talk to them, personal data does reach them there. Apple, Google and TMDB choose their own safeguards for that under Chapter V of the GDPR, normally the EU-US Data Privacy Framework where the recipient is certified, and standard contractual clauses otherwise, and their privacy policies set out which. We do not rely on your consent for any of these transfers.

11. How long we keep it

• Your account and everything in it: for as long as your account exists.
• After you ask us to delete your account: there is a 30-day grace period, during which you can cancel by signing in. Once it ends, we delete your account and content, and any remaining records are permanently erased within a further 30 days, so the full process may take up to 60 days.
• Backups: we take encrypted backups, kept in the EU, so a fault does not cost you your account. When you delete something it goes from the live service straight away, and it leaves the backups as they roll over on their own cycle. We never restore a backup to bring deleted data back.
• Data-export archives: 7 days, then automatically deleted. Deleting your account destroys any outstanding archive immediately.
• Contact hashes: not kept at all.
• Support and purchase records: kept while your account exists and deleted with it. Apple keeps its own record of the transaction under Apple's rules, which we cannot delete for you.
• Audit records: 90 days with the IP address and user agent, after which those are anonymised; the whole record is deleted at 12 months.
• Authorisation decision logs: up to 36 months, then deleted.
• Application logs and traces: set to be deleted after 7 days. Service metrics: 3 months.
• Reports you file: kept while the report is being handled and for a reasonable period afterwards, so patterns of abuse can be seen.

12. Recommendations, and automated decisions

What Kino suggests to you (For You, Explore, more-like-this) is computed from your own activity, from what people you follow do, and from the catalogue. Some of it is worked out by a separate recommendation service that we run on our own infrastructure; when it ranks for you, our system sends it your account identifier and reads your activity to do so. It affects which films you are shown and nothing else, and nothing here produces a legal or similarly significant effect on you within the meaning of Article 22.

We do not use your activity to price anything, to score you, or to decide anything about you outside the app. Kino does not currently send recommendation notifications; there is a switch for them in Settings so that if we ever start, you can turn them off first. There is no way to switch off personalised ranking itself, so we will not imply there is; what you can do is log or rate less, and the model then has less to work with.

13. Your rights, and how to use them

Under the GDPR you have the right to access your data, to have it corrected, to have it erased, to restrict or object to processing, to portability, and to withdraw consent where consent is what we rely on.

Most of it you can exercise yourself, without asking:

• Access and portability: Settings, then Privacy, then Export your data. We build a ZIP of JSON files covering your profile, settings, reviews, watches, lists, favourites, following, comments, reactions and imports, and give you a download link. It is available for seven days, and you can request up to three a day.
• Rectification: edit your profile, reviews, lists and settings directly in the app. Write to us about anything you cannot correct yourself.
• Erasure: Settings, then Account, then Delete account. You get a reminder email before it happens, your account keeps working during the grace period, and signing in and cancelling stops it. When it completes, your account and content are deleted, not hidden. Some records survive on their own timers, as section 11 sets out, because keeping a security audit trail is a legitimate interest and a legal expectation. When you correct or delete something, we pass that on to the internal analytics copy and to our backups as they roll over.
• Withdrawing consent: turn off contacts access, location, or notifications in the app or in iOS Settings.

Two things are left out of the export file, because they are as much someone else's data as yours: the list of people who follow you, and other people's comments on your content. That is a limit on the export, not on your rights. If you want either, ask us and we will give you what we can under your right of access, redacting only what would tell you more about the other person than you are entitled to know.

Your right to object, stated on its own because the law requires it. Where we rely on legitimate interests, listed in section 7, you can object at any time on grounds relating to your situation. If you do, we stop that processing unless we can show compelling grounds that override your interests, or we need it to establish or defend a legal claim, and we will tell you which.

For restriction, objection, or anything the export does not cover, write to privacy@kinoapp.eu. We will respond within one month, and tell you if we need longer (the GDPR allows up to two further months for complicated requests, and we will explain why). If we decide not to act on a request, we will still answer within that month, tell you why, and tell you that you can complain to the supervisory authority and can go to court. We may ask you to sign in or otherwise confirm who you are, because disclosing an account's data to the wrong person would itself be a serious privacy failure. None of this costs anything, unless a request is repetitive or excessive.

14. Children

Kino is for people aged 16 and over. We do not collect dates of birth and cannot verify anyone's age, so we act on what we learn: if we have good reason to believe an account belongs to someone below the age that applies to them, we close it and delete the data. If you are a parent or guardian and that describes your child's account, write to privacy@kinoapp.eu and we will deal with it quickly. Who may hold an account, including the national-age rules for people aged 13 to 15, is set out in section 3 of the terms of use.

15. Security

What we do: passwords stored as bcrypt hashes, never in plain text. TLS on everything that crosses the public internet. Access tokens that expire and refresh tokens that rotate, with a revocation list. Rate limits on sign-in, registration, password reset and other sensitive routes. An audit trail. Permission checks written once and tested against a matrix of viewer-and-content combinations, because privacy rules implemented twice are privacy rules that drift apart. A small number of people with access, and infrastructure that is not reachable from the public internet unless it needs to be.

What we do not claim: that Kino is unbreakable, that we hold any certification, or that we have been independently audited. We have not. We keep our own register of privacy and security issues and work through it.

If something goes wrong. If we find a personal data breach we assess it at once. Where it is likely to put your rights at risk we report it to the supervisory authority without undue delay and, where we can, within 72 hours, and if we are slower we explain why. Where a breach is likely to put you at high risk we tell you directly and without undue delay, in plain language. We keep a written record of every breach we find, including those that never reach the reporting threshold.

16. Cookies and similar technologies

The website uses no analytics cookies, no advertising cookies, and no third-party cookies of any kind. There is nothing to consent to, which is why you are not being asked.

The staff dashboard sets two first-party cookies: one remembers whether the sidebar is open, and one is a simple marker that you are signed in, so the site can tell a signed-in visit from a signed-out one before the page loads. Neither tracks you. Your sign-in tokens live in your browser's local storage, alongside the organisation you have selected, your light or dark theme, and, in the video editor, a local copy of your recent edits. Both cookies and that storage are strictly necessary for a signed-in session.

The iOS app stores your sign-in tokens in the iOS Keychain, marked device-only, so they are not synced to iCloud or restored onto a new phone. It also keeps a few preferences and recently-viewed items in local storage on the device, which never leave it. There are no tracking technologies in the app at all.

17. Changes to this policy

We will update this page when what we do changes. For material changes we will email registered users at least 30 days beforehand and update the date at the top. Smaller clarifications take effect when published. If a change means we would process your data on a new basis that needs your consent, we will ask for it rather than assume it.

This page is written in English. If you use Kino in another language and English is difficult for you, write to privacy@kinoapp.eu and we will explain any part of it in the language you prefer.

18. If you think we have got it wrong

Tell us first: privacy@kinoapp.eu. We will do our best to resolve the issue directly.

You also have the right to complain to a data protection supervisory authority, whether or not you talk to us first. You can go to the authority in the EU country where you live or work, or where you think the problem happened. Because we are established in the Netherlands, our lead supervisory authority is the Autoriteit Persoonsgegevens (the Dutch Data Protection Authority), Postbus 93374, 2509 AJ Den Haag, reachable at autoriteitpersoonsgegevens.nl. Separately from any complaint, you can also take us to court if you believe we have breached your rights under the GDPR.

19. Contact

privacy@kinoapp.eu for anything on this page, or by post to Gijs Addas, Marnixstraat 69a, 1015 VC Amsterdam. Our full details are in section 1.

For everything else, the contact page is faster. The terms of use cover the rest of the relationship.