Data controller/operator: Bon Aleksei Michailovich.
Data-subject contact: support@motohub.app.
This Policy applies to Motohub and explains what data is processed, why, on what basis, with whom it is shared, how long it is retained, and how Users can exercise their rights.
1. Scope and principles
This Policy covers the mobile app, website, APIs, support, social features and related Motohub services. Personal data is processed lawfully, fairly, for specified purposes, with data minimisation, accuracy, retention limits and appropriate security.
2. Data categories
Account data: account identifier, email/login, password hash, authentication tokens, account status and creation date; phone number and verification status when phone verification is used.
Profile and social data: nickname, name, date of birth, gender, biography, avatar and photos, profile colours, contact/social links and linked VK identifier when provided; motorcycle and garage details, friends, follows, blocks, group membership and roles, posts, reactions, comments, reports, achievements and rankings; language, privacy and notification preferences.
Location and trips: current/last known coordinates and online status; route points and timestamps, accuracy, speed, heading, distance, elevation, start/finish, duration, lean angles and other supported sensor-derived statistics, trip photos and visibility choices. Location supports maps, nearby riders and road assistance, route recording and group location sharing. Weather information for the trip may also be saved.
Group location sharing: account and group identifiers, latitude and longitude, nickname and profile colours; speed only when sharing speed is enabled. Background collection is described in section 5.
Health data: heart-rate samples (beats per minute and timestamps) from Google Health Connect on Android or Apple HealthKit on iOS for the selected trip, and calculated minimum, average and maximum heart rate. See section 6 for permissions, saving and visibility.
Communications and support: message text and attachments, sender/recipient and conversation identifiers, timestamps and delivery state; support correspondence, contact details, reports and moderation records.
Local intercom and QR codes: microphone audio while speaking in an intercom room, room/peer identifiers and local-network connection information. Camera access is used to scan a room’s QR code. Audio is transmitted to room participants over the local wireless connection.
Technical data: IP address, device model/vendor, operating system and app version, language, push/installation identifiers, request and service events, crash reports and security logs. Crash diagnostics on Android include an identifier linked to the Motohub account. Operational logs may include service-email delivery details.
Subscription data: Pro status and expiry; for a linked VK Donut subscription, VK user identifier, subscription event and community identifiers, payment amount and amount after fees. Motohub does not receive full bank-card details through this integration.
3. Sources
Data comes from the User, the device and app, Google Health Connect or Apple HealthKit with permission, other Users when they interact or report content, and the service providers listed in section 9. VK Donut supplies subscription events for the linked VK account.
4. Purposes and legal bases
Contract performance: accounts and verification, maps and nearby features, route recording and statistics, group location sharing, social features, chats and local intercom, rankings, support, subscriptions and syncing.
Consent: location access including background access, camera/photos, microphone and local-network access, heart-rate reading and other processing where required. An operating-system permission does not always replace legal consent; separate consent is requested where required.
Legitimate interests where applicable: security, fraud prevention, diagnostics, service improvement, defence of rights and aggregated statistics, subject to balancing the User’s rights and interests.
Legal obligations: lawful authority requests, accounting and applicable retention, restriction and deletion duties. Explicit consent or another legally permitted basis is used for health data where it is a special category of personal data.
5. Background location
Motohub uses background location for two separately controlled features: a trip recording started by the User and location sharing enabled by the User for one or more groups. Either feature can continue while the app is minimised or not on screen, including when the screen is locked, subject to device permissions and operating-system limits.
Trip recording: location and sensor readings are used to build the route and trip statistics. Saved trip data is sent to Motohub for storage and syncing. Other Users’ access depends on the trip’s publication and visibility settings.
Group sharing: while sharing is enabled, coordinates, account/group identifiers, nickname and profile colours are sent periodically to Motohub and relayed to participants with access to that group’s live map. Speed is included only when its separate sharing option is enabled. Group sharing can run without a trip recording; trip privacy settings do not stop group sharing.
Controls: stop trip recording to end that recording; disable location sharing for each selected group or use the control to stop all group sharing. Stopping one feature does not stop the other, and stopping one group does not stop sharing with other selected groups. Minimising the app or locking the screen is not a stop command. Previously enabled group sharing may resume when the service restarts.
Location permission can be withheld or revoked in device settings; this limits or disables the related features. Where the device allows it, background and precise-location access can be controlled separately. Stopping new collection does not delete already saved trips or other previously stored data; deletion is covered in section 12.
6. Google Health Connect and Apple HealthKit
Motohub integrates with Google Health Connect on Android and Apple HealthKit (Apple Health) on iOS. After the heart-rate feature is enabled and system permission is granted, Motohub reads only heart-rate samples for the selected trip period. It does not request diagnoses, medication, sleep, steps or other health categories, and does not write data to Health Connect or HealthKit.
The readings are used to display heart rate alongside trip statistics. When the User saves heart-rate data to a trip, the samples and their timestamps, minimum, average and maximum values, and trip identifier are transmitted to Motohub and stored with that trip. This data is not confined to the device.
Minimum, average and maximum heart rate can be visible to other Users who have access to the trip. The detailed list of saved heart-rate samples in trip details is available to the trip owner. Consider this when saving heart rate to a shared trip or changing a trip’s visibility. Group live-location sharing does not include heart-rate samples.
Health data is used for the User-facing trip and statistics features, not for advertising, marketing profiling, credit, insurance or employment decisions, or sale to data brokers. Motohub does not sell health data or provide it to advertising networks.
Disable the heart-rate feature in Motohub or revoke Motohub’s read permission in Health Connect on Android or Health/Privacy settings on iOS to stop new access. This does not automatically delete readings already saved in Motohub; delete the trip or Account, or contact support for a data-deletion request. Deleting data in Motohub does not delete the original records in Health Connect or Apple Health.
7. Public and social Content
Published profile information, posts, photos and routes are visible to the audience allowed by the relevant feature and visibility settings. Group participants receive the live-location information described in section 5. Saved heart-rate summaries follow the trip visibility described in section 6.
Other Users may capture or redistribute content outside Motohub. The Operator treats public content as personal data where applicable and processes it for service delivery, security, moderation and legal obligations.
8. Chats, intercom and moderation
Messages are stored for delivery, syncing, conversation history, abuse prevention and complaint handling. Access by authorised personnel is limited to support requests, reports, security, technical diagnosis or lawful demands.
Push notifications can contain a sender name, message preview and conversation identifiers. The notification providers in section 9 process that payload for delivery, and notification previews may appear on the device’s lock screen according to its settings.
The local intercom uses microphone audio and local-network/nearby-device access to connect room participants. Voice packets pass to the other participants and, in relay mode, through relay devices in the local network. Motohub does not save this audio as chat history or upload it to the Motohub backend. Mute the microphone or leave the room to stop sending voice; microphone permission can also be revoked in device settings.
9. Recipients and processors
The following services process data when the corresponding feature is used. Access is limited to the data needed for that function; a provider’s own terms also apply to its independent services.
Motohub and authorised personnel: the Operator’s backend, storage and backup infrastructure processes account/profile data, locations, saved trips and heart rate, messages, uploads, support requests, subscription status and technical logs to operate the Service. Personnel access is limited by their support, administration and security duties.
Other Motohub Users: message recipients, group participants and the permitted audience of profile/content/trips receive the information described in sections 5–8. Group location is relayed through Motohub to the relevant group.
Local intercom participants and relay devices: voice packets, room/peer identifiers and connection information needed for local wireless communication. Room participants can hear transmitted audio; relay devices forward packets when that mode is used.
Google Firebase Cloud Messaging and Apple Push Notification service (APNs): push tokens, device/installation and delivery information, notification title/body and routing identifiers; chat notifications can include the sender and message preview. On iOS, Firebase delivers notifications through APNs.
Google Firebase Crashlytics: crash reports, diagnostic events, app/OS/device details and installation identifiers for troubleshooting. Android diagnostics include an identifier linked to the Motohub account.
Yandex Maps: IP address, technical request data and coordinates used for map display and map/geocoding requests. Embedded maps process the routes and rider/group markers displayed on them, including positions and profile labels.
OpenWeather: requested latitude/longitude, language, units, IP address and request metadata for weather and reverse geocoding (place names for coordinates).
Yandex email service: recipient email address, subject and email body, including verification, password-recovery and account-deletion codes, for service-email delivery.
FlashCall: phone number and verification-session identifiers for phone confirmation; Motohub receives verification status from FlashCall.
VK / VK Donut: when the User opens the subscription page, VK processes the User’s interaction and payment under its own terms. VK Donut sends Motohub the linked VK identifier, subscription-event/community identifiers and payment amounts to activate Pro. This integration does not send trip, location or health data to VK.
Google Health Connect and Apple HealthKit: device health-data sources and permission interfaces, as described in section 6. Motohub reads authorised heart rate from them and does not send trip data or write health records back through these integrations.
App stores and external links: Google Play, Apple App Store, RuStore and Huawei AppGallery process visits, downloads and updates under their own terms when the User uses the corresponding store. Opening external links, including VK or Boosty, connects the User to that service. These links do not by themselves grant access to Motohub trips, messages or health data.
Data may also be disclosed to competent authorities when legally required, or to professional advisers where necessary to establish or defend legal claims. Motohub does not sell personal data and does not provide health data to advertising networks.
10. International transfers
The providers in section 9 may process their respective data outside the User’s country. Depending on the feature, this can include coordinates and map requests, notification content, device identifiers and crash diagnostics, rather than only anonymous technical data.
Cross-border transfers must comply with applicable legal grounds, notification or authorisation requirements and safeguards. The Operator must comply with applicable localisation requirements for personal data of Russian citizens, including the use of databases in Russia where required by law. For EEA data, an applicable GDPR Chapter V transfer mechanism is required, such as an adequacy decision or Standard Contractual Clauses where appropriate.
11. Retention
Account/profile: while the Account is active and normally up to 30 days to complete deletion, unless a longer period is legally required.
Routes, photos and trip statistics, including saved heart rate: until the item or Account is deleted; backups normally expire within 90 days.
Group location: live updates are relayed while sharing is enabled. Stopping sharing ends new updates but does not erase the last known position already saved in the profile or separately saved trip data. These are subject to profile/trip deletion and applicable log-retention periods.
Messages: while available to participants or until deletion under the Service’s functionality; complaint evidence may be retained for up to three years or the applicable limitation period.
Technical logs: normally up to 12 months; security and abuse evidence up to three years where necessary.
Subscription and transaction records are retained for statutory accounting and consumer-law periods. After the applicable period, data is deleted, anonymised or restricted pending deletion. A shorter period may apply on request if there is no basis for further retention.
12. Deletion
Users can delete individual routes, photos and posts through the available in-app controls and request Account deletion in-app or by emailing support@motohub.app. Identity verification may be required.
After verification, active data is normally deleted or anonymised within 30 days and backups within a cycle of up to 90 days, subject to legal, security, dispute and accounting exceptions. Revoking health or location permission stops new access but is not a request to delete previously saved data.
Deleting a sender’s copy may not delete a recipient’s copy unless a delete-for-everyone feature is available. Third-party screenshots and redistributions are outside the Operator’s control.
13. User rights
Depending on applicable law, Users may request information, access and a copy of their data, correction, restriction, deletion, objection, withdrawal of consent and portability, and may complain to a supervisory authority or court.
Send requests to support@motohub.app with enough information to verify identity. Responses are provided within the applicable legal deadline; the general target is 30 days. An extension is used only where the law allows it and the User is informed. Withdrawal does not affect earlier lawful processing or processing based on another legal ground.
14. Automated processing
Rankings and recommendations may be generated automatically but are not intended to produce legal or similarly significant effects. Users may challenge a moderation action or obvious ranking error.
15. Security and incidents
Measures include access controls, encrypted connections to the Motohub backend, password hashing, logging, backups, patching, network protection and incident response. Local intercom transport is separate from the backend connection; do not assume that every local wireless mode provides the same protections. No system is completely secure.
Users should protect their device and password. The Operator notifies affected individuals and authorities following an incident where required by law.
16. Children
The Service is for adults aged 18+. The Operator does not knowingly seek children’s data. An underage Account may be suspended and data deleted unless another lawful basis applies.
18. Changes
Material updates will be communicated in-app, on the website or by email. The revised Policy applies from the stated date unless fresh consent is required.
19. Contact and complaints
Data requests: support@motohub.app.
Controller/operator: Bon Aleksei Michailovich.
Users may also complain to Roskomnadzor, their local data protection authority or a competent court.