LEGAL

Privacy Policy

Last updated: 18 November 2026

1. Who is responsible

The controller for data processing on this website and in the Berk desktop app ("Berk", "we", "us") is:

Umur Karakas
[Street and house number]
[Postcode] [City], Germany
Email: [contact email address]

We are not required to appoint a data protection officer. For any privacy question or request, email us at the address above.

2. Summary

3. This website

The website is hosted on Cloudflare (see section 9). When you visit it, your browser sends technical data such as your IP address, the requested page, date and time, and browser type. Cloudflare processes this data to deliver the pages and protect them against attacks. We do not run access logs of our own.

The website uses no analytics or tracking tools. It sets cookies only when you use the account page or the web stint planner: a short-lived cookie (10 minutes) that protects the Discord sign-in against forgery, and a sign-in cookie that keeps you signed in for up to 30 days or until you sign out. Both are strictly necessary for the sign-in you ask for (§ 25(2) no. 2 TDDDG) and are never used for tracking.

Legal basis: Art. 6(1)(f) GDPR — our legitimate interest in delivering a secure, working website.

Links to other websites (for example OpenKneeboard or Unsplash) only send data to those sites if you click them.

4. Account and sign-in (Discord)

Berk requires a Discord account. When you sign in, you are sent to Discord's own login page; we never see your Discord password. We request the Discord scopes identify and guilds.members.read and receive:

If you sign in on the website's account page, we store a website session (when it was created and last used, and whether your account passed the Discord server check at sign-in) so the page can show your profile, plan, plan history and signed-in app installs. Signing in on the website does not start the free trial.

We then store a sign-in session for each installation of the app, together with when it was created and last checked. The app checks your session with our server each time it starts and periodically while it runs. We also store your access status (free-trial start date and paid-until date), a daily count of sign-ins and checks per account, and a log of refused sign-ins (date, reason, Discord ID and name) for troubleshooting and abuse prevention.

To give each PC only one free trial, the app sends a one-way scrambled form (SHA-256 hash) of your Windows installation ID when you sign in and when it checks your session. We hash it once more and store it with your Discord user ID. It cannot be turned back into the Windows ID and is only used to decide whether a free trial is offered. Free trials are also only offered to Discord accounts at least 60 days old; the age is read from the Discord user ID.

If you join the Berk Discord community server, our bot gives your account a Trial, Basic or Premium role that matches your membership, and removes it when the membership ends.

Your IP address is used briefly to rate-limit requests to our server. It is not stored.

Legal basis: Art. 6(1)(b) GDPR — performance of our contract with you (providing the app and checking your access); Art. 6(1)(f) GDPR — our legitimate interest in preventing abuse.

5. Payments

Paid plans are sold through our online reseller Paddle.com, which is the Merchant of Record for all orders. Paddle processes your payment, billing and tax details as an independent controller under its own privacy policy. We receive from Paddle only what we need to activate your plan: your Discord user ID (passed into the checkout), the plan, subscription status, dates and amounts. We never see your card or bank details.

For contributions made before Paddle checkout was available, we record the Discord user ID, the period purchased, the amount and a short internal note.

Legal basis: Art. 6(1)(b) GDPR (contract) and Art. 6(1)(c) GDPR (statutory retention duties under German tax and commercial law).

6. Data the app sends to our server

Berk reads iRacing telemetry on your PC. The following items are sent to our server (running on Cloudflare) because the features depend on them. They are linked to your account on the server; when shared with other users they are only shared in aggregated or anonymised form.

WhatWhyWhen
Session timing aggregates: pit-lane time loss, stop counts, sector splits and track geometry for a car/track combinationA shared community cache so every user gets accurate pit and timing estimates soonerOnce per track and class during a session
Tyre-wear readings from your pit stops: car, track, series, session type and ID, tyre wear, temperatures, pressuresImproving tyre-wear modelsAt pit stops
Lap count: how many laps you completed in your own car in online sessions since the last report. One number; no track, car or lap timesThe “laps driven with Berk” total on the websiteAbout every 10 minutes while driving, and when Berk closes
Names of other drivers that the Crew Chief voice packs cannot pronounce yet (first and last name only)Adding those names to voice packsEvery few minutes while the voice feature is used
Series, season, track, week and car classLooking up historical pit-loss and race-distance data from iRacing's data service, using our own iRacing accountAutomatically in official sessions; when you open the Team Planner
Map tile coordinatesSatellite map images in the lap viewer (we fetch them from Esri on your behalf, so Esri does not see your IP address)Only when you open the satellite map

Other drivers' names: iRacing shows the names of the drivers in your session. Berk uses them on your PC for timing displays and voice callouts. Only names the voice packs are missing are sent to us, without any iRacing IDs, so we can record pronunciations. Where we cache iRacing results on our server, other drivers' iRacing customer IDs are replaced by a keyed hash.

Legal basis: Art. 6(1)(b) GDPR (providing the features) and Art. 6(1)(f) GDPR — our legitimate interest in improving the accuracy of Berk's estimates and voice callouts. You can object at any time (see section 11).

Updates and downloads

The app checks GitHub for updates when it starts, and periodically checks GitHub for voice-pack updates and a service status file. These requests contain no personal data, but GitHub necessarily sees your IP address. Legal basis: Art. 6(1)(f) GDPR — keeping the app up to date and secure. The installer download link on this website is also served from GitHub through our server.

7. Optional integrations

These only run if you enable them. Legal basis: Art. 6(1)(a) GDPR (your consent, given by connecting or enabling the feature) and Art. 6(1)(b) GDPR. You can disconnect any of them at any time in the app.

8. Data stored on your PC

Berk stores its settings, sign-in tokens (Discord and Garage 61 tokens are encrypted with Windows data protection), fuel and tyre history, team plans, session snapshots and diagnostic logs in its folder on your PC. This data stays on your PC except as described above. Uninstalling the app and deleting its data folder removes it.

9. Service providers and transfers outside the EU

Where personal data is transferred to the USA, the transfer is based on the EU–US Data Privacy Framework where the recipient is certified under it (Art. 45 GDPR), and otherwise on the EU Standard Contractual Clauses (Art. 46 GDPR). Data transferred to the UK is covered by the European Commission's adequacy decision.

We do not sell personal data or use it for advertising.

10. How long we keep data

DataKept
Sign-in sessions and Discord refresh tokenUntil you sign out of that installation, your access is withdrawn, or you ask us to delete your account
Website sign-in sessions30 days, or until you sign out on the website
Account, profile and access status (trial, paid-until)While your account exists
Payment and contribution recordsUp to 10 years, as required by German tax law (§ 147 AO, § 257 HGB)
Hashed installation IDs (one free trial per PC)While your account exists
Daily sign-in counts90 days
Refused sign-in logMost recent 500 entries
Shared timing cache365 days
Lap counts (per account and day)Kept while your account exists; only the total is shown
Missing voice-pack names180 days
Tyre-wear readingsWhile your account exists
Team Sync live data / team plans12 hours / until replaced or deletion is requested
Discord teams: membership / invitations / saved plansuntil you leave, are removed or the team is deleted / 14 days or until answered / until deleted by a team member or the team is deleted
Temporary sign-in handover data (Discord, Garage 61)10 minutes at most

11. Your rights

Under the GDPR you have the right to:

To exercise any of these rights, including deleting your account, email us from or with your Discord username so we can find your data. We will respond within one month.

12. Children

Berk is not directed at children under 16. Discord and iRacing set their own minimum ages.

13. Changes

We will update this policy when Berk's features or our service providers change. The date at the top shows the current version.