Privacy and consent

What the site does now

• Loads the listing dataset needed to render the explorer.
• Keeps only a thin long-term index of active listings rather than a full source replica.
• Uses necessary in-browser state for core operation and the consent record itself.
• Stores optional preferences such as region, range mode, view mode, sort order, theme, and dismissed hints only if you opt in to preferences.
• Loads Google Analytics 4 only if you opt in to analytics.
• Sends visitors to third-party marketplace pages when they choose to open a listing.

What the site does not currently do

• No account system.
• No checkout or payment flow.
• No built-in messaging or comments.
• No personalized ad experience on the core explorer.
• No broad telemetry stream for render performance or deep behavioural profiling.
• No long-term storage of source images, seller names, seller contact details, or full raw listing text.

Third parties

Marketplace sites, Google Analytics when analytics consent is granted, and any future ad or sponsor destinations operate under their own policies and terms. Clicking out to those pages means leaving the direct control of evrange.info. The original listing remains the authoritative source for photos, seller identity, exact specification, and live availability.

Cookie and similar technology choices

The site separates storage and tracking into three groups:

• Necessary: core operation and the consent record.
• Preferences: region, view mode, sort order, range mode, theme, and dismissed helper messages across visits.
• Analytics: a narrow set of Google Analytics 4 product events such as launcher opens, view changes, model opens, and outbound listing clicks.

Preferences and analytics are off until you opt in. The site includes a persistent Privacy choices control so consent can be revisited later.

Current analytics boundary

The analytics setup is intentionally narrow. It exists to understand whether the product is being used, not to maximise data collection. Google Analytics is not loaded until analytics consent is granted, ad-related storage stays denied, IP anonymisation stays enabled, and technical performance metrics remain local debug signals rather than a persisted analytics stream.

The differentiating product work is not broad user surveillance. It is the site's own EV-specific derived analysis: range references, degradation logic, confidence tiers, cross-source dedupe, and other decision aids built on top of a thin source-linked index.

Consent controls and renewal

The site shows privacy choices on first visit, offers a rejection path that is as direct as acceptance, and allows you to reopen those choices later through the persistent privacy button. Consent records are stored for a limited period and should be refreshed periodically rather than assumed forever.

Listing-data boundary

The long-term listing store is intentionally narrow. The site keeps source links, coarse county-level location, and the fields needed for EV comparison and derived range logic. It does not aim to be a permanent mirror of the source marketplace page.

County-level distance is an approximation derived from county centroids, not a stored seller address or exact seller pin.

Retention and takedowns

Operational listing snapshots are kept on a short retention window and older runtime payloads are pruned rather than kept indefinitely. If a listing should be removed or corrected, the published contact route should be used so it can be suppressed from the index and the next publish cycle.

Consent and ad boundary

No broader ads or analytics should be treated as settled just because a narrow consent flow now exists. Any serious expansion of AdSense, more invasive measurement, or personalised ad behaviour still needs separate review for user trust, legal fit, and platform policy.

Updates and contact

If the product later adds richer contact routes, account features, broader ads, or more data collection, this page should become more specific rather than staying vague. The public feedback and enquiry route lives on the Contact page.