Privacy Policy & Data Transparency

The kersF1 telemetry platform is designed with a strict privacy-first engineering philosophy. We do not require user account registration, do not collect personal identifiers (such as names, emails, or phone numbers), and do not sell, rent, or monetize any user data.

To provide a seamless, persistent telemetry experience across race sessions, kersF1 stores small configuration tokens locally in your browser's localStorage. This data never leaves your device:

The telemetry, lap times, tire degradation data, and live sector timings displayed on kersF1 are retrieved from public open-access Formula 1 telemetry feeds:

• Jolpica-F1 / Ergast Archive: Historical race results, qualifying data, driver standings.
• OpenF1 API: Real-time high-frequency GPS positions, throttle/brake telemetry, tire stints.
• Formula 1 Live Timing Feed: Team radio audio communications and public timing feeds.

When your browser queries these services, your IP address is processed temporarily by the respective CDN edge servers in accordance with standard internet networking protocols.

kersF1 utilizes privacy-respecting client analytics solely to identify slow network requests, broken circuit maps, and platform crashes. Analytics cookies are completely disabled by default until and unless you explicitly opt in via the Cookie Consent banner.

Under the EU General Data Protection Regulation (GDPR) and California Consumer Privacy Act (CCPA), you retain the absolute right to decline analytics tracking without affecting any telemetry visualization features of the platform.

5. Security Governance & Open Source

All data in transit is protected using Strict Transport Security (HSTS) and modern TLS 1.3 encryption. kersF1 enforces a stringent Content Security Policy (CSP) to neutralize cross-site scripting and unauthorized data exfiltration.

For security inquiries or questions regarding this policy, please open an issue in the official GitHub project repository.