Privacy

No account, no cookies, just to read the site.

If you sign in, we keep as little as we can, only to run the site, and never sell or share it for advertising.

Last updated 20 November 2026.

Who is responsible

The site is run by volunteers of AFiG: Amsterdam Film Group, a film group in Amsterdam. Responsible for your data (the controller, in the GDPR’s words) is Juanma (Juan Mauricio Torres Perez), one of the group’s hosts, who runs the site, in Amsterdam. Write to hello@afig.nl about anything on this page.

When you read the site

  • Cloudflare hosts the site. Like any web server, it receives your IP address and browser details to send you the pages and to keep the site safe, and keeps technical logs of requests for up to 7 days to find errors. A visit from China is first checked by Cloudflare to tell a person from a program, usually without a puzzle: nearly all the site’s traffic from there came from programs. Passing the check leaves one cookie, cf_clearance, for 30 minutes, so it isn’t repeated on every page; it is needed to keep the site safe, so the site doesn’t ask for consent.
  • Images from other sites: event pictures load from Meetup’s servers and film images (posters and stills) from TMDB’s, so your browser connects to them, and they see your IP address, as with any image on the web. Both are US companies.
  • Your browser remembers the theme, only if you pick one (Light or Dark), and that you chose “Not now” on the card inviting you to add AFiG to your home screen, only if you do. Both stay in your browser; we never receive them. Nothing else is kept there.
  • The app: if you add AFiG to your phone’s home screen, the app keeps one page on your phone, the one it shows when you’re offline, with the styles and fonts that draw it. It is the same for everyone and holds nothing about you. Removing the app, or clearing the site’s data in your browser, removes it. A page opened in the browser keeps nothing of the kind.
  • Notifications: if you turn them on in the app, we keep your phone’s subscription (an address at your phone maker’s push service, Apple’s, Google’s, Mozilla’s or Microsoft’s, and the keys to encrypt for it), the notifications you chose on your account page, and which ones we sent you, for 60 days, to send each only once and only a few a day. Each goes encrypted through that push service, which carries it but can’t read it. Turning them off on that phone, signing out there or deleting your account deletes the subscription; one that took no notification in six months goes by itself.
  • Counting visits: Cloudflare Web Analytics counts how the site is used without cookies and without keeping anything in your browser. It notes the page, the site you came from, your browser and device type, your country and how fast the page loaded, and shows us only totals, never who visited, for up to six months. No tracking across sites, no advertising cookies. The hosts’ own visits, while signed in, aren’t counted.
  • Counting what’s used: the site itself counts, day by day, how often a film’s page is opened and from where (a search, an event’s page), whether a search found anything, which filters are used, how often an event’s page is seen and from where (Upcoming, the evenings added this week, Going, another page of the site or outside it), its buttons are used (Add to calendar, Meetup, tickets, I’m going, Share) or its newsletter link followed, where the newsletter is asked for (the agenda, an event’s page or its own page), how often a film is shared, how often Going is opened, how often the app is opened from its icon on a phone, and how often a page isn’t found (for an event’s or a film’s address only its number, otherwise only the part of the site it was under or that it is one robots try; never the address itself). Only the numbers are kept, by the day: never your IP address, your account, your browser, what you typed or the time of day. To leave robots out, the site looks at your browser’s name as the page loads or a button is pressed, and at whether your connection comes from a cloud or data centre (by its network’s number, which Cloudflare gives with every request), and keeps nothing of either. The site’s admins see the totals. The hosts’ own visits, while signed in, aren’t counted.
  • The site never shows the public which members go to an event, only how many: Meetup’s RSVPs and the site’s together. The group’s hosts see who said they’re going here (Signing up for an evening, below). Each event’s page shows its description as the host wrote it on Meetup, which may give the host’s first name or where they sit, so you can book nearby.

For hosts

The hosts’ sign-in emails are kept in a list only the site’s software reads, to open the host tools to them. An admin brings the events in from our Meetup page by copying it by hand: the page also names some members who are going, and the site discards those names at once and never keeps or shows them. Of each event’s hosts, it keeps their Meetup member numbers until the evening starts, never Meetup’s names. An admin gives each host a name, which shows as Host on their evenings, on the evening’s page and in Upcoming, for everyone; the host changes it on their account page, and an admin takes it away when they stop hosting, or when they ask. A host who links their account to their Meetup profile, once an admin has confirmed it’s theirs, gets one email a day about who signed up on the site for the evenings Meetup has them on; until then the admins see the link with the host’s name and email, and get that email instead. A host who writes the newsletter’s note signs it with their first name; it goes to every subscriber and stays with that issue. A host who puts a film on the hosts’ shortlist is shown to the other hosts with their first name and any note they add, until they take it off, the group makes an event with the film, or three months pass; members never see it. An admin can look at the site as a member or as a host sees it: a cookie in their browser keeps that choice for up to 12 hours, until they switch back. The hosts’ own visits aren’t counted. A host whose Meetup link an admin confirmed can add a photo of themselves on their account page: it shows beside their name as Host to those going to their evenings, and to the hosts, until they remove it or their account goes. A host who posts where the group is on an evening’s page (below) shows under their name as Host.

When you sign in

You sign in to say you’re going to an evening, keep a watchlist, recommend films and rate the evenings, in one of three ways; with the same email address, they all lead to the same account. There are no passwords.

  • With Google. Google tells us your name, your email address, whether Google verified it, and an id for your Google account. We keep those, with when you signed in and last used the site, only to know it’s you. We don’t keep your Google picture, your password (we never see it) or any access to your Google account. Google knows that you signed in to this site; see Google’s privacy policy.
  • With a code by email. We keep your email address. To send the code, we give your address and the code to Brevo, an email service in the EU that sends it for us and keeps its record of the email for 30 days; the code itself is stored only in a scrambled form, and only until it is used or expires after 10 minutes. For a day after the first code, we note how many codes your address was sent and how many wrong codes were typed for it, so nobody can keep asking or guessing. Before sending, Cloudflare Turnstile checks in your browser that you’re not a robot, usually without a puzzle; see Cloudflare’s Turnstile privacy notice.
  • With a passkey, once you’ve added one on your account. Your phone or computer keeps its secret part and never sends it; we keep only the public part, which checks it, with the kind of device and when you added it. You can remove a passkey there at any time.

Two cookies keep you signed in: one for up to 90 days, renewed while you use the site, and one that remembers your session for 5 minutes so the site stays fast. A third lives up to 10 minutes while you sign in. All are needed for signing in, so the site doesn’t ask for consent. We don’t keep your IP address with your account.

Your name is the one you give us: we ask everyone for the name the group knows them by, once, before anything else, with Google’s filled in to keep or change if you signed in with Google, and keep when you gave it. The hosts see it beside what you send them, so they know who it is: saying you’re going to an evening, recommending a film, writing a line on one. Its first word signs your rating lines. Change it on your account page.

When you recommend

What you send in Recommend (a film, and a note if you add one) is kept with your account. The group’s hosts, a few volunteers, see it with your name and email, so they can reply. Other members never see who recommended what. You can withdraw a recommendation yourself at any time.

When you rate an evening

When you rate a film the group saw, we keep your stars, and your line on it if you write one, with your account. Everyone who visits the event’s page sees the group’s average, once three have rated, with how many gave each number of stars, and your line with your first name, never your stars on their own. The page is public, so search engines such as Google can show your line and first name too, and a line you remove can stay in their results until they read the page again. If your account has no name, we ask for a first name when you write a line, and keep it with your account. The hosts see your name and email with your line, and can hide it from the page; a hidden line stays with your rating, seen only by you and the hosts, until you change or remove it or your account is deleted. You can change or remove your rating yourself at any time; your account lists the evenings you rated, with your stars and your line, for you only. You can also make an image of your own rating to share where you like: we draw it from your stars, your line and your first name when you ask, send it only to you, and don’t keep it; where it goes from there is up to you. If a line names you, or shouldn’t be there, write to hello@afig.nl, whether you have an account or not, and the hosts take it down.

Your watchlist

The films on your watchlist are kept with your account, with when you added each one, so the site can show you when they play. Only you see it; the hosts don’t. The site’s admins see only how many members want a film, on watchlists or recommended, once two or more do, never who. If you import your IMDb watchlist, we read from the file you pick each film’s IMDb id, title and year, and the date you added it; your list keeps the films and those dates, and the rest of the file is discarded. If you import your Letterboxd watchlist, your browser opens Letterboxd’s export and sends us only its watchlist, never your diary, ratings or reviews; we keep each film’s title, year, link on Letterboxd and the date you added it; a film from it that you take off here stays noted with that import until you import again or delete your account, so a new import knows it. We never connect to your IMDb or Letterboxd account. You can remove films yourself at any time. If you turn on the emails when a film on your list starts playing, we keep that you did and when the last one went, and which films we told you of, with when, for 60 days, so each is told once; they go through Brevo and name the films as the cinemas bill them. Turning them off, on your watchlist or with the one-click link in each email, deletes your choice.

Signing up for an evening

If you say “I’m going” to an evening here, we keep that you did, with when, how many guests you bring if you bring any (only the number: nothing about them), and the line for the host if you write one, with your account. The number going includes you and your guests; your name, your guests’ number and your line are seen only by the group’s hosts, so they know who to expect: on the evening’s page, in Upcoming and on their Going page until two days after the evening, and in the emails the evening’s hosts (or, when none is linked, the admins) get: a daily one, and a last list a few hours before it. If the evening’s hosts need to reach you about it, say for a seat or a ticket the group bought, an admin may give them your account’s email, for that only. Two days after the evening your line is deleted. We email you a reminder before the evening (on the day, or the evening before for one that starts before 13:00), and if the evening is cancelled or moves; these emails come from evenings@afig.nl through Brevo. The evenings you went to stay onyour account page until you remove them; saying you can’t make it takes you off the list, and once an evening has passed we delete the sign-ups that didn’t go. Meetup knows nothing of it: an RSVP on Meetup is separate.

On the day, at the cinema: one of the evening’s hosts may post where the group is on the evening’s page, with a photo of the spot or of themselves if they add one. Those going see it there, and on their phone if they turned on the notifications for their evenings, until an hour after the film starts; the hosts see it too. If you’re going, you can tap “I’m here” at the cinema, with where you are if you say: the hosts see it beside your name in their list, and the evening’s hosts on their phone. Both are deleted three hours after the meetup time.

The newsletter

If you subscribe to the newsletter, with or without an account, we keep your email address, when you asked and when you confirmed it, and which issue you last got. Before the form sends, Cloudflare Turnstile checks in your browser that you’re not a robot, as for sign-in codes. Nothing goes out until you confirm by the link we email you. A member who signed in can subscribe their account’s own address in one tap instead: that address was confirmed when they signed in, so there is no robot check and no link, and the tap is the consent. Opened in your own browser, the link confirms at once; to tell you from the programs some mail services use to open links by themselves, it looks at your browser’s name and network as it opens, keeps neither, and otherwise asks you to press Confirm. An address not confirmed is deleted after 48 hours. The newsletter isn’t part of an account: deleting your account doesn’t end it, and leaving it doesn’t touch your account. Every issue has a link to leave, and a member whose account has the same address can leave from the account page or the newsletter’s page too; leaving deletes your address at once. The emails go through Brevo, an email service in the EU. Brevo counts how many people open each email and which links are clicked, without knowing who; we don’t look at either, and Brevo keeps these counts under its own retention rules. Your address is never sold or shared. An offer for members in an issue, such as a discount on a concert, comes with a code for everyone: whoever makes it learns nothing about you from us, and only knows you if you book with them.

Why we may keep it

Signing in is your request to use the parts of the site for members, and we keep only what that needs (GDPR Art. 6(1)(b)). The newsletter goes only to those who asked for it and confirmed: your consent, which you withdraw by leaving (Art. 6(1)(a)). The technical logs, the robot check before a code or the newsletter, the pictures loaded from Meetup and TMDB, the anonymous counting of visits and of what’s used, the admins’ counts of the films members want, the hosts keeping lines that shouldn’t be public off the site, the list of hosts’ sign-in emails, each event’s hosts’ Meetup member numbers and their emails about who signed up, the hosts’ shortlist, a host’s first name under the newsletter’s note, and showing the hosts’ descriptions of their events, serve our legitimate interest in a site that works, stays safe, shows the films and events, and helps the group (Art. 6(1)(f)).

Where it is, and for how long

  • Your account and what you send are stored in a Cloudflare database in the EU. Cloudflare handles them only for us, under its data processing agreement, and so does Brevo for every email the site sends: sign-in codes, the newsletter, the emails about evenings you signed up for and the hosts’ emails about them, and the watchlist’s. Cloudflare and Google are US companies certified under the EU-US Data Privacy Framework, which covers your data where it reaches the US. Meetup’s and TMDB’s image servers, also in the US, get your IP address straight from your browser, under their own privacy policies. If you turn on the app’s notifications, each one goes through your phone maker’s push service (Apple, Google, Mozilla or Microsoft, outside the EU), encrypted so that it can’t read it.
  • Your account stays until you delete it on your account page or ask us to, or until it hasn’t been used for 24 months; then it is deleted with everything you sent. You can withdraw a recommendation, remove a rating, take a film off your watchlist, or remove an evening you signed up for, yourself at any time.
  • Something deleted stays up to 30 days in the database’s own history, which lets us repair it after a mistake, and then it is gone. Errors are noted in the technical logs without what you sent in a form; the logs, which also hold each request’s address, are deleted after 7 days.
  • A host’s sign-in email stays on the hosts’ list while they host, and their link to Meetup until they unlink it; each event’s hosts’ Meetup member numbers until the evening starts; the record of the hosts’ daily emails about sign-ups is deleted after a month. Brevo keeps its record of each email it sends (the address, the subject, whether it arrived, and a copy of the email) for 30 days, then deletes it, and counts how many of the site’s emails are opened and which links in them are followed, without knowing who; we don’t look at either. Past events stay in the archive with their hosts’ descriptions; a host can ask us to take a description down.
  • Emails you send to hello@afig.nl are kept in the group’s mailbox on afig.nl, with Google Workspace, for as long as it takes to deal with them.

Your rights

You can ask to see what we keep about you, to correct it, to have it deleted, to receive it in a file, to limit how we use it, or to object to how we use it. To make sure it’s you, we answer at the address of your account. Write to hello@afig.nl, or message the hosts on Meetup; we answer within a month. If you think we handle your data wrongly, you can also complain to the Dutch data protection authority, the Autoriteit Persoonsgegevens.

You don’t have to give us anything: the site is open to read without it, and without an email address you just can’t sign in or get the newsletter. We make no decisions about you by automated means, and no profiling. Signing in is for people aged 16 or over.