Privacy Policy

Who we are and how to reach us

1. This policy explains what we do with your personal data when you use flow, and what you can ask us to do about it.
2. erudeon v.o.f. decides why and how your personal data is used, and is the controller for it. Our details are below, and that address is also where you write to us about anything in this policy.
3. We have not appointed a data protection officer. We are not required to, and a request sent to the address below reaches the people who can act on it.
4. flow and pass the year share one account. Our pass the year pass the year Privacy Policy covers what happens on that side.

What personal data we collect

1. What you give us. Your name, your email address, a password or your Google sign-in, and whatever you put on your profile: a photograph, a university, a study program, the handles you choose to show.
2. What you do here. The events you host, reply to, save or turn up at; who you bring; the comments and reactions you leave; the photographs you put on an event's wall; who you are friends with, who you follow and who you have blocked.
3. What you tell a host. When you say you have arrived, or send a question or a call for help during an event, the host sees it and so does anyone they have made responsible for that night.
4. Where you are, if you ask us to follow it. Only a city, never a position, and only when you have turned it on. Clause 8 sets out exactly what that means.
5. What we record as you use it. Sign-in and access records, your IP address, your browser or device, and which pages you viewed.
6. What your device tells us for notifications. A push token, which identifies the device rather than you, so a notice you asked for can reach it.
7. We do not ask you for special categories of data, such as health, beliefs or who you are attracted to. Clause 9 explains the one feature that comes close and how it is built so that it does not become one.

Why we use it, and our legal basis

1. To give you an account and run flow. Creating and securing your account, showing you events, taking your replies, carrying your comments and letting you find people you know. Our basis is that we need this to perform our contract with you.
2. To let hosts run their events. Giving a host the list of who is coming, and carrying arrival and help messages to them. Our basis is performance of our contract with you and, for the host, our legitimate interest in an event that is actually run.
3. To keep flow safe. Acting on reports, checking accounts we have reason to doubt, and enforcing our Community Guidelines. Our basis is our legitimate interest in protecting the people here.
4. To send you service messages and notices you asked for. Sign-in links, changes to an event you replied to, and what a host announces. Our basis is performance of our contract with you.
5. Where we ask for your consent. Analytics and session replay, following the city you are in, and anything stored on your device beyond what is strictly necessary. You can withdraw any of these at any time, and withdrawing does not affect what we did before you did.
6. To meet a legal obligation, where one applies to us.

Who we share it with

1. We share your personal data with providers who process it on our instructions and for no purpose of their own, and only what they need. Those categories are: email delivery; product analytics, where you have consented; delivering push notifications to your device; and serving and protecting the site.
2. Ask us and we will name the company behind any of those categories, and tell you what it holds about you.
3. Signing in with Google is different. If you choose it, Google authenticates you on its own terms as its own controller rather than on our instructions, so it is not one of the providers above. You never have to use it.
4. Other members are not processors either, and this is the part worth reading. flow is social, so some of what you do is meant to be seen. What you post, the events you host and your profile are visible to the people flow shows them to. Whether another member can see that you are going somewhere is your own setting, and by default only people you are mutual friends with can.
5. A host sees their guest list. When you reply to an event, the person running it learns that you are coming, and so does anyone they have made responsible for it. That is the point of replying, and you cannot be on a guest list invisibly.
6. We also share personal data where the law requires it, and with our professional advisers where we need advice. We do not sell your personal data, and we do not share it for anyone's marketing.

Where your data goes

1. We keep your personal data in the European Union. Our database, our file storage and our video sit on servers we control in the EU.
2. Some of our providers are established outside the EU. Where personal data reaches one of them, the transfer relies on the Standard Contractual Clauses approved by the European Commission.
3. Ask us about a particular provider and we will tell you where it processes data and which safeguard the transfer relies on.

How long we keep it

1. We keep personal data for as long as we need it for the purpose we collected it for, and then delete or pseudonymize it.
2. An event is a shared record. Your reply is yours, and the guest list is the host's record of the night they ran, so deleting your account removes you from both rather than erasing the event.

Your rights

1. You may ask us for a copy of your personal data, to correct it, to delete it, to restrict what we do with it, to receive it in a portable form, and to object to processing we base on our legitimate interests.
2. Where we rely on your consent, you may withdraw it at any time, and it is as easy to withdraw as it was to give.
3. You can do the main two yourself, at any time, without asking us. The routes are below.
4. Deleting your account starts a 30 day period during which you can change your mind. After it we erase your data: your profile is stripped, your replies and photographs are deleted, your messages to hosts are detached from you, and records we have to keep no longer name you.
5. Erasure cannot reach what other people already saw or saved. A comment you wrote is deleted, but a screenshot somebody took of it is not ours to recall.
6. We answer within one month. Where a request is complex we may need longer, and we will tell you so within that first month.

The city you are in

1. flow can follow the city you are in, so that what you are shown is about where you actually are rather than where you signed up. It is off until you turn it on.
2. We keep a city, never a position. Your device's coordinates are rounded to a place before anything is stored, and the exact location is never kept, never logged and never sent to anyone.
3. It is never used to decide what you can do or what anything costs.
4. You can turn it off whenever you like. Once off, the city we hold is no longer read, and you can ask us to delete it.
5. Turning it off in flow does not withdraw the permission you gave your browser or your phone. Those are controlled where you granted them.

Crushes

1. Where a host turns crushes on for an event, a guest who opts in may privately mark another guest.
2. Nothing is revealed unless it is mutual. A mark is never shown to the person marked, is never counted for them, and never appears anywhere, unless they have marked you as well and you are both still opted in.
3. Because nothing is ever disclosed one way, the fact that you marked somebody does not reveal anything about you to them or to anyone else.
4. You can opt out at any time, which stops both sending and matching.
5. We built it this way deliberately. Who a person is attracted to is exactly the kind of thing the law protects most strongly, and the safest design is one where a one-sided signal never leaves the system.

Keeping your distance from somebody

1. You can block another member, which hides each of you from the other.
2. You can also privately mark somebody as a person you would rather not be near. That mark carries no text, is never shown to them, reaches nobody by itself and cannot be used to punish them. It exists so that flow can keep the two of you apart.
3. Neither of these is a report. If somebody has done something wrong, report them, and our Community Guidelines explains what happens next.

Photographs and other people

1. A photograph from an event usually shows people who did not post it.
2. Photographs you put on an event's wall are yours. Deleting your account deletes the pictures, not just your name against them.
3. If you appear in a photograph on flow and want it gone, tell us and we will remove it. You do not have to give a reason, and you do not need an account to ask.

Inviting people who are not on flow

1. When you invite somebody, we hold what is needed to deliver that invitation and to let them accept it.
2. Where you invite people from your phone's contacts, your address book is never sent to us or stored. Only the numbers needed to check who is already here leave your device, we never say which number matched, and the invitation itself is sent by you from your own phone.
3. An unaccepted invitation is cleared 30 days after it expires, and the invitee's name is removed from the link.

Cookies and similar technologies

1. Our Cookie Policy sets out what we store on your device, why, and the choices open to you.
2. Analytics and session replay run only if you agree. Before you answer, and after a refusal, nothing is stored on your device or read from it and you are not identified.

Children

1. You must be at least 16 to hold an account, which is the age from which a person may consent to the handling of their own personal data in the Netherlands.
2. We do not knowingly collect personal data from anyone younger. If you believe a member is under 16, tell us and we will look into it and close the account if it is so.

Changes to this policy

1. We update this policy when what we do with personal data changes.
2. The date at the top of this page is the date of the current version, and a change takes effect when it is published here. Where the law requires us to tell you about a change directly, we will.

Complaints

1. Tell us first. Write to the address above and we will look into it.
2. You may also complain to the Dutch data protection authority, the Autoriteit Persoonsgegevens, at autoriteitpersoonsgegevens.nl.
3. If you live in another EU country, you may complain to the supervisory authority there instead.