Privacy

This page describes what actually happens when you open PaceScope. It is written in two parts on purpose: what is running today, and the analytics and advertising that will be added at launch, disclosed here before they exist. Every claim about today's behaviour can be checked against this repository; the planned part is written now so that nothing ships before it is disclosed.

The short version

No accounts, no sign-in, no user data. There is nothing to store because there is nothing to identify you with.
Your inputs are not sent anywhere except into the address you asked for. The calculator works out the answer in your browser when JavaScript is on, and on the server when it is off.
Today: no cookies, no browser storage, no analytics, no advertising and no third-party scripts at all. The site sets no cookie and reads no localStorage or sessionStorage.
At launch: Google Analytics 4 and Google AdSense will be added, together with Google's consent management platform (the one that ships with AdSense). They set cookies, they are third-party code, and the section below describes exactly what they do. Ads are what pay for the site; they are not a reason to avoid saying so.

What the server records

A server has to record something to stay up. With each request the application writes one access-log line with:

Field	Example	Why
`method`	`GET`	which kind of request it was
`uri`	`/de/tools/pace-calculator?d=marathon&t=3:00:00`	what was asked for — including the query string
`status`	`200`	whether it worked
`latency`	`1.2ms`	how long it took
`remote_ip`	`203.0.113.7`	the client address, needed to diagnose abuse and routing faults
`request_id`	`3f2c…`	a random per-request id, so one request can be found in the logs

Two consequences worth stating plainly:

A result you type into the calculator appears in the address bar, and the address bar is logged. That is inherent to how the site works: the result is the address, which is what makes it shareable. If you would rather a specific time did not appear in a server log, do the calculation with JavaScript enabled and do not reload the page — nothing is sent.
Your IP address is in the log. The site does not use it for anything except operating the service; it is not combined with any other data, and it is not joined to the analytics described below.

The logs are kept for a short operational window (14 days by default, rotated by the system; see the deployment manual in this repository) and are not shared or sold.

Analytics and advertising

This is the part most privacy pages bury. Here it is in full.

Who. Google Analytics 4 for usage measurement, and Google AdSense for advertising. Both are operated by Google. Consent is collected and enforced by Google's consent management platform (the Privacy & Messaging / Funding Choices solution that ships with AdSense, built on IAB TCF v2.2).

Why. Analytics answers which pages are useful and where the site is broken — without it, changes are guesses. Advertising covers the cost of running the site. Neither is used to build a profile of you across other services by us: we have no user database to attach anything to.

What they set. Google Analytics writes first-party cookies named _ga and _ga_<container-id>; Google's advertising products write cookies whose names include __gads and __gpi (the exact set can change — Google's own documentation is authoritative). Advertising requests also send your IP address and a user-agent string to Google, as any ad request does.

Consent. In regions that require it (the EEA, the UK and Switzerland at the time of writing), the consent platform shows a message before any non-essential cookie is written, and you can accept or refuse:

Refuse — Google does not use cookies for ad personalisation. Ads may still be shown in a non-personalised form, and the cookies used for that are limited to frequency capping and abuse prevention. Analytics runs in a consent-mode form that does not write its cookies.
Accept — the cookies above are written and ads may be personalised.
Change your mind at any time — the consent message can be reopened from the privacy link in the ad area, and your choice is remembered. Independently of this site, you can also use Google's ad settings or Google's Analytics opt-out browser add-on.

Retention. Google Analytics event data is retained for 14 months by default (configurable in the Analytics property). Google's own retention for advertising data is described in Google's privacy policy; it is not set by us.

Transfers. The processing happens on Google's infrastructure, which means data may be transferred outside your country (for example to the United States), under the transfer mechanisms Google documents — including the EU–US Data Privacy Framework where it applies.

What we still do not do. We do not sell data, we do not run our own analytics or ad server, we do not add a newsletter, comment system or contact form, and we do not join the access logs above to the analytics data. If a report tells us a page is popular, it does not tell us who read it.

If that ever changes

Anything that collects personal data is described on this page before it goes live, in the same commit as the code. That is the rule this site set for itself: the deployment manual carries the checklist, and the repository history is the audit trail.

Who runs this site

PaceScope. The site itself is the data controller for everything described on this page — there is no separate company behind it, and the address below is how to reach it.

Contact

Questions about this page, or a request concerning data that might relate to you: [email protected]. If your request concerns data held by Google (Analytics or AdSense), it is fastest to use the Google controls linked above — but write to us as well if you are unsure, and we will tell you what this site itself holds.