Privacy policy

What this policy covers

This policy covers the ZetRound website, Android phone app and Wear OS app. ZetRound plans running routes, records runs, transfers routes between phone and watch, and can synchronize selected data through cloud services.

Account and authentication

The Android phone app requires a ZetRound account. The website can also be used in guest mode. If you create an account, Supabase processes your email address, authentication credentials and session data. ZetRound can also store a display name and account role. Passwords are handled by Supabase authentication and are not stored in the ZetRound app.

Location, routes and runs

Route generation sends the chosen start location, requested distance and route options to the ZetRound server and OpenRouteService so a route can be calculated. Generated and saved routes can contain precise route geometry, directions, distance and elevation. Recorded runs can contain precise GPS points, timestamps, pace, duration and navigation statistics.

Saved routes, runs and settings are stored locally in browser or app storage. When you are signed in, ZetRound synchronizes those saved routes, runs and settings with Supabase so they are available on your other devices. ZetRound does not request background location permission on the phone. The Wear app uses a visible location foreground service while you are actively tracking a run.

Phone and watch synchronization

Direct phone-to-watch transfer uses Google Play services Data Layer and transfers route geometry, directions and acknowledgements between your paired devices. If direct transfer is unavailable, the cloud fallback stores the latest watch route, its delivery acknowledgement and up to 100 completed watch-run records on the ZetRound server. That data can include route and run GPS coordinates.

Diagnostics and feedback

ZetRound records limited operational diagnostics for route-generation failures and watch delivery failures. These records contain a timestamp, failure code and, when relevant, a route identifier and short technical detail; the diagnostic record does not include an account identifier. Native diagnostic traces remain on the device unless you choose to share them.

If you submit beta feedback, ZetRound stores your account identifier, category, message, page, optional route or run identifier, app version and status in Supabase. Feedback is submitted only when you choose to send it. ZetRound has no advertising or third-party behavioral analytics SDK in the production app.

Optional Strava integration

Connecting Strava is optional. ZetRound requests activity-write access and stores the refresh token in a secure, HTTP-only server cookie. A completed run is sent to Strava only when you explicitly upload it; the upload includes the activity name, GPS track, timestamps and any recorded elevation. Disconnecting Strava revokes the connection and clears the ZetRound cookie.

Service providers and disclosure

ZetRound uses Supabase for authentication and account-linked storage, OpenRouteService for route calculation, Google Play services for paired-device transfer, and the ZetRound hosting provider for serving the app and cloud watch fallback. Strava receives data only when you connect it and request an upload. These services process data under their own terms and privacy policies. ZetRound does not sell personal data or use it for ads.

Retention, choices and deletion

Local data remains until you delete it in ZetRound, clear the website/app storage, or uninstall the app. You can delete individual saved routes and runs in ZetRound and can disconnect Strava at any time. Cloud-synchronized items are deleted through ZetRound and deletion markers can be retained to keep devices synchronized. The cloud watch fallback replaces the previous route and limits its completed-run queue to 100 records.

For complete account or cloud-data deletion, or if you cannot access your account, use the developer contact email published on ZetRound's Google Play listing. Signed-in beta testers can also send a deletion or privacy request through Settings → Beta feedback.

Security and changes

ZetRound uses HTTPS for network traffic, Android release signing, restricted server-side credentials and access controls for account data. No system can guarantee absolute security. This page will be updated when ZetRound's data practices materially change.

Contact

Contact the ZetRound developer using the support email shown in the Google Play listing, or use Settings → Beta feedback while signed in. Include “privacy” or “data deletion” in the request so it can be handled correctly.