Skip to content

Privacy

Click here for our Privacy and Cookie Statement

This is a translation. The Dutch text is binding. Dutch version: /privacy

Who processes your data

S.I.S.E. B.V., trading under the name Ik Stop Ermee, is the controller for the data that you share with us via ikstopermee.nl and the associated course environment, except for the data that you leave when you make a gift.

Address of main office: Van Musschenbroekstraat 87, 3514 XJ Utrecht
KvK number: 72709820, registered office in Amsterdam
Contact address for privacy questions: info@ikstopermee.nl

Hugo Hairwassers is the point of contact for privacy questions within S.I.S.E. B.V., reachable at info@ikstopermee.nl.

There are two organisations. S.I.S.E. B.V., KvK 72709820, provides the courses and this website. Stichting Ik Stop Ermee, RSIN 857960258, has ANBI status and receives the gifts. If you make a gift, the Foundation is the beneficiary in name and in deed.

For the data that you leave when you make a gift, Stichting Ik Stop Ermee is the controller.

Which data and why

We process the following data, depending on what you do with us:

  • Your name, to address you personally and to put on a certificate or invoice.
  • Your e-mail address, to manage your account, to give you access to the course and to send you practical e-mails about your registration.
  • Your telephone number, if you leave it, so that we can reach you with questions about your registration.
  • Your place of residence, as part of your profile or of a physical meeting that you register for.
  • The name of your company, if you register via an employer or organisation.
  • Your language preference, to offer the course and the communication in the right language.
  • Data about your registration and the meeting or course that you follow, to give you access and to keep track of your progress.
  • Payment and order data, to process your payment and to meet our administrative obligations.
  • Chat messages that you send to a coach, to be able to support you during the course.
  • Your video progress, so that you can resume the course where you left off.
  • A technical security value when requesting discount codes: an encrypted representation of your IP address, not the IP address itself. We use this only to prevent misuse of the request form.
  • The data that you fill in when you request a discount code: the name of your organisation, the department and the location, the postal address and the postcode, your first and last name, your e-mail address and your telephone number. We need them to assess whether your organisation qualifies for a discount.

If you make a gift, we process your e-mail address, and your name, organisation and message if you fill those in yourself. You can also give anonymously: then name and organisation remain empty. We do need your e-mail address, because that is where we send the confirmation of your gift.

If you are a partner

We work with partners who bring our course to the attention of others. If you sign up as a partner, we process your name, your company name, your address, postcode, town or city and country, your telephone number, your e-mail address, how you want to bring us to the attention of others and the comments that you fill in yourself.

If we approve your application, we also process your KvK number, your VAT number and your IBAN. We need these to be able to calculate, invoice and pay out your fee. With every payout we record the amount, the VAT, the invoice number and the payment date.

We use this data to carry out the cooperation and to meet our administrative and tax obligations. We do not share it with other partners.

If you ask for deletion, we delete everything we have of you: your data, your clicks and every fee that is still outstanding. That fee lapses and we no longer pay it out. What we have already paid out to you remains in our accounts for seven years, because the tax law prescribes this. Your discount code does remain in existence and keeps working. That code appears on the orders that customers have already placed with it, and those must remain in our accounts for seven years; after that, the code no longer shows whose it was. This cannot be undone.

If you arrive via a partner link

If you come to our site via the link of a partner, we place a cookie in your browser with a random identifier in it. At the same time we record which partner it was and at what moment you clicked. This allows us, if you book a course within thirty days, to attribute that booking to that partner and to pay out their fee. That same identifier ensures that you receive the customer discount that is attached to that partner.

That identifier contains no name, no e-mail address and no IP address: it is a random number that belongs only to your own browser. The cookie is called ise_partner and is listed further on in the cookie policy, with its retention period. This cookie is not strictly necessary for the operation of the site; see there what that means.

On what legal basis

We process your data because that is necessary to carry out the agreement with you, such as your registration and the access to the course. For payment and invoice data we have a legal obligation. For the technical security value with discount codes we have a legitimate interest: preventing misuse.

To process your gift and to send you a confirmation of it (performance of agreement).

For the data of a partner and of a request for a discount code, performance of the agreement applies, and for the KvK number, the VAT number, the IBAN and the payouts our legal administrative obligation applies in addition.

For the cookie that attributes a booking to a partner, we need your consent, because this cookie is not needed to make the site work. We therefore ask for your consent at the moment you arrive via the link of a partner. You then first get a screen that says which partner it concerns and what the cookie does. The cookie is only placed once you say yes. If you say no, we place nothing and you can simply view and book the course; only the discount of that partner then lapses.

How long we keep it

Invoices carry 21 percent VAT. Everything that is attached to a payment or invoice, we keep for seven years. This is the statutory tax retention period.

Data of a gift: also 7 years, because a gift is attached to a payment.

All other data, such as your profile, registration, chat messages and video progress, we keep for two years after the reason for the processing has lapsed, for example after your access to a course has expired.

The data of a request for a discount code we keep for two years, counted from the moment we handled the request, or from the request itself if we have not handled it yet. Technical log lines about a change in our system we also keep for two years, counted from the moment of that change.

An e-mail that we send without it being linked to an account, such as a confirmation to someone who makes a gift without otherwise becoming a customer, we keep for two years from the moment we send it. If an e-mail is linked to an account, we keep it for as long as the account itself exists.

Data of a partner that is attached to a fee or a payout, such as the KvK number, the VAT number, the IBAN and the amounts, we keep for seven years. That is the same tax retention period as with an invoice.

The identifier of a click on a partner link we keep for two years. The cookie in your own browser lapses earlier, after thirty days; it is listed further on in the cookie policy.

With whom we share it

We share data only with parties that help us to provide the service:

  • Our website runs at Vercel. Every visit to every page goes through that platform, even if you never fill in a form. They receive your IP address, your browser data and the address of the page that you request. We have a data processing agreement with Vercel on European terms.
  • Our database and login environment run at Supabase. All your data from this statement is stored here.
  • Our course videos are played via Cloudflare Stream. They receive your playback request as soon as you start a video.
  • Cloudflare Turnstile checks with certain forms whether you are a human and not an automated system. Technical characteristics of your browser and request are processed in the process.
  • Our e-mails, such as confirmations and account e-mails, are sent via Mailgun. They receive your e-mail address and the content of the e-mail.
  • We measure website visits with Umami, without any cookies being placed.
  • Payments go through Stripe. They receive your payment and order data to process the transaction.

The headings and the text on this site use fonts that the site supplies itself. Your browser fetches those fonts from the same server as the page itself, and so not from another company. No IP address goes to a font service for this and no cookies come from a font service.

We never sell your data to third parties.

Where it is stored

Our website runs at Vercel. Our database is at Supabase. Our course videos are at Cloudflare. Our e-mail is sent via Mailgun. These parties may process data outside the Netherlands; we make sure that they comply with the European privacy rules in doing so.

Cookies and measuring

We measure visits to our website with Umami. Umami places no cookies in doing so.

For the operation of the site we do store data in your browser that is needed to stay logged in and to remember your choice about measuring. This happens from three components of the site: the measuring component, the navigation component and the logout page.

We place two cookies of our own: ise_partner and ise_bedank. The cookie ise_partner is only placed if you arrive via the link of a partner, and it serves to attribute a booking to that partner. The cookie ise_bedank is only placed when you start the payment, and it serves to log you in after the payment. On all other pages we place no cookie. The details are further down on this page, in the cookie policy.

On 4 September 2026 it was measured in a real browser what is actually set, on all public pages of the site in both languages: 121 measurements. This yielded one cookie, that of the partner link, and otherwise only browser storage.

Your rights

You have the right of access to your data, the right to have incorrect data corrected, the right to have your data deleted, the right to have the processing of your data restricted, the right to object to the processing, and the right to receive your data in a portable form.

For all these requests you can get in touch via the contact address at the top of this statement.

Security

We take appropriate technical and organisational measures to protect your data against loss or unlawful use. Access to our systems is limited to what is necessary to provide the service.

Complaints

Do you have a complaint about how we handle your data? Then please first contact us via the contact address at the top of this statement. If you cannot reach a solution with us, you have the right to lodge a complaint with the Autoriteit Persoonsgegevens (the Dutch Data Protection Authority).

Changes

We may amend this privacy statement, for example if we start using a new service or if the regulations change. The date of the last change is at the bottom of this page.

Cookie policy

This is the cookie policy of S.I.S.E. B.V. The table was re-measured on 4 September 2026 in a real browser, on all public pages of the site: 32 Dutch pages, the same 32 in English, the same 32 once more with consent for measuring, the page of a blog and of a news item, the partner link, an unknown address and the course environment after logging in. In total 121 measurements. The video was measured separately on 26 August 2026, with a video that was actually playing.

What cookies are

A cookie is a small file that a website places in your browser. Besides cookies, a website can also store data via browser storage, such as localStorage. That works differently from a cookie: it does not automatically go along with every request to our server, but stays in your browser until the website removes it itself or you delete it yourself.

Which ones we use

We use two cookies of our own: ise_partner is only placed if you arrive via the link of a partner, and ise_bedank only when you start the payment. In addition we use browser storage, for the operation of the site:

name or typewhere it comes fromwhat it is forhow long it stayscookie or browser storage
ise_partnerOur own, set by the partner link, and only after you have said yes on the consent screenAttributes a booking to the partner via whose link you arrived, so that we can pay that partner their fee and you get the customer discount that is attached to that partner. It contains a random number, no name, no e-mail address and no IP address. This cookie is NOT strictly necessary for the operation of the site; we ask your consent for it separately on the screen that you see when you arrive via a partner link, and it is only placed after your yes.30 days. Measured on 4 September 2026: it is only placed on the partner link and is then 36 characters long, with httpOnly on, secure on and sameSite Lax, valid for the whole site.cookie
ise_bedankOur own, set at the moment you start the paymentKeeps track of which browser has just paid, so that only that one is logged in after the payment. It contains a random number, no name, no e-mail address and no IP address. This cookie is strictly necessary for logging in after the payment.30 minutes. The cookie is erased as soon as it has been used. It is httpOnly, secure and sameSite Lax, and applies only to the address /betaling-gelukt.cookie
ise-metenThe measuring component of the siteRemembers whether you have given consent for the measuring of your visitStays until you empty the storage of your browser. Browser storage has no expiry date and we nowhere remove this key. Measured on 4 September 2026: it is only placed after your choice, then appears on all pages of the site and is 2 characters long.browser storage (localStorage)
sb-*-auth-tokenSet by the Supabase client itself; removed when you log outKeeps you logged in so that you do not have to log in again each timeStays until you log out or empty the storage of your browser. Measured on 4 September 2026: it is placed when you log in, is then well over 2000 characters long, and is gone after logging out.browser storage (localStorage)
sb-*-auth-token-code-verifierSet by the Supabase client itself, as soon as you ask for a login link, ask for a new password, log in with Google or register on the siteTemporary verification code that completes the login when you return to this browser. It contains a random code, no name and no e-mail address.Stays until you complete the login, log out or empty the storage of your browser. Measured on 11 October 2026: it is gone after logging out.browser storage (localStorage)
sb-*-auth-token-flow-*-code-verifierSet by the Supabase client itself, as soon as you ask for a login link, ask for a new password, log in with Google or register on the siteTemporary verification code that completes the login when you return to this browser, one per request. It contains a random code, no name and no e-mail address. With more than five open requests the oldest one is removed.Removed at the latest when you log out or empty the storage of your browser. Measured on 11 October 2026: it is gone after logging out.browser storage (localStorage)
sb-*-auth-token-flows-code-verifierSet by the Supabase client itself, as soon as you ask for a login link, ask for a new password, log in with Google or register on the siteList of the requests that are still open in this browser. It contains only random codes, no name and no e-mail address.Removed at the latest when you log out or empty the storage of your browser. Measured on 11 October 2026: it is gone after logging out.browser storage (localStorage)
ise-beheer-*-sessieSet by the Supabase client of the admin area; removed when you log out of the admin areaKeeps you logged in to the admin area, separately from the login on the site. Only used when you log in to the admin area.Stays until you log out of the admin area or empty the storage of your browser. Measured on 11 October 2026: it appears when you log in to the admin area and is gone after logging out of the admin area.browser storage (localStorage)
ise-beheer-*-sessie-code-verifierSet by the Supabase client of the admin area, as soon as you ask for a login link in the admin areaTemporary verification code that completes the login to the admin area when you return to this browser. It contains a random code, no name and no e-mail address.Stays until you complete the login, log out of the admin area or empty the storage of your browser. Measured on 11 October 2026: it is gone after logging out of the admin area.browser storage (localStorage)
ise-beheer-*-sessie-flow-*-code-verifierSet by the Supabase client of the admin area, as soon as you ask for a login link in the admin areaTemporary verification code that completes the login to the admin area when you return to this browser, one per request. It contains a random code, no name and no e-mail address. With more than five open requests the oldest one is removed.Removed at the latest when you log out of the admin area or empty the storage of your browser. Measured on 11 October 2026: it is gone after logging out of the admin area.browser storage (localStorage)
ise-beheer-*-sessie-flows-code-verifierSet by the Supabase client of the admin area, as soon as you ask for a login link in the admin areaList of the requests in the admin area that are still open in this browser. It contains only random codes, no name and no e-mail address.Removed at the latest when you log out of the admin area or empty the storage of your browser. Measured on 11 October 2026: it is gone after logging out of the admin area.browser storage (localStorage)
ise-rol-*The navigation component of the site, the Beheer (admin) button and the Partner link in the headerRemembers for the duration of your visit whether your account is an administrator or a partner, so that the header does not have to ask the database for the Beheer button or the Partner link on every page. The number in the name is the number of your account. It contains only the word beheerder (administrator), partner or geen (none). This key is only set if you are logged in.Stays until you close the tab or the browser.browser storage (sessionStorage)
Cloudflare TurnstileExternal script from Cloudflare, used on the contact form, the gift form, the sign-up form for partners, the form for a request code and the registration form for the courseChecks whether you are a human and not an automated systemStays until you empty the storage of your browser. Browser storage has no expiry date. Measured on 4 September 2026: it is only placed when you touch a field in the form, only on those five forms and their English counterparts, and is then 149 characters long.Browser storage (localStorage), the key cf.turnstile.u on the domain challenges.cloudflare.com of Cloudflare. Measured on 4 September 2026: no cookie.
Cloudflare StreamExternal script from Cloudflare, used when playing course videosMakes the video player work and makes playback go wellNothing stays. Measured on 26 August 2026 with a video that was actually playing.Neither of the two. Measured on 26 August 2026 with a video that was actually playing: no cookie and no browser storage.

What we do NOT use

We place no advertising cookies. We place no cookies of third parties: the only cookies on this site are ise_partner and ise_bedank, and those are our own. We do not follow you with them across other websites, and we pass their content on to no one. We measure your visit to our website with Umami, and that happens without cookies.

How you refuse or delete them

For measuring your visit, the website asks you for consent before anything is measured. If you choose no, nothing is measured.

The cookie ise_partner is only placed if you arrive via the link of a partner. If you arrive directly, it is never placed. If you already have it, you can remove it via the settings of your browser; you will then miss the customer discount that is attached to that partner.

The other browser storage is needed to stay logged in. If you want to delete that, you can log out, or empty the storage of your browser for our website via the settings of your browser. After that you have to log in again.

Changes

We may amend this cookie policy, for example if we start using a new service or if the regulations change. The date of the last change is at the bottom of this page. If you have questions about this policy, please get in touch via info@ikstopermee.nl.

Last changed: 4 September 2026.