Cookie policy
Last updated 4 November 2026
Australia has no cookie-consent law, so we do not show a consent wall. We do show a notice when advertising cookies are in use, and we list everything here by name so you can decide for yourself.
Set by us
| Name | Type | Purpose | Lifetime |
|---|---|---|---|
ddr-notice | localStorage | Remembers that you dismissed the cookie notice | Until you clear site data |
That is the only thing the site itself stores in your browser. There are no login cookies because there are no accounts.
Set by Meta (only when the Pixel is enabled)
| Name | Set by | Purpose | Lifetime |
|---|---|---|---|
_fbp | facebook.com via the Pixel script | Identifies your browser so Meta can attribute a purchase to an ad you saw | 90 days |
_fbc | same | Stores the click identifier from a Meta ad you clicked | 90 days |
Events the Pixel sends to Meta from your browser: page view, viewing a kit, clicking buy, submitting the plan form, and purchase (on our thank-you page after Stripe's checkout).
When the Pixel is on, our server also reports each purchase to Meta directly (Meta's Conversions API), so a sale is counted once even if the browser event is blocked. It sends the purchase value, which kit was bought, the order's checkout id (the same id the browser event uses, so Meta keeps only one of the two), and a one-way hashed (SHA-256) copy of the buyer's email address and phone number. Meta matches those hashes against its own users' hashed details to tell us which ads led to sales; we send them for ad measurement only. We never send Meta your name, delivery address or card details.
Set by Stripe
Checkout happens on buy.stripe.com, which sets its own cookies for fraud prevention and session handling. See Stripe's cookie policy at stripe.com/cookies-policy/legal.
Opting out
- Block the Pixel with any content blocker, or Firefox's or Safari's built-in tracking protection; the site works identically without it.
- A content blocker does not stop the server-side purchase report described above, because it is sent from our server, not your browser. It is sent only while the Pixel is switched on for the site, and how Meta uses it follows your Meta ad settings.
- Adjust Meta ad settings at facebook.com/adpreferences.
- Clear
ddr-noticeby clearing site data; the notice will simply show again.
What we deliberately do not use
No Google Analytics, no Google Tag Manager, no session recording, no heat maps, no chat widgets, no third-party fonts, no A/B testing scripts. Our ad measurement is the Pixel plus Stripe's own reports.