WheelHUD privacy policy
This policy covers the WheelHUD mobile app, wheelhud.ru and the connected WheelHUD services. The app displays electric unicycle telemetry, records rides and offers optional account, backup and community features.
Data on your device
Wheel connection settings, Bluetooth device information, speed, PWM, voltage, current, temperature, battery information, ride history and recorded GPS tracks are stored on your device. Heatmaps, route analysis and speed calibration use these records. Recording a local ride does not itself publish the track to the community.
Data leaves the device when you enable a relevant online feature, upload a backup or diagnostic file, publish content, or export and share a file. Enabled automatic cloud backup can upload ride history and settings for eligible accounts.
Technical service session
When the configured app initializes its connection to WheelHUD, it registers a technical session even if you have not created an account. This transmits a generated installation/session identifier, device model and platform, app version and build number; the service also processes the network IP address. These support session operation, compatibility and protection against abuse. This technical connection does not itself upload your local ride history or GPS track, and does not make your profile public.
Account and connected features
- Account: email, display name, username, profile image, Google or Telegram identity, login sessions, device/app metadata and security credentials. These support login, profile display, account protection and recovery. Passwords are stored as hashes, not as plaintext.
- Connected wheel models: while signed into an account, the app automatically sends the manufacturer and model of a connected real wheel for compatibility support. This record does not include Bluetooth addresses, serial numbers or coordinates. Administrators can see the models and when the service first and most recently received each model. These are not exact connection times or a complete past connection history; identical models are combined. Records remain until account deletion.
- Location sharing: coordinates, accuracy, timestamps and optional speed/battery values are sent when sharing is enabled. Visibility depends on your sharing settings and the chosen feature. Friends, nearby riders or group participants may see shared information. Telegram group locations can be imported when the WheelHUD bot is used.
- Cloud backup and sync: selected ride records, GPS tracks, settings and ride metadata are transmitted for the features you use. A backup may contain more information than a ride summary; review the upload feature before sending it.
- Diagnostics: files uploaded for support can include wheel telemetry, protocol packets, device/app information, location information, event logs and comments. These are used to investigate issues. Check the file contents before sharing and do not upload a file containing information you do not wish to send.
- Community: profiles, friendships, group rides, pings/reactions, published dashboard layouts and complaints are processed to provide and moderate these features. Public content can be viewed or copied by other users.
- Battery statistics: account-associated samples are transmitted when the corresponding data-sharing feature is enabled.
- Acceleration leaderboard: only when you choose to publish, wheel/GPS speed samples, timestamps, quality values, wheel model and limited measurement context are uploaded for server recalculation and GPS consistency checks. The public record contains your profile name and rider identifier, reported model, result, limitations and speed curves with relative times; it does not contain coordinates, Bluetooth addresses or serial numbers. Original evidence stays private to service operations and remains until you delete the publication or account. These checks do not certify sensor authenticity or timing precision. Infrastructure backup retention and deletion replay follow the rules below.
- Notifications: a Firebase messaging token, platform, language and notification settings enable push delivery. Account sessions also use a generated device identifier and app/device metadata.
- Voice: microphone audio is transmitted during calls. Signaling uses the WheelHUD server; media can travel directly between participants or through a configured TURN relay. Network addresses and connection metadata are used to establish the call.
Permissions and background operation
Bluetooth permissions connect to wheels and accessories. Location permissions support GPS recording and selected sharing features, including while the screen is off when you start background recording/sharing. Microphone access supports voice calls. Notifications show ongoing activity and selected alerts. You can change permissions in Android settings, stop recording/sharing and disable optional online features. Denying a permission can make the related feature unavailable.
Service providers and other recipients
WheelHUD uses hosting and backup infrastructure including Selectel and Yandex Disk; Google services for optional Google login and Firebase push; Telegram for optional login, bots and group features; RuSender for verification and recovery emails; and Cloudflare for configured relay/monitor services. Map requests use OpenStreetMap tiles and, where configured, Geoapify or MapTiler previews. Map providers receive network metadata and requested map areas. Voice connection providers depend on the configured STUN/TURN service.
Providers process the information needed for their function, such as email delivery addresses or push tokens. Some providers and call participants may process information outside your country. A Google or Telegram account has its own provider privacy policy. Exporting a file or publishing/sharing information makes it available to recipients you choose. We do not sell personal data or use it for advertising profiles.
Storage, retention and security
Active account data and uploaded cloud backups remain until removed through the applicable feature or account deletion. Uploaded diagnostics expire after 14 days. Shared app location and its retained activity are removed when sharing is stopped. The service has short-lived presence/location data and a separate retention window of up to 30 days for ended Telegram shares accessible to administrators. If the operator enables activity collection, voluntarily shared app and active-group Telegram locations also contribute to an administrator-only activity map for service operations. Activity is stored as coarse map cells (50 projected metres) and one-minute buckets for up to 30 days; exact trails are not retained in this collection. The map covers retained sharing observations, not all rides or unique rider counts. Deactivating a Telegram group or membership removes its activity; account deletion removes related app and linked Telegram activity. Voice signaling is temporary. Service requests also process network metadata for security, rate limits and operations; APK download statistics use ticket digests and timestamps. Short-lived anti-abuse counters may remain for up to 24 hours after account deletion.
Transport to WheelHUD services uses HTTPS. Cloud account backups are not presented as end-to-end encrypted: server administrators can access the stored data when needed for service operation. Infrastructure backups use encrypted storage and restricted access. Cloud infrastructure backups retain recent, daily, weekly and up to 12 monthly snapshots; database dumps on the server are retained for 14 days. Separate encrypted recovery copies on the operator's computer currently have no automatic expiry and remain until the operator removes them.
After account deletion, older cloud snapshots and server database dumps expire under those schedules; separate computer recovery copies may remain until manually removed. None of these copies is used as active accounts. Before restored data can be served, deletion records must be replayed; restoration is blocked when the completeness of the deletion journal cannot be established. A minimal deletion journal is retained without automatic expiry to prevent deleted records being restored; it contains technical identifiers and credential/identity hashes, not account names, emails or original credentials. It is restricted to deletion and recovery operations.
Your choices and deletion
You can edit your profile, stop sharing, change notification settings, export local records and request account deletion in the app or at the account deletion page. We verify ownership before deletion. Deletion removes the account and associated active server data and revokes access. Uploaded backups and diagnostics are removed; group rides and published content you own are also removed. The confirmation screen explains the scope.
Local ride history is kept on your device unless you separately delete it. Account deletion cannot retract copies that another person already downloaded or data held independently by Google, Telegram or recipients of your exports. Contact wheelhud@gmail.com for questions about access, correction, deletion or handling of your data.