Legal

Cookie Policy

Short, because there is very little to say.

Last updated August 19, 2026

The short version

Browsing this site sets no cookies at all. Not one. There is no analytics, no advertising pixel, no tag manager, and no third-party script on any page.

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.

Which is why there is no consent banner. There is nothing here to consent to.

Before you sign in

Zero cookies. The marketing pages, the coverage demo, and every page you are reading now are rendered without setting anything in your browser and without loading anything from another company’s servers.

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; nothing is left behind in your browser and you are not followed anywhere.

After you sign in

At most two cookies, named here because a policy that will not name them is not a policy.

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.

Both are strictly necessary — the product cannot function without them — which is the category exempt from consent requirements under every privacy regime that applies to us. We are not relying on that exemption to sneak anything past it; those two are genuinely the whole list.

What we do not use

No analytics of any kind — no Google Analytics, no Plausible, no self-hosted equivalent.
No advertising or conversion pixels, and no remarketing.
No tag manager.
No social embeds, chat widgets, or third-party fonts loaded at page view.
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, no script, and it tells us nothing about you before you decide to press the button.

If that ever changes

Adding any non-essential cookie to DealerTech.io means adding real consent first — a genuine choice, defaulting to off, that works if you decline it — and rewriting this page in the same change. We would rather not have the data than have it dishonestly.

You can also block or clear cookies in your browser. Clearing the two above signs you out and forgets which rooftop you were on; nothing else in the product depends on them.

Questions

info@dealertech.io.

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.