Cookie Policy

Last updated: 6 September 2026

What are cookies?

Cookies are small text files stored in your browser when you visit a website. We also use similar technologies such as localStorage. These help us understand how visitors use our site so we can improve it.

Cookies we use

Service	Purpose	Type
PostHog	Tracks how visitors interact with our site — pageviews, feature usage, and error events. Also records anonymised session replays (all text and inputs are masked) to help us understand usability and improve the product. No data is sold to third parties.	Analytics Session replay
Google Ads (gtag.js)	Measures Google Ads campaign performance and conversions. We run Google Consent Mode v2 in Advanced mode: when you decline, the tag still loads but Google only receives cookieless pings so it can model anonymous conversion volume — no advertising identifiers are stored on your device.	Advertising
HubSpot	Records which marketing pages you visit and links them to any demo request you submit, so we can follow up with relevant context. Sets `hubspotutk`,`__hstc`, `__hssc` and `__hssrc`. The tracker is only loaded after you accept — decline and it is never placed on your device. Data is held in HubSpot's EU data region.	Analytics
Session (essential)	Keeps you logged in while using the platform. Required for the product to function.	Essential

Essential cookies cannot be declined as they are required for the platform to work. Analytics cookies are only set after you give consent.

Third-party services

PostHog is a product analytics and session replay platform. We use it to understand how users navigate the site and to record anonymised session replays for usability research. All text content and form inputs are masked in recordings — no personal or financial data is captured in replays. Data is processed in accordance with PostHog's Privacy Policy.

Google Ads (gtag.js) is used to measure how our paid Google Ads campaigns perform. Google Analytics 4 now runs on the same tag and under the same consent signals, measuring how our public marketing pages perform. It is loaded on those pages only — never on the application, onboarding, document-upload or verification flows.

HubSpot is our CRM. Its tracking code attributes marketing pageviews to the demo requests submitted through our contact form. Unlike the Google tag it is not loaded at all until you accept — decline, or leave the banner unanswered, and no HubSpot script or cookie reaches your browser. Like GA4 it runs on the public marketing pages only. Data is processed in HubSpot's EU data region, in accordance with HubSpot's Privacy Policy.

Google Consent Mode v2

We implement Google Consent Mode v2 in Advanced mode. Before you make a choice on the cookie banner — and any time you choose Decline — all four Google consent signals (ad_storage, ad_user_data, ad_personalization, analytics_storage) are set to denied, and we enable url_passthrough and ads_data_redaction so no advertising identifiers are written to your device.

In that denied state, the Google tag still loads, but the only thing Google receives is a small, cookieless beacon containing no personal identifiers. Google uses those beacons to model anonymous conversion volume — they are not joined to any individual profile. If you click Accept, the four signals flip to granted and normal cookie-based measurement resumes.

To change or revoke your decision later, use the Accept / Decline buttons below, or clear this site's storage in your browser to be shown the cookie banner again on your next visit.

Your choices

You can change your analytics preference at any time using the buttons below. Your current status: You have not yet made a choice.

Tip: you can also append ?show-cookie-banner=1 to any page URL to force the banner to re-appear — handy for testing Google Consent Mode in Tag Assistant.

Contact

Questions about this policy? Email us at hello@firstmilelabs.com.