Privacy & Analytics

DIAN Racing keeps this website’s analytics deliberately minimal and privacy-friendly. We measure how the site is used in aggregate so we can improve content, navigation, recruitment, and sponsorship communication — nothing more.

What we collect

We use privacy-first, cookieless analytics to record anonymous, aggregated usage statistics:

  • Page views (which pages are visited, and the general source of a visit such as a search engine or a campaign link)
  • Clicks on important elements: calls-to-action, sponsor and partner links, “Join Us” / recruitment links, contact links, language switches, and document downloads
  • Whether visitors reach key pages (for example recruitment or contact)
  • Whether a page is missing (404) or a basic front-end error occurs, so we can fix broken pages

For these events we store only safe, non-identifying details — the page path, a short element label or id, the destination domain for external links, the file type for downloads, and the current language.

What we deliberately do not collect

  • No names, email addresses, phone numbers, or other personal identifiers
  • No form input contents — we only ever record whether a submission succeeded or failed
  • No keystroke logging
  • No session replay or screen recording
  • No advertising trackers
  • No cross-site tracking or browser fingerprinting
  • No exact IP addresses
  • No full URLs carrying sensitive query parameters — we keep only standard campaign tags (utm_source, utm_medium, utm_campaign, utm_content, utm_term)

How analytics is loaded

The analytics script is loaded asynchronously and never blocks the page from rendering. Analytics can be fully disabled by the site operators via configuration, and is turned off entirely during local development.

Why we do this

This data is used only to improve the website — its content, navigation, recruitment funnel, sponsorship communication, and technical quality. It is never sold, never used for advertising, and never used to identify individual visitors.

Questions about this policy? Reach us through the contact page.