Cookie Policy
Last updated: 20 September 2026
This policy explains every cookie TradeLog NZ sets, why it exists, and how to change your mind. It sits alongside our Privacy Policy, which covers personal information more broadly under the Privacy Act 2020.
The short version: we set the cookies needed to sign you in and take payment, plus two optional analytics cookies and one optional advertising cookie (the Meta pixel). No data brokers, and your trade data is never used for any of this — the optional cookies see page addresses, nothing you enter into the app.
1. What cookies are
Cookies are small text files a site stores on your device. We also use closely related browser storage (local storage and session storage) for the same purposes; wherever this policy says “cookies” it covers those too.
2. Strictly necessary cookies
These make the service work. They cannot be switched off in the app, and they do not require your consent because the service you asked for is impossible without them. If you block them in your browser you will not be able to log in.
| Cookie | Set by | What it does | Lasts |
|---|---|---|---|
| sb-*-auth-token | Supabase | Keeps you signed in and authorises every request to your own data. Without it you cannot log in. | Session / until sign-out |
| tl_consent | TradeLog NZ | Remembers the cookie choice you made on this page so we stop asking. | 6 months |
| __cf_bm, cf_clearance | Cloudflare | Bot detection and abuse protection in front of the site. | 30 minutes – 1 year |
| __stripe_mid, __stripe_sid | Stripe | Payment fraud prevention on the checkout and billing pages. Set only for subscribers. | Session – 1 year |
3. Analytics cookies (optional)
These tell us which features are actually used and where people get stuck. Along with the marketing cookie below they are the only cookies you can turn off, and turning them off changes nothing about how the app works for you.
| Cookie | Set by | What it does | Lasts |
|---|---|---|---|
| ph_*_posthog | PostHog | Product analytics — which features get used, where people get stuck, and which errors occur. Used to improve the product, never sold. | 1 year |
| _ga, _ga_* | Google Analytics 4 | Aggregate traffic measurement — how people find the site and which pages they read. | 2 years |
Analytics data is aggregated and used only to improve TradeLog NZ. We do not sell it, and we never send your trades, expenses or tax figures to an analytics provider.
4. Advertising cookies (optional)
We run one: the Meta pixel, from Meta Platforms (Facebook and Instagram). It exists so we can tell whether the ads we pay for actually bring traders to the site, and so we can show those ads to people similar to the ones who already find TradeLog NZ useful. It is covered by the same consent choice as analytics — pick “Necessary only” and it never loads.
| Cookie | Set by | What it does | Lasts |
|---|---|---|---|
| _fbp | Meta (Facebook) | Meta pixel. Tells us whether someone who saw one of our ads on Facebook or Instagram went on to sign up, and lets us show our ads to similar people. Set only if you accept optional cookies. | 3 months |
What Meta receives is the page address you are on and a randomly generated browser identifier. It is never given your trades, expenses, tax figures, broker details or anything else you enter into the app, and we do not upload customer lists to Meta. Google Analytics remains configured with advertising storage, ad personalisation and ad user data permanently denied.
You can also limit what Meta does with this data from your own Facebook ad preferences, independently of the choice you make here.
5. How we ask for consent
The first time you visit, a banner asks how you want analytics handled. What happens by default depends on where you are:
- EEA, United Kingdom and Switzerland — analytics and advertising cookies are blocked until you choose “Accept all”. The Meta pixel is not even downloaded. Nothing is stored on your device before then, in line with GDPR and the ePrivacy Directive.
- New Zealand and everywhere else — analytics and the Meta pixel run from your first visit, and the banner tells you so and lets you opt out in one click. This is permitted under the Privacy Act 2020.
For Google Analytics we implement Google Consent Mode v2, so the consent state is applied before any measurement request is sent.
6. Changing your mind
Withdrawing consent is as easy as giving it. Use the button below, or the Cookie preferences link in the footer of any page, at any time.
You can also block or delete cookies in your browser settings. Be aware that blocking the strictly necessary cookies above will sign you out and prevent you signing back in.
7. Third parties named in this policy
- Supabase — authentication and database
- Stripe — payments and fraud prevention
- PostHog — product analytics
- Google Analytics — traffic measurement
- Meta Platforms — advertising measurement (Meta pixel)
- Cloudflare — security and bot protection
8. Changes to this policy
If we add or remove a cookie, this page is updated and the date at the top changes. Where a change materially affects your choices, we will ask for consent again.
9. Contact
Questions about cookies or anything else on this page: [email protected].