Cookie Policy

Last updated: [effective date] · Operator: [operator legal name]

This page explains the cookies and similar on-device storage EVRadar uses. We keep it to the minimum: preferences that make the site work, sign-in, and — only if you agree — analytics.

This document still contains [placeholder] fields. Fill them in src/lib/legal.ts and have the text reviewed before you rely on it — it’s an accurate draft of what the site does, not finished legal advice.

What we use

NamePurposeTypeKept for
evradar-countryRemembers the country detected from your connection, to default your language and currency.Functional~1 year
evradar-localeStores the language you choose.Functional~1 year
evradar-consentRemembers your cookie choice on this bar.Functional~1 year
sb-… (Supabase)Keeps you signed in to your account.FunctionalSession / until sign-out
_ga, _ga_… (Google Analytics)Measures anonymous usage (visits, pages, device). Set only after you accept.Analytics~13 months

On-device storage (never sent to us)

These live in your browser’s local storage and are never transmitted to any server — they stay on your device:

evradar:theme, evradar:locale, evradar:currency, evradar:marketYour display preferences (light/dark, language, currency, price market).
evradar:compare, evradar:viewedThe cars you compare and recently viewed — used only on your device to power the “For you” suggestions.

Analytics & your consent

We use Google Analytics 4 to understand how the site is used. It runs in Google’s Consent Mode with everything denied by default: no analytics cookies are set and no data is sent until you press Accept on the cookie bar. If you decline, analytics stays off. You can change your mind at any time:

You can also block or delete cookies in your browser settings. Blocking functional cookies may sign you out or reset your preferences.

More information

How we handle personal data generally is described in our Privacy Policy. Questions? Contact admin@evradar.online.