Your account

Cookies and analytics

The websites ask once and the portal follows that answer. Analytics and ad cookies wait for consent; change it any time.

Updated 2026-10-15 · 8 min read

The first time you visit TheTuningGroup's or TheTuningFiles' website, a banner asks what may be set: analytics (measuring how the site is used), marketing (crediting adverts and showing relevant ones), both, or neither. Customise lets you pick one without the other; nothing is ticked in advance. Until you answer — and whenever you decline — no analytics or advertising cookies are written. Strictly functional cookies (your session, your language, the answer itself) are always set; they are what signing in requires.

The portal never asks. Dealers and tuners are at work there, so it follows the answer you gave on the website you came through. If it has none — you went straight to the portal, or your browser cleared its cookies — it treats you as having declined.

What accepting does

Accepting lets the site measure how it is used, through Google's measurement tools — and, on TheTuningGroup's own website and portal, also through PostHog, a product analytics service hosted in the EU. What is measured is the pages visited and the actions completed: buttons and contact links pressed, searches run, forms started, sent or failed, and — on a tuning website — the car a visitor looks up, the tuning stage they pick, any extra services they tick, which route they take through the search and how far they get along it, and any purchase that follows.

The files attached to an order, the contents of messages and support tickets, and your sign-in details are never part of these measurements.

One decision covers the website and the portal. TheTuningGroup's website and portal share a domain, so they share the answer. TheTuningFiles' website is on a domain of its own, so its answer travels with you on the sign-up and login links, and the portal keeps it.

How the choice is applied. The page always records the steps above in its measurement layer; your answer decides which tools may act on them. Without analytics consent, Google's measurement sends only cookieless signals — no identifier, nothing stored on your device — that Google uses to estimate totals. Without marketing consent, advertising tools (Google Ads, Meta) set no cookies and receive none of your details.

Is the licence plate part of what is measured?

Yes, when the car was found by plate — on a tuning website built on the platform. Looking a car up puts that car into the measurement data — make, model, engine, year, fuel, power, and which of the three routes (licence plate, search, or browse) the visitor took. On a tuning website, where the route was the plate, the plate itself is sent to the site owner's account, tidied to one form (upper case, no dashes or spaces), with a one-way digest of it alongside. On TheTuningGroup's own website only the digest is sent, never the plate.

This includes lookups that find nothing. On a tuning website the plate is recorded as the search term when it is submitted, so a plate we hold no car for is measured too — along with the reason it failed, which is what tells a site owner which vehicles their visitors want and their catalogue does not cover.

A licence plate is personal data in most of Europe, so it is worth saying plainly rather than leaving it to be found in a network tab. The vehicle identification number (VIN) and the German HSN/TSN key numbers stay with the lookup and are never sent.

Contact details are handled differently. Where a visitor gives an email address or a phone number on a contact or quote form, the measurement carries a one-way digest of it — never the address or the number itself. Two digests, in fact: Google and Meta each require the address to be written their own way before it is digested, so the same address produces a different one-way value for each, and neither can be turned back into the address.

These digests go to Google and Meta only with marketing consent. They are what lets an advert be credited with a sale without anyone learning who bought — but a digest of a real person's address is still that person's data. On TheTuningGroup's and TheTuningFiles' own sites and portal, the advertising tags are set to require marketing consent before they read them.

The same applies to you when you are signed in to the portal. Google and Meta receive your account as a set of one-way digests — of your user id, your organisation and your own email address — never as the address itself, which does not leave your browser. The digest of your user id is what lets a visit on your laptop and one on your phone be counted as one person rather than two. PostHog knows your account by its internal ids (user, organisation and workspace) together with your role, plan, subscription status and language — never your name, email address, phone number or licence plates. PostHog follows your analytics answer, and the digests your marketing answer: decline, and none of it is sent from your browser. Your plan, your role and whether you are on a trial are also reported, but as plain categories that describe the account rather than identify you.

Separately from the banner, the portal records what happens to your account — an order placed, a file delivered, a plan changed — in PostHog for TheTuningGroup's own product analytics, keyed on your user id and without names, email addresses, plates, file names or message text.

Ad clicks and sign-ups

On TheTuningGroup's and TheTuningFiles' own websites and portal, accepting marketing also keeps track of the advert or campaign that brought you: the click ids and campaign tags on the link you arrived through, kept in a cookie for 90 days. When you sign up, or use the portal while signed in, these are stored with your account together with Google's and Meta's browser ids, your IP address and your browser's user agent. That lets a sign-up, a payment that settles days later, or a first paid plan be reported to Meta from our servers as the result of that advert — and a payment to Google too — identified by the one-way digest of your user id and, for Meta, of your email address. Only sales TheTuningGroup itself makes are reported this way, never a purchase from a tuner's shop.

Before you accept, an ad click is held only in that browser tab (session storage, gone when the tab closes) and nothing is sent; it is written to the cookie the moment you accept. Decline, and it never leaves the tab — and a cookie already written is deleted. A tuning website built on the platform does none of this.

Whose analytics account receives all this?

It depends on whose site the visitor is on.

On TheTuningGroup's own website and portal, the measurement goes to TheTuningGroup.

On a tuning website built on the platform, it goes to the site owner: the Google Tag Manager container, the Google Analytics 4 property and the Meta Pixel entered under Website → Settings, in the Tracking & code card. If you run such a site, everything described above arrives in your own account, the licence plate included — which makes it yours to declare in your privacy policy and yours to set a retention period for.

Measurements about the platform itself — sign-ups, subscriptions, orders placed, orders delivered — are never handed to a site owner's account. Only the visitor-facing events on their own site are.

Changing your mind

Use the Cookie settings link in the website footer to withdraw or change a decision at any time. Withdrawal takes effect immediately — measurement and advertising cookies stop the moment you clear the choice, the ones already set are deleted, and the banner comes back so you can decide again. The portal follows the new answer on your next visit. Ad-click details already stored with your account from an earlier acceptance stay with it, so a later payment or first paid plan can still be reported with them.

Declining never limits the product: every feature works identically either way.

No banner appeared, or my choice keeps being forgotten

On a tuning website the banner is the site owner's setting, not a fixed part of the page: a site whose owner has not turned the banner on will not show one, and tags then start at the default the owner chose. What the owner's own tags do with the measurements and digests is set in the owner's Tag Manager container, which they configure. On TheTuningGroup's and TheTuningFiles' websites the banner is always shown until it is answered; the portal never shows one.

If the banner returns on every visit, the decision cookie is not surviving — usually a browser set to clear cookies on close, or private browsing. The choice is stored in a cookie, so a browser that discards cookies discards the answer with them.

Anything else, tell TheTuningGroup Support which page you were on, whether you accepted or declined, and what you saw instead — that is enough to trace which of the two banners was involved.

Was this helpful?

Didn’t find your answer?

Sign in and open a ticket, or contact us — a question that needed a person is also how this article gets better.

Last verified 2026-10-15.