Privacy
Privacy Notice
This notice describes the data PaceMaker processes today. It does not describe user accounts, stored training history, marketing trackers, or a backend contact form because those capabilities are not currently implemented.
Controller
Oleksandr Maistrenko
Email: contact@racepacemaker.com
Vienna, Austria · Full address available upon request
Data categories processed today
Race configuration inputs
Race date, target finish time, and preferred distance unit entered in the planner.
GPX uploads and derived route points
Uploaded GPX file content plus the parsed route coordinates, elevation points, and distance data needed to calculate a plan.
Weather lookup inputs
Route coordinates and race date sent to forecast services, plus any manual wind override values entered when automatic weather is unavailable.
Pace-plan and workout export inputs
Generated split data, wind context, and optional workout naming inputs used to produce FIT or TCX exports for the active plan.
Purposes and legal bases
Service delivery
Race planning requests are processed because the runner asks PaceMaker to analyze a route, weather context, and pacing target.
Operational reliability
Minimal technical logging and security processing may occur to keep the hosted service available and diagnose failures.
Optional analytics only with consent
If optional analytics are enabled and you opt in, PaceMaker may process limited product-usage analytics. You can withdraw consent later.
Why the data is used
Generate the requested pacing plan
Planner inputs are combined to compute pacing guidance, charts, map views, and exportable workouts for the current session.
Show route and weather context
Route and forecast inputs are processed so the planner can explain terrain and wind effects that influence the pacing output.
Operate and secure the hosted app
Infrastructure metadata may be processed for availability, abuse prevention, troubleshooting, and observability of the live service.
Recipient and processor categories
Hosting and infrastructure providers
Static frontend hosting, backend hosting, logging, and delivery infrastructure that present and operate the application.
Weather data providers
Forecast providers receive route coordinates and race-date context when PaceMaker requests weather information for a calculation.
Optional analytics provider
If analytics consent is granted, the configured analytics processor receives limited product-usage events rather than raw GPX files or exact race-location data.
Retention and deletion criteria
Session-oriented planning data
PaceMaker currently has no account system or saved race-history library. Planning inputs are intended for the active browser session and short-lived request processing rather than long-term profile storage.
Browser-side persistence
Some preferences such as analytics consent can remain in the browser until the runner clears them or resets the choice.
Operational logs and provider defaults
Technical logs, telemetry, and provider-side request records follow the retention settings of the selected hosts and processors. Review and document those concrete retention windows before launch.
Transfers and review note
Depending on the chosen hosting, weather, or analytics providers, technical processing may involve countries outside the runner’s home jurisdiction. Confirm the providers and their safeguards before launch.
Informational notice only, not legal advice. Review the final notice with the actual launch operator before production.