Legal
Cookie Policy
Short, because there is still very little to say.
Last updated October 5, 2026
The short version
These marketing pages run Google Analytics, which sets two cookies in your browser and tells Google which of our pages you read. It is how we find out whether anybody is reading them.
Google Analytics never runs where the work happens. It does not load in the signed-in workspace, on a customer’s menu link, on a document-capture page, or on the demo tour. Those pages send Google nothing, because their URLs are nobody else’s business.
PostHog is our product analytics. It runs on these pages and inside the signed-in workspace, counts page views and errors, and records a session replay with all text and form fields masked. It uses your browser’s local storage, not cookies. It is off on customer links, capture links, invitations and the operator console, and replay is off on sign-in, billing and customer-record screens. A section below says exactly what it sends.
If your browser sends Global Privacy Control, none of it loads at all — no Google script, no cookies, no request to Google, and nothing is sent to PostHog either. The same goes for Do Not Track, for PostHog.
Signing in sets one strictly necessary cookie: the session that keeps you signed in. A second appears only when you pick which rooftop you are working, and it is a preference, not a tracker. That is the complete list.
Before you sign in
Two cookies, both set by Google Analytics, both first-party — they are written on this domain and no other site can read them. Named here, because a policy that will not name them is not a policy.
_ga
Google Analytics’ visitor identifier: a random number that lets Google tell a returning browser from a new one, so two visits from you are not counted as two people. It contains no name, no email and nothing you typed. It expires two years after your last visit.
_ga_ followed by our measurement ID
The session counter for this specific site — the rest of its name is our own measurement ID. It records when the current visit started, so a page you open after lunch is a second visit rather than a very long first one. Also two years.
What Google receives alongside them is the ordinary analytics set: which page you are on and which page or search sent you, an approximate location worked out from your IP address, and your browser, device type and screen size. We do not send it anything else, and there is nothing to send — you have not told us anything at this point.
The tag is configured with Google Signals and ad-personalisation signals switched off. That is set in our own code rather than in a settings panel, and it is what keeps this a page count instead of an advertising audience: nothing here is joined to your Google account across other sites, and none of it can be used to target an ad at you.
If you submit the demo-request form, what you typed is sent to us and stored — see the privacy policy. That is a form submission, not a cookie, and it does not travel to Google.
Where Google Analytics never runs
Google Analytics is switched on by an allowlist of the eleven marketing and legal pages, matched as whole paths. Everything else on this domain is off, including everything that does not exist yet. Concretely, no analytics script loads and no page view is sent from:
- The workspace. Every signed-in page — the drive, a customer record, a vehicle, the loaner desk, the manager and BDC screens, billing, setup, the admin console. Those URLs contain a dealership’s work.
- Anything reached by a link with a code in it. A menu link sent to a customer’s phone, a photo-capture link, an invitation, a paired tablet. In each of those the URL is the credential, and handing that address to another company would be handing over the key.
- Sign-in, sign-up and the demo tour. The tour is in our sitemap and is a perfectly ordinary page to read; it is left out of analytics anyway, because the next thing that happens on it is somebody typing an access code.
This is not a promise about our intentions. It is one list of paths, shared with the file that generates our sitemap so the two cannot drift apart, and a test that fails if the analytics component is imported anywhere except the site’s root layout.
PostHog, on the site and in the workspace
PostHog (a US company; we use its US cloud) gives us product analytics, error reports and session replay. Unlike Google Analytics it also runs inside the signed-in workspace, because that is the product we are trying to improve. Here is what it does and does not do.
- No cookies. It keeps a random anonymous id in your browser’s local storage, plus a session id in browser storage. When you are signed in it uses a one-way (SHA-256) hash of your account id instead, never the id itself, and never your name or email. Signing out, or reaching the sign-in or sign-up page while identified, clears it.
- What it records. Page views and page leaves, with record ids replaced by a placeholder and any query string or anchor removed; errors; and session replay. Replay masks all text and all form fields and blocks images, video and canvas, so it shows the shape of a screen and where people click, not what is written on it. Page titles are dropped. Button and link text is not captured. In the signed-in workspace an error report carries the error type and where in our code it happened, not its message.
- What it never receives. Names, emails, phone numbers, or any customer, vehicle or deal data; anything you type; or any address containing an access code. It does not load at all on a customer’s menu link, a document-capture link, an invitation, the presentation screen, the operator console or our API.
- Where replay is off. Sign-in, sign-up, billing, the demo tour, data import, the team, devices, loaner and customer screens, and vehicle contract pages. Page views are still counted there; nothing is recorded.
- What our server tells it. When a dealership signs up, an invitation is accepted or a demo request is saved, our server sends PostHog a count of that event with a label and a hash (or, for a demo request, a random id). Nothing you typed is in it.
- Like any service you connect to, PostHog sees the IP address of the request, which it uses for an approximate location. We do not sell this data, and we do not share it for advertising.
Both PostHog and Google Analytics stay off for a browser sending Global Privacy Control, and PostHog stays off for a browser sending Do Not Track.
Global Privacy Control
Some browsers, and several privacy extensions, send a signal called Global Privacy Control — a standing instruction not to sell or share your data. If yours does, this site does not load Google Analytics at all: the script is never requested, the two cookies above are never set, and Google never learns you were here. PostHog likewise does not load, and nothing is sent to it.
No banner to dismiss, and nothing to remember on your next visit. Your browser already said it; we listened.
After you sign in
At most two more cookies. Google Analytics does not run here; PostHog does, as described above, and it uses browser storage rather than cookies.
The Supabase authentication session
Set by our authentication provider when you sign in, and refreshed as you use the product. It is what makes the next page know it is still you. Without it there is no way to be signed in at all. It is stored so that page scripts cannot read it, and it is cleared when you sign out.
dt_active_store
Remembers which rooftop you are currently working, for people who hold a role at more than one store in a group. It is set when you pick a store — someone who only ever works one rooftop may never receive it. It is a preference, never a permission: the value is only ever used to pick from the list of dealerships your account provably has a role at, so editing it in your browser changes which of your stores you land on and nothing else.
What we do not use
- No advertising or conversion pixels, and no remarketing.
- No tag manager. Google Analytics is loaded directly, as one script we control.
- No analytics tool other than Google Analytics and PostHog — no Plausible, no Hotjar, no heatmaps. The only session recorder is PostHog’s masked replay, described above.
- No social embeds, chat widgets, or third-party fonts loaded at page view. Our typefaces are served from this domain.
- No cross-site tracking, and no fingerprinting as a substitute for cookies.
The demo-request form records which page it was submitted from. That is a hidden field in the form itself — no cookie, and it tells us nothing about you before you decide to press the button.
If that ever changes
Adding anything beyond what is named on this page means rewriting this page in the same change, and re-dating it. Adding a cookie that is neither strictly necessary nor covered by the analytics described above means adding real consent first — a genuine choice, defaulting to off, that works if you decline it. DealerTech.io would rather not have the data than have it dishonestly.
You can also block or clear cookies in your browser, and blocking Google Analytics changes nothing about how this site works. Clearing the two sign-in cookies signs you out and forgets which rooftop you were on; nothing else in the product depends on them.
Questions
This document was written from the software it describes, and has not been reviewed by counsel. It is the honest starting text, not legal advice. If a term here matters to your dealership’s decision, tell us and we will get it right rather than argue it later.