Community donation privacy notice
Notice version: donation-v2. Donation is optional. The donation page shows the operator, deletion contact and configured retention period (default: 90 days).
Local analysis does not upload anything. Donation requires a separate selection, browser sanitisation, an unticked consent checkbox and an explicit submission. Only the prepared diagnostic text is sent; the original filename is replaced with donation.txt. The server repeats the same sanitisation independently and stores only its result.
The sanitiser projects recognised diagnostics and retains course/position records after regex and field-based identifier removal. Unrecognised non-course lines are omitted. Course records can contain undetected identifying text, so review the residual risks before donating. It retains relative timestamps, FPS, supported CPU/GPU model families, graphics profiles, resolution, software versions, protocol events and selected numeric errors. It omits unknown non-course text, custom device names, account and user identifiers, names, emails, IP and MAC addresses, UUIDs, serials, device tokens, usernames, home paths, SSIDs, credentials and absolute dates. Zwift GPS, virtual-world coordinates, course/route names and IDs, and position data are retained. Ambiguous GPS in a Zwift log is treated as virtual and retained; expressly real-world, phone/device GPS and home-location records are omitted. Retained route/location patterns may be identifying. Unknown hardware models and event details are deliberately lost.
Automatic detection cannot reliably identify every person or every sensitive pattern. A rare hardware configuration, event sequence or numeric value could permit inference or correlation. Projection also cannot prove that every accepted numeric field is authentic diagnostic data. Do not donate if this residual risk is unacceptable, or if you do not have permission to share the log. Files with unsupported encoding or structure are rejected.
Maintainers retain sanitised diagnostic text and minimal consent metadata: random receipt, submission time, notice version, consent and expiry. They do not store the original log, original filename or IP alongside donations. Storage is private, has no public listing or download endpoint, and is used to improve and test RideScope. Curated examples should receive further review before any publication; donation is not a promise that text will be published.
The service checks configured expiry on startup and hourly; operators must monitor expiry and configure backup retention. Deletion removes active copies; backup copies expire according to the operator's published backup policy. Contact the address shown on the donation page with your receipt to request deletion or withdraw consent. Without the receipt, locating a donation may not be possible. You do not need to provide your original log or identity documents.
The API does not log requests or donation content. Nginx Proxy Manager, hosting infrastructure and security tools may separately log IP addresses, URLs, errors and timestamps. Operators must minimise these logs, disable body logging and publish their retention policies. Traffic stays on this site's origin and server; no external analytics or third-party upload services are used.
Uploads have size, concurrency, rate and total storage limits. A cancellation during transmission may arrive after the server has accepted the donation; keep any receipt and contact the operator if necessary. Cancelling before submission clears the prepared donation without sending it.