Last updated: 22 August 2026
Your choices
When Meta measurement is configured, the site asks you to allow or reject advertising technologies. Rejecting is as easy as accepting, does not prevent you using the website, and does not change your eligibility for a free website.
Necessary storage
Consent choice: local storage remembers whether you allowed or rejected advertising measurement, along with the wording version and expiry. The choice expires after six months, or sooner if the wording changes.
Form protection: the server processes short-lived technical identifiers for rate limiting and spam prevention. Persistent rate-limit keys are one-way hashed.
Optional Meta advertising technologies
Application attribution: after advertising consent, session storage may retain referrer and UTM campaign values during the current browser session so campaign information survives the application journey. It does not contain the submitted application.
After you select Allow advertising, the site loads Meta Pixel from connect.facebook.net. Meta may set first-party identifiers such as _fbp and, after an advert click, _fbc. These help Meta connect a website visit or application to an advert.
Reflow Digital also uses Meta Conversions API for consented application Leads. This is a server-to-server request rather than a browser cookie, but it follows the same advertising choice. Browser and server Lead events share one event ID so Meta can deduplicate them instead of counting one application twice.
Events we measure
- PageView: pages visited after advertising consent.
- ApplicationStarted: a custom funnel event after the first valid step is completed.
- Lead: sent only after a new application is successfully stored in Supabase. Failed or duplicate submissions do not create a Lead event.
We do not use GA4 at present and do not use advertising consent to subscribe applicants to marketing.
Change or withdraw your choice
Use the Cookie preferences control shown at the edge of the website after making a choice. Withdrawing stops future Pixel events, sends Meta's revoke command and removes accessible Reflow-domain Meta identifiers. You can also clear site data in your browser.
For more about personal information and the Conversions API payload, read the privacy policy. Meta explains its own use of cookies in the Meta Cookies Policy.