Privacy Policy

Service provider and contact

Seller / service provider

Püspöki Zsolt

Service / business location

2022 Tahitótfalu, Bólyai János utca 2., Hungary

Support contact

support@wattalo.com

1. Account and authentication data

WorkOS AuthKit provides Wattalo with a verified user identity, email address and optional display name after sign-in through Google or an email one-time code. Wattalo maps that identity to a random opaque Wattalo user ID and stores identity snapshots, login timestamps and an Admin flag.

Wattalo does not persist WorkOS, Google or other upstream access or refresh tokens. A secure, HttpOnly Wattalo authentication cookie uses a 30-day sliding lifetime. Short-lived AuthKit state/correlation and antiforgery cookies support sign-in and protected requests. Server-side Data Protection keys protect authentication state and persist across restarts.

2. Route-planning requests

A planning request sends the chosen origin coordinates, ride time, target power, direction, workout, rider/bike values, planning country, route style and blacklist choices needed to calculate a route.

The current database schema does not store planning requests or generated private route results. Server diagnostics record a request ID, region, processing stage, timings, result category and graph-cache counts; they do not intentionally log exact coordinates, street names, GPX points or account identity.

The graph cache contains reusable map/elevation routing data, not a rider’s request history.

3. TCX ride learning

Climbing-power learning remains local in your browser and may store a derived 20-bin gradient/power profile with planner settings. If you select ETA calibration or anonymous shared learning, the selected TCX XML is sent securely to the Wattalo API for processing.

The API does not persist the raw TCX XML. During processing it temporarily keeps the minimum derived map-matched segment location/time data needed to resolve historical weather. After each segment is resolved or rejected, that detailed segment record is deleted. Wattalo retains ride-level processing metadata, derived calibration observations for personal ETA learning, and compact calibration factors.

Anonymous shared learning is a separate opt-in. Shared contributions are copied into an aggregate-learning sample table without account, ride, position or timestamp identifiers. Personal observations remain linked to your account only when personal ETA calibration is selected.

4. Shared routes

Creating a share stores a random 128-bit public share ID, creation/expiry timestamps, route geometry, distance, estimated duration, target power and optional direction. It does not store the sharing account ID, rider profile, IP address or full planning request with the share.

Anyone who has the unguessable link can open the shared route. The configured lifetime is currently 30 days; expired records are removed by bounded periodic cleanup.

5. Billing data

When billing is enabled, Paddle receives the customer, checkout, payment and subscription information needed to provide hosted billing. Wattalo does not receive or store raw payment-card details.

Wattalo stores only linkage and entitlement records such as Paddle customer ID, subscription ID, status, event timestamps, short-lived opaque checkout references and processed webhook event metadata.

6. Planner telemetry, GPX downloads, technical logs and browser storage

When explicitly enabled after a privacy review, server-side analytics may additionally record an approximate US state (or an unknown-state marker) derived from Cloudflare visitor geolocation. The selected planning country is not treated as the visitor location. No IP address, city, precise location or route position is included in this additional analytics property.

Wattalo records a small first-party planner funnel in a separate telemetry database: planner opened, controls changed, Generate clicked, planning started, coarse planning outcome, and GPX downloaded. Events may include random installation/session identifiers, the opaque Wattalo user ID when signed in, planning country, app version and a coarse outcome code. They do not include email, display name, precise coordinates, searched address text, route geometry, GPX content or detailed rider-profile values.

A GPX download is created locally in the browser from the already returned route; the GPX file is not uploaded again. The download event reuses the same first-party funnel telemetry and contains only the small metadata described above.

Application diagnostics record technical service information such as request ID, planning region, processing stage, elapsed time, result category, graph snapshot identity and tile/cache counters. Errors may include an exception together with request ID, region and stage. These diagnostics are used to operate, secure, troubleshoot and improve the service; they do not intentionally include exact route coordinates, street names, GPX points or Wattalo account identity.

Hosting, edge and network providers may also process ordinary access-log or network metadata such as request time, source IP address, requested path, response status and user-agent according to their service configuration. Wattalo uses this technical metadata for security, abuse prevention, availability and incident investigation, not for advertising or cross-site profiling.

Browser local storage holds language and planner preferences, including rider/bike settings, route preferences, blacklists and the optional TCX-derived profile. Cookies are used for authentication, AuthKit sign-in correlation and cross-site request forgery protection. The reviewed PWA contains no advertising or third-party analytics/tracking integration.

7. Purposes, legal bases and service providers

Wattalo processes account, planning, sharing and subscription data as needed to provide the service and take steps requested by the user in connection with the service. Where applicable, this processing relies on performance of a contract or steps taken at the user’s request before entering a contract.

Security, abuse prevention, rate limiting, service diagnostics, limited first-party product-usage telemetry, incident investigation and reliability monitoring are processed on the basis of Wattalo’s legitimate interests in operating and improving a secure and dependable service, with data minimization used to reduce impact on users. Billing or record-keeping data may also be processed where necessary to meet applicable legal obligations.

WorkOS provides AuthKit Hosted UI and identity management for authentication; Google may act as the upstream social sign-in provider when that option is chosen. WorkOS receives the identity and authentication data needed to operate those flows. Paddle acts as the hosted billing provider and Merchant of Record when billing is used. OVHcloud hosts the production VPS and provider-level backups. Cloudflare provides the Tunnel/edge path and private R2 application-backup storage. These providers receive only the information needed for their respective service roles and may process technical network metadata under their own applicable terms and privacy notices.

8. Retention, backups and your rights

Shared routes currently expire after 30 days and the authentication cookie uses a 30-day sliding lifetime. Raw planner-funnel telemetry is automatically expired after 60 days; compact daily funnel aggregates are retained for approximately one year. Private application backups containing the core SQLite database and Data Protection keys are configured for approximately 14-day retention in Cloudflare R2; the separate telemetry database is not part of that application-level archive. Provider-level VPS backups follow the provider configuration. Operational and access-log retention follows host/provider configuration and the time reasonably needed for security, troubleshooting and service operation.

Account, entitlement and billing-linkage records are retained while needed to provide the account or subscription and for applicable security, dispute, accounting or legal requirements. Retention may therefore differ by record type, and data may remain temporarily in protected backups until those backups expire.

Depending on applicable law, you may request access, correction, deletion, restriction or portability of personal data, and you may object to processing based on legitimate interests. Rights are not absolute where a legal, security or other permitted retention ground applies. You may also lodge a complaint with the competent data-protection supervisory authority.

You can remove locally stored preferences through browser site-data controls and stop sharing a route link. Send privacy-rights requests or questions to support@wattalo.com.