Skip to content

Last updated · 12 November 2026

Cookie policy

This policy explains which cookies and similar browser storage inburgeringprep.com uses, why, and how you control them. It is published to satisfy Article 11.7a of the Dutch Telecommunicatiewet and the ePrivacy directive, and to support the consent requirements of the GDPR.

See also our Privacy policy and Terms of service.

What are cookies?

Cookies are small text files placed on your device by the websites you visit. We also use related browser-storage technologies such as localStorage; in this policy we treat them as cookies for clarity, since the consent rules are the same.

We group cookies in four categories. Strictly-necessary cookies are required for the Service to work and don't need consent. Functional, analytics and marketing cookies are only set if you consent.

Strictly-necessary cookies

Always on. Without these, you can't sign in or use the app.

ip_session
Keeps you signed in. Without this you would have to log in on every page.
Session: deleted when you close the browser
First-party
ip_csrf
Anti-CSRF token used to verify form submissions come from your browser.
Session
First-party
cookie-consent:v2 (localStorage)
Stores your cookie preferences (functional, analytics, marketing) separately so we respect your choices and don't ask you on every visit.
12 months, then re-asked
First-party

Functional cookies

Improve usability: remembering preferences, language, etc.

ip_pref
Remembers UI preferences such as collapsed sidebars and last-opened lesson.
12 months
First-party
ip_locale
Stores the interface language you chose.
12 months
First-party

Analytics cookies

Google Analytics 4, PostHog (usage stats, click heatmaps and anonymised session recordings) and our own first-party metrics, used to see how the site is used and where it fails. Analytics cookies are set only after you accept Analytics.

ip_visitor
Anonymised, salted visitor identifier used to count unique visits and measure feature adoption. Never shared with advertisers.
30 days
First-party
attribution:v1 (localStorage)
Records which channel you arrived through (campaign tags or UTMs, the referring site, and the page you landed on) so a sign-up can be counted against the right channel. Under Analytics alone no advertising identifier is kept: an ad click ID in the link is used to tell that the visit was a paid one and is then discarded.
90 days
First-party
_ga
Set by Google Analytics 4 to tell browsers apart, so visits and feature use can be counted over time. Set only after you accept Analytics.
2 years
Third-party (Google)
_ga_SN6W5YF5T6
Set by Google Analytics 4 to keep track of your current visit (session) for the same counts. Set only after you accept Analytics.
2 years
Third-party (Google)
ph_phc_AgfQU2qgP8fJyERgAduSwbNzjtH8ACMLrP6MNLmXsAdG_posthog (cookie + localStorage)
Set by PostHog through our own domain (inburgeringprep.com), as a cookie and in localStorage, to tell browsers apart and keep a visit together, so we can count visits, see where people click (heatmaps) and replay a sample of visits as anonymised session recordings. Typed text, your answers and your name or email are masked, and sign-in, account, checkout and admin pages are never recorded. Stored in PostHog's EU region (Frankfurt). Set only after you accept Analytics and deleted when you withdraw it.
12 months, or until you withdraw Analytics
First-party (PostHog)
ip_aid
Random identifier, not linked to your name or account, that keeps you in the same variant of an A/B test of our page text across visits, so the results can be compared. Set only after you accept Analytics and deleted when you withdraw it.
12 months, or until you withdraw Analytics
First-party
ip_analytics
Copy of your Analytics choice, readable by our server, so the page it sends already shows the right A/B test variant. Set only after you accept Analytics and deleted when you withdraw it.
12 months, or until you withdraw Analytics
First-party

Marketing cookies

Used only after consent, for measuring paid-campaign performance with the Google Ads, Meta and Reddit tags.

attribution:v1 (localStorage)
With Marketing accepted, the same record additionally keeps the raw ad click ID (Google, Meta, Reddit, Microsoft, TikTok), which lets a later purchase be reported back to the advertising platform that produced the click. Written only to your own account.
90 days
First-party
g_click_id, rdt_cid, msclkid, _fbc (localStorage)
Our own copies of the ad click identifier in the link you arrived through (Google, Reddit, Microsoft or Meta), so a purchase made a few pages later can still be reported to the platform that produced the click. Written only after you accept Marketing.
Until you clear site data or withdraw Marketing
First-party
_gcl_au
Set by the Google Ads tag to link a sign-up or purchase to the Google ad that led to it. Set only after you accept Marketing.
90 days
Third-party (Google)
_gcl_aw
Stores the click identifier from a Google ad link (gclid) so the resulting sign-up or purchase can be reported back to Google Ads. Set only after you accept Marketing.
90 days
Third-party (Google)
_fbp
Set by the Meta pixel to recognise your browser across visits, so a sign-up or purchase can be attributed to the Meta ad you clicked. Loads only after you accept Marketing.
90 days
Third-party (Meta)
_fbc
Stores the click identifier from a Meta ad link (fbclid) so the resulting sign-up or purchase can be reported back to Meta. Loads only after you accept Marketing.
90 days
Third-party (Meta)
_rdt_uuid
Set by the Reddit pixel to recognise your browser across visits, so a sign-up or purchase can be attributed to the Reddit ad you clicked. Loads only after you accept Marketing.
90 days
Third-party (Reddit)

Consent tracking

When you provide consent for optional cookie categories, we record:

  • Your specific choices for each category (functional, analytics, marketing)
  • The timestamp when consent was given
  • Your IP address at the time of consent (for legal compliance)

If you have an account, your preferences are also synced to your profile so they persist across devices. You can withdraw consent at any time without affecting the lawfulness of processing based on consent before withdrawal.

Managing your preferences

On your first visit we show a banner asking which categories you accept. You can change your mind any time:

  • Use the link in the page footer.
  • From your Account → Privacy Settings (for logged-in users).
  • Or clear your browser's site data for inburgeringprep.com. The banner will reappear on the next visit.
  • Browser-level cookie controls in Chrome, Firefox, Safari and Edge also work; check your browser's help for details.

Disabling strictly-necessary cookies will break the Service. The other categories can be turned off at any time without losing your Account.

Third parties

These providers set cookies or receive data from your browser on inburgeringprep.com:

  • Google (Google Analytics 4 and Google Ads). Google's tag loads on every page in Consent Mode, with all storage denied by default: until you accept, it sets no cookies and sends Google only cookieless signals. Accepting Analytics lets it set the _ga cookies; accepting Marketing lets it set the _gcl cookies and use ad click data. If you arrived from a Google ad and have not accepted Marketing, the ad click identifier can be carried along in the page address instead of being stored. See Google's privacy policy.
  • PostHog (PostHog Inc., EU cloud in Frankfurt). Web analytics, click heatmaps and session recordings. Loads only after you accept Analytics, through our own domain, and stops and deletes its cookie and storage when you withdraw it. Recordings mask everything you type, your answers, AI feedback and your name or email, and sign-in, account, checkout and admin pages are never recorded. See PostHog's privacy policy.
  • Meta (Meta pixel). Loads only after you accept Marketing. See Meta's privacy policy.
  • Reddit (Reddit pixel). Loads only after you accept Marketing. See Reddit's privacy policy.
  • Microsoft Advertising (UET tag). Built in but currently switched off, so it loads nothing and sets no cookies. If we switch it on, it will load only after you accept Marketing, and its cookies will be listed here first. See Microsoft's privacy statement.
  • Stripe. Payment pages are processed by Stripe inside their own iframe, and Stripe sets its own cookies there for fraud prevention. See Stripe's cookie policy.

Updates

If we add or remove cookie categories, we'll bump the consent version and re-prompt you. Material changes will also be announced by email to active Accounts.

Questions? Email hello@inburgeringprep.com or open the cookie banner from the footer at any time.