What data we collect
Ad measurement (only with consent). If you accept in the cookie window, the page loads the Meta Pixel. It sets the _fbp and _fbc cookies (see “Cookies and browser storage”) and sends Meta three events: a page view, starting to fill in the form, and a sent request. Each event carries the page address (with its campaign tags), the previous page’s address, your IP address and browser details. The Pixel doesn’t send Meta your contact details. When you send a request, our server sends Meta the sent-request event (Conversions API): your email address and phone number in hashed form (one-way codes from which the original can’t be read back, but which Meta can compare with its own data to link the event to your Meta account if you have one), the _fbp and _fbc cookie ids, your IP address, browser details, the page address (without campaign tags), the event time and a random event number, so Meta doesn’t count the same request twice. Your name isn’t sent to Meta.
If you declined in the cookie window, the request form shows an optional box, unticked by default, with which you can allow data to be sent to Meta for advertising. If you tick it, our server sends Meta only the sent-request event for that request: your hashed email address and phone number, IP address, browser details, the page address (without campaign tags), the event time and an event number. No cookies are set and the Pixel isn’t loaded.
Either way, we don’t send Meta the content of your request (the car you want, budget, notes).
Website usage analytics (only with consent). If you accept in the cookie window, the page also loads PostHog. It records which pages you view, where you came from (campaign tags and the previous page’s address, without ad platforms’ click ids), what you click and how far you scroll, how fast the page loads, which device and browser you use, and your approximate location (country and city), which PostHog works out from your IP address; the IP address itself isn’t stored. It also makes recordings of page use: how the page changed on your screen, where you clicked and how you scrolled. In the recordings, everything typed into the form’s fields and the form’s summary is hidden, and the name, email, phone and notes fields aren’t recorded at all. On the calculator, PostHog also receives the car details you entered there, as part of the page address. For a sent request, PostHog receives only that it was sent and the same random event number as Meta, not the content of your request or your contact details. PostHog links page views only through a random id in your browser (see “Cookies and browser storage”); it doesn’t know your name or contact details.
Why, and on what basis
Ad measurement and targeting on Meta (only with consent). We measure whether our ads on Facebook and Instagram bring requests, and Meta uses these events to show our ads to people more likely to send one. Meta may also show our ads to you, and uses the data for its own purposes under its own terms. The basis is your consent (Article 6(1)(a)), which you give in the cookie window or with the separate box in the request form; it’s separate from the consent for your request, and you don’t need it to send a request. You can withdraw the cookie window consent at any time through the “Cookie settings” link in the footer; withdrawing doesn’t affect the lawfulness of processing before it. Consent given with the form’s box covers only that request: the event is sent to Meta when you send the request, and nothing more is sent on that basis. For data already sent to Meta, contact Meta. We keep your choice, the box’s state and the consent text’s version with your request, to be able to show which consent you gave (Article 6(1)(c) and Article 7(1)).
Website usage analytics (only with consent). We look at how visitors use the website: which pages and links bring requests, where people stop filling in the form, and whether the site works, so we can improve the site and the form. The basis is your consent (Article 6(1)(a)), which you give in the cookie window with the same “Accept” button as for ad measurement. You can withdraw it at any time through the “Cookie settings” link in the footer; PostHog is then stopped and its data in your browser deleted. Withdrawing doesn’t affect the lawfulness of processing before it.
How long we keep it
The _fbp and _fbc cookies: 90 days from your last visit. If you withdraw consent, they’re deleted from your browser at once.
Your choice in the cookie window, in your browser: acceptance 6 months, refusal 1 month; then we ask again. The consent record with your request (your choice, the box’s state and the consent text’s version): as long as the request (12 months).
Meta keeps the data sent to it under its own privacy policy (facebook.com/privacy/policy).
PostHog data: recordings of page use up to 30 days, other events (such as page views and clicks) up to 12 months; then PostHog deletes them. PostHog’s ids in your browser: while your consent lasts (6 months); if you withdraw it, they’re deleted at once.
Who receives your data
Meta Platforms Ireland Limited (Merrion Road, Dublin 4, D04 X2K5, Ireland), only with your consent: ad measurement and targeting. We and Meta are joint controllers for collecting the data and sending it to Meta (Article 26 GDPR); Meta alone is responsible for what it does with the data afterwards. Under the arrangement, we’re responsible for informing you and having your consent. You can use your rights with us or with Meta. The essence of the arrangement: facebook.com/legal/controller_addendum; Meta’s privacy policy: facebook.com/privacy/policy.
PostHog, Inc. (USA), only with your consent: website usage analytics. The data is stored in PostHog’s EU cloud in Frankfurt (Germany). PostHog processes it on our behalf and on our instructions (processor, Article 28 GDPR).
Transfers outside the European Economic Area
Cloudflare and Resend are US companies, and Google’s parent company is in the US, so data may be transferred to the US. All three participate in the EU–U.S. Data Privacy Framework, which the European Commission has found to give adequate protection. Our agreements with Cloudflare and Resend also include the European Commission’s standard contractual clauses. For Gmail, Google transfers data under its own terms. Meta’s parent company, Meta Platforms, Inc., which also owns WhatsApp, is in the US and also participates in the EU–U.S. Data Privacy Framework; Meta and WhatsApp transfer data under their own terms. PostHog stores the data in the EU, but it is a US company and its staff may also access the data from the US.
Cookies and browser storage
Without your consent, the website sets no cookies and uses no tracking or analytics tools.
If you accept in the cookie window, the page loads the Meta Pixel. It sets the _fbp cookie (an id for your browser) and the _fbc cookie (the click id of a Meta ad; only if you came from one) on our domain. Both last 90 days from your last visit. Meta may also use its own cookies on its own domain; see Meta’s cookie policy for those.
If you accept, the page also loads PostHog. PostHog sets no cookies: it keeps a random visitor id and session id and its own settings in your browser (localStorage and sessionStorage), under names starting with “ph_”, to link one visitor’s page views. They’re kept while your consent lasts; if you withdraw it, they’re deleted at once.
Your browser remembers your choice (localStorage): acceptance for 6 months and refusal for 1 month, so the window doesn’t reappear on every visit. You can change it at any time through the “Cookie settings” link in the footer. If you withdraw consent, the Pixel and PostHog are stopped and the _fbp and _fbc cookies and PostHog’s data are deleted from your browser at once; we can’t delete Meta’s own cookies or data already sent to Meta, so contact Meta about those. Without JavaScript there’s no window, no Pixel and no PostHog.