Last updated: 20 September 2026
The short version. PaceGuru processes your driving and telemetry data entirely on your own machine. Your laps, your recordings and your settings never leave your PC and are never stored on our servers. What we do store is only what is needed for your licence, your account and running the website — all of it listed individually below.
This is a courtesy translation. In case of any discrepancy, the German version is the legally binding one.
Dominik Schmitt
Amelungenstraße 62
96129 Strullendorf
Germany
Email: [email protected]
A data protection officer is not legally required and has not been appointed.
The website and all related services run on a server operated by Hetzner Online GmbH, Industriestr. 25, 91710 Gunzenhausen, Germany. The server is located in Germany. Backups are stored, encrypted, with the same provider (Falkenstein, Germany). A data processing agreement under Art. 28 GDPR is in place.
Legal basis: Art. 6 (1) (f) GDPR — legitimate interest in secure, reliable operation.
Every request is automatically logged with the data your browser transmits:
This data is technically necessary to deliver the site and serves to detect and fend off attacks. It is not combined with other data sources and is deleted automatically after 14 days at the latest. Legal basis: Art. 6 (1) (f) GDPR.
Access to paceguru.net is routed through the network of Cloudflare, Inc., 101 Townsend St., San Francisco, CA 94107, USA. Cloudflare acts as an intermediary, distributes delivery and mitigates attacks. In doing so, Cloudflare processes your IP address. Transfer to the USA may occur; Cloudflare is certified under the EU-US Data Privacy Framework and standard contractual clauses are additionally in place.
Legal basis: Art. 6 (1) (f) GDPR — legitimate interest in availability and attack mitigation. See the Cloudflare privacy policy.
We use no advertising, tracking or analytics cookies. There is no cookie banner because there is nothing to consent to. Only the following strictly necessary or convenience cookies are used:
| Name | Purpose | Lifetime |
|---|---|---|
cf_ipcountry |
Country code, so we can offer you the site in a matching language (notice banner). Contains the country only, not a precise location. | 1 hour |
lang_banner_dismissed |
Remembers that you closed the language notice. | 30 days |
pm_at, pm_rt |
Keep you signed in after login. Only set if you have an account and sign in. Not readable by JavaScript. | 15 minutes / 30 days |
Legal basis: § 25 (2) no. 2 TDDDG in conjunction with Art. 6 (1) (b) or (f) GDPR — these cookies are strictly necessary for the function you requested.
All fonts are served from our own server. No connection is made to Google Fonts or any other external provider, and no IP address is transmitted to third parties for this purpose.
An account is created with the sign-up form on the home page or on the sign-up page. We process your email address in order to confirm it, to write to you about your account, and to send you your access key.
While the closed beta is running, the key is issued automatically once you have confirmed your email address. The separate beta form that used to sit on the home page no longer exists — there is only one way to a key, and that is the account.
If you redeem an access code, we record which code was redeemed by your account and when. This prevents the same code being used more than once, and for that same reason it survives the deletion of your account — without any link to a person who still exists.
Legal basis: Art. 6 (1) (b) GDPR (contract and pre-contractual measures at your request), and Art. 6 (1) (f) GDPR for the block against multiple redemption.
If you create an account, we process:
| Data | Purpose |
|---|---|
| Email address | Sign-in, account correspondence, delivery of the licence key |
| Sign-in data (password, session tokens, licence key) | Signing in and linking your access. All three are stored in a form that cannot be reversed: what we hold cannot be turned back into the original. Your password itself cannot be viewed by us. |
| Operational and security data (timestamps, failed attempts, IP address) | Running the account and protecting it against automated password guessing. The IP address is stored as a digest only, never in plaintext. |
| Two-factor sign-in, if you switch it on | Second step when signing in. The secret of your authenticator app is stored encrypted — unlike your password it has to be recoverable, otherwise we could not check your codes. |
| Subscription data (Stripe customer number, status, period end) | Linking your account to your subscription and how long your access runs. Only exists once you have subscribed. |
Legal basis: Art. 6 (1) (b) GDPR (performance of contract) and, for the security measures, Art. 6 (1) (f) GDPR.
Retention: Account data is stored for as long as the account exists. If you delete your account, the account, its licence link and all sign-in data are deleted immediately. Security log entries no longer contain personal data afterwards and are removed after 12 months at the latest.
When you choose a password, we check whether it has appeared in known data breaches, using Have I Been Pwned with k-anonymity: only the first five characters of a digest of your password are transmitted. Neither the password, nor your email address, nor any other personal data leaves our server, and the provider cannot determine which password the query refers to.
Legal basis: Art. 6 (1) (f) GDPR — legitimate interest in protecting user accounts.
For confirmation, licence and security emails we use the mail service of Google (Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland). The recipient address and the message content are processed through Google's systems. Transfer to the USA may occur; Google is certified under the EU-US Data Privacy Framework.
Legal basis: Art. 6 (1) (b) GDPR.
Payments are processed by Stripe Payments Europe, Ltd., 1 Grand Canal Street Lower, Grand Canal Dock, Dublin, Ireland. When you take out a subscription we transmit your email address and your account identifier to Stripe; you enter your payment details and your billing address on Stripe's own page. You can pay there by card; on the annual plan you can also pay by PayPal.
We never see your full card details. They do not pass through our server and are not stored there. What we receive back from Stripe is the customer number, the status of your subscription and its period end.
Paying by PayPal. On the annual plan you can choose PayPal at checkout instead of a card. The payment is then handled by PayPal (Europe) S.à r.l. et Cie, S.C.A., 22–24 Boulevard Royal, L-2449 Luxembourg. Your email address and the amount are transmitted; signing in and approving the payment happen on a PayPal page, and PayPal's own privacy notice applies in addition. Legal basis: Art. 6 (1) (b) GDPR.
Transfer to the USA (Stripe, Inc.) may occur; the basis for it is the EU standard contractual clauses, and a data processing agreement under Art. 28 GDPR is in place. Stripe's own privacy policy applies to what Stripe does with the data as a controller: stripe.com/privacy.
Free trial, and why we remember a device. The trial is free and needs no payment details — Stripe is not involved in it at all. It can be started once per person and once per device. To make that hold even after an account is deleted, we store the device identifier the app transmits anyway (see section 13) when the trial is granted, together with the time and the identifier of the account that started it.
That single entry deliberately outlives your account; without it, deleting an account and signing up again would reset the trial. After a deletion the account identifier in it points to no account and says nothing on its own. The entry is deleted after 24 months.
Until 7 September 2026 we stored a digest of your payment card for this purpose instead, because the trial required a card back then. We no longer do.
Legal basis: Art. 6 (1) (b) GDPR (performance of contract) for the payment itself, and Art. 6 (1) (f) GDPR (legitimate interest in preventing repeated use of the free trial) for the device entry.
If you cancel through the cancellation form, we store your declaration together with the date and time it reached us: your email address, and any name, contract reference and reason you enter. § 312k (4) of the German Civil Code requires us to confirm exactly this to you, and to keep it available as evidence. The entry is deleted after three years (§ 195 German Civil Code).
Legal basis: Art. 6 (1) (c) GDPR (legal obligation) and Art. 6 (1) (b) GDPR.
PaceGuru signs in to our own server with your account — no third-party licensing service is involved any more. Transmitted are your account identifier, the session token and a device identifier. As with any request on the internet, your IP address is technically visible; what happens to it is described in section 3.
The device identifier is computed by the app on your machine and only a digest of it is transmitted (SHA-256 over identifiers of your Windows installation). Neither your hardware nor your Windows user account can be derived from that value. For us it answers exactly one question: is this the same machine as last time?
The device identifier serves two purposes: limiting how many machines use one account at the same time, and limiting the free trial to one per device (see section 11). For the second purpose it is stored separately and outlives your account — that is the only case in which this happens. You can see your devices in your account and sign each one out individually. A signed-out device is not deleted but marked as signed out — otherwise a shared account could no longer be told apart from someone simply changing computers. These entries are deleted with your account.
If our server is unreachable, PaceGuru keeps running on a previously issued, time-limited offline pass; no data is transmitted during that time.
Legal basis: Art. 6 (1) (b) GDPR (performance of the contract) and Art. 6 (1) (f) GDPR (legitimate interest in preventing unauthorised multiple use).
All of this data resides solely on your machine under %AppData% and is
never transmitted to us.
The database is backed up nightly. Backups are end-to-end encrypted and cannot be read on the server itself. They are stored with Hetzner in Germany and deleted after 90 days. If you delete your account, your data disappears from the live systems immediately; it drops out of the backups when that period expires.
You have the right at any time to:
An email to [email protected] is enough. You can also delete your account yourself at any time.
You have the right to lodge a complaint with a data protection supervisory authority. The authority responsible for us is:
Bayerisches Landesamt für Datenschutzaufsicht (BayLDA)
Promenade 18, 91522 Ansbach, Germany
www.lda.bayern.de
We update this policy when our processing changes. The current version is always on this page; the date at the top shows when it was last revised.