Cookies are small text files stored on your device. We also use browser storage and similar technologies. This policy explains what they do and how you can choose which optional uses to allow.
These make the site work and cannot be switched off: they keep your lookup and checkout session together, remember your currency choice, and keep you signed in if you have an account. They contain no advertising identifiers.
Stripe and Onelink may set cookies during checkout for fraud prevention and secure payment processing. These are governed by their respective privacy policies.
We use Google Analytics to understand which pages and tools are useful, where site journeys need improvement and whether our own advertising leads to visits and purchases. For visitors in the UK, European Economic Area and Switzerland, analytics remains off unless they accept it. In other countries, analytics is enabled by default and can be declined or switched off at any time through Cookie settings. If we cannot reliably determine the country for the request, analytics remains off unless the visitor accepts it.
Our hosting provider supplies an approximate country for the current request so the site can select the appropriate setting. Buildsheet Pro receives only the resulting analytics setting and does not add the country to its consent counts. When analytics is enabled, we send only the page path and recognised campaign parameters on public landing pages, such as a Google click identifier or UTM campaign tag, so visits and purchases can be attributed. Private order references, customer or vehicle data and all other query parameters are excluded. Google advertising storage, advertising user data and ad personalisation remain disabled.
When you make an explicit analytics choice, we add one to a daily aggregate count for the choice, broad page group, desktop or mobile layout, and whether the choice was made in the banner or settings. These counts contain no email, vehicle or order information, no country, no full URL and no visitor identifier. They are retained for 14 months so we can improve the consent experience.
When this feature is available, the Advertising (Meta) choice allows the Meta Pixel to measure public page visits and product views, and our server to share checkout starts and eligible confirmed purchases to measure and improve our Facebook and Instagram ads. When you have no saved choice, Advertising (Meta) starts selected in Settings. Tracking stays off until you choose Accept all or Save choices with Advertising (Meta) selected. The selection alone does not start tracking. Saved choices, including refusals, remain respected. Accepting analytics alone or email marketing does not enable Meta tracking, and your purchase does not depend on it. Earlier marketing grants do not enable the added matching cookies and checkout measurement; we ask you to review and save the updated choice.
After you choose Accept all or Save choices with Advertising (Meta) selected, and our server confirms the saved choice, the Pixel loads Meta's browser script on supported public information pages. It can set first-party _fbp and _fbc cookies to recognise a browser and, where present, a real Meta ad click. Before loading it, we remove query strings and fragments from the public page address; a valid Meta ad click can be retained separately only after the advertising choice is saved. The browser connection also gives Meta your IP address and browser or device information, and may send existing Meta cookies according to your browser settings. Meta may associate these details with your Meta account or ad interactions under its own privacy policy. The Pixel does not load on vehicle lookup, checkout, order, account, login, purchased-report, staff or calculator pages. We skip Pixel loading when the page address or referrer cannot be handled safely. Automatic event collection and advanced matching are disabled; we do not send submitted contact details, registration, VIN, report contents, order references or payment-session identifiers as measurement fields.
Our server can link your active saved advertising choice and permitted browser or ad click identifier to a new checkout. It sends a checkout-start event after the payment session is created, and a purchase event only after Stripe confirms a valid paid order. You do not need to return from Stripe for the eligible purchase to be measured. These events include the browser or click identifier, browser type, event time, value, currency, a random event identifier and a fixed public checkout address. A browser identifier can support matching even when there is no captured Meta ad click. The server events do not include your IP address or private page address. No purchase event is sent by the browser Pixel.
We remember this choice for up to 180 days. A secure first-party cookie records your saved-choice reference; the corresponding server record holds that choice. Browser and click identifiers are used for no more than 90 days from their recorded creation time. An unfinished checkout reservation is removed by the next scheduled cleanup after 24 hours; a completed checkout link is retained for up to 30 days, with its matching details cleared once a purchase is queued. Queued event matching details and browser type are cleared after delivery, withdrawal or abandonment; a minimal duplicate-prevention record remains for up to 30 days. Declining or withdrawing marketing consent disables future Pixel events, removes accessible Meta measurement cookies on our domain and cancels events that have not been sent. It does not undo data already received by Meta or remove cookies on Meta's own domains. We do not sell browsing data or create remarketing audiences through this feature.
See our Privacy Policy or email support@buildsheetpro.io.