Cookie policy

Where we are today

Our website sets no cookies. Not one — not analytics, not advertising, not even a preference cookie. We checked on 3 September 2026 and we will keep this page honest as that changes.

That is unusual enough to be worth stating plainly rather than publishing a table of cookies we do not have.

Three things are true alongside it, and all three are below: our pages load a font and a stylesheet from other companies, which is not a cookie but does tell them your IP address; our booking page stores one item in your browser’s local storage to hold your basket, which is not a cookie but is the same idea; and our checkout runs on a different website, which does set a cookie.

1. What a cookie is, briefly

A small file a website asks your browser to store, so it can recognise your browser next time. “Cookie” in this policy also covers similar technologies — local storage, tracking pixels, and device fingerprinting.

UK law (the Privacy and Electronic Communications Regulations) says we may only set a cookie without asking you first if it is strictly necessary to provide something you asked for. Everything else — analytics, advertising, anything that follows you — needs your permission before it is set, not after.

2. Cookies on snsdriven.com

2.1 Strictly necessary

We do not need to ask permission for this one, because it exists purely to record your answer. If you have not made a choice yet, it does not exist.

2.2 Advertising and measurement — only if you accept

We use Meta’s advertising pixel so we can tell whether our adverts actually work. It does not run unless you press Accept on our cookie banner. This is not a script that loads and then sits idle: until you accept, the code is never fetched from Meta at all, and if you press Reject it is never fetched.

If you accept, it sets these:

Both durations above were measured in a real browser on 3 September 2026, by accepting and reading what was actually stored — not copied from Meta’s documentation.

What it tells Meta: which of our pages you looked at, and whether you clicked through to our eligibility form. The pixel does not send Meta your name, your email address, your licence details or anything you type into our site. You can change your mind at any time from the Cookie settings link in our footer, and we delete the two cookies above when you do.

There is a second, separate thing we should mention here even though it is not a cookie and nothing on this page controls it. When a booking completes, our booking system reports that to Meta directly — server to server, not through your browser — so we can tell whether an advert led to a booking. That message includes your name, email address and phone number scrambled into an unreadable code before it leaves our systems, and it is sent only for bookings we have already checked and accepted. It never includes your licence number, date of birth or anything from your eligibility form. This is not switched on yet — we are telling you before it starts rather than after. Our privacy policy sets it out in full.

2.3 Things that are not cookies, but are worth telling you about

Our pages load two files from other companies. Neither sets a cookie, but both mean your browser makes a request to that company, and a request includes your IP address.

We do not control either. If you would rather this did not happen, a browser extension that blocks third-party requests will stop it, and the site will still work — it will just look slightly different.

If you accept advertising cookies, Meta’s pixel also writes three items to your browser’s local storage, which is a different mechanism to a cookie but is still storage on your device: lastExternalReferrer and lastExternalReferrerTime (which site you came from, and when), and multiFbc (only if you arrived from one of our adverts). We list them because they are stored on your device and the law does not care what the storage is called. They are removed when you clear site data for this site in your browser; unlike the cookies above, our Cookie settings link cannot delete them for you.

2.4 Links, not embeds

Our Instagram and WhatsApp buttons are ordinary links, not embedded widgets. Clicking one takes you to Meta’s own app or website, under their policies rather than ours. The buttons themselves load nothing and set nothing — the only thing on our pages that contacts Meta is the advertising pixel described in section 2.2, and only if you accepted it.

3. Our booking page — local storage, not cookies

The private booking page we send to approved customers loads Booqable’s booking software so you can see live prices and availability. It sets no cookies. It does store one item in your browser’s local storage:

This is strictly necessary — it is the basket itself, not a record of your behaviour — so we do not ask permission for it. It holds no personal information: it is a random reference, not a name, an email address or a profile.

Two honest details. It is created when the page loads, before you have chosen anything, and it is not removed when you leave. You can delete it at any time by clearing site data for snsdriven.com in your browser settings.

4. Cookies at checkout — a separate website

When you go to pay, you are handed to checkout.snsdriven.com. That is our storefront, but it runs on Booqable’s system, and as far as your browser is concerned it is a different website with its own cookies.

What it sets:

It also stores the same bqCartId basket identifier described in section 3, and loads its typefaces from fonts.bunny.net. Booqable’s hosting adds one further request, to Cloudflare’s website-analytics service (static.cloudflareinsights.com) — that is injected by Booqable’s infrastructure rather than by anything on the page, we cannot switch it off, and it sets no cookie.

There is no advertising or analytics tracking on the checkout. We checked on 3 September 2026, and _booqable_session was the only cookie — Secure, HttpOnly, SameSite=Lax, and deleted when the browser closes.

5. Our eligibility form

Our eligibility form is hosted on Google Forms at docs.google.com and requires you to sign in with a Google account. Google sets its own cookies there, under its own privacy and cookie policies, not ours. We cannot change that, and our banner does not reach it.

Between our site and that form sits one page of ours, snsdriven.com/eligibility, which exists only to hand you across — some apps, Instagram in particular, open links in a built-in browser that Google will not accept a sign-in from, and that page helps you out of it. It sets no cookies, stores nothing and loads no tracking of any kind, which is why no banner appears on it. We verified this on 3 September 2026 by loading it and reading the browser’s own cookie and storage list.

6. How to change your mind

• On our site: the Cookie settings link in the footer of every page reopens the banner. Changing your answer takes effect immediately, and if you turn advertising off we delete the cookies it set.
• In your browser: every browser lets you block or delete cookies. If you delete our sns_consent cookie, we will ask you again next time.
• Everywhere: www.aboutcookies.org explains how, browser by browser.

Turning cookies off does not stop you using our website or making a booking.

7. Questions

Email enquires@snsdriven.com. Our privacy policy covers everything else we do with your data — what we collect when you hire a vehicle, how long we keep it, who we share it with, and your rights.