BikeX Privacy Policy

1. Sign in with Apple is required to enter the main app. Authentication transmits an Apple identity token, an installation device public key, and a random device identifier to sign in and verify device access.

2. When Apple supplies a name, it may be used as your nickname; you can edit it. An avatar uploads only after you select a photo. Profile information, member numbers, rides, and routes are linked through your account.

3. Profile information is stored privately, but public routes, recent riders, and group features may display associated identity information under the boundaries below.

1. A signed-in account synchronizes ride summaries including date, total/moving duration, distance, average/maximum speed, and ascent, together with goals and profile nickname/avatar. After sign-in, rides can be saved locally and synchronize when networking is available.

2. An ordinary ride summary does not automatically back up full raw GPS frames, original or generated videos, audio, weight, or calories. Explicitly saved routes, event-linked group replay samples, and precise GPS endpoints when product analytics is enabled upload under their separate scopes; this is not a promise that all location data stays on device.

3. Recording, dashboard compositing, and manual video creation run on device; exports and system sharing are initiated by you. AI highlight selection and automatic reels have been removed. Ordinary recording and manual video creation remain available.

1. Routes you explicitly save synchronize privately with your account, including GPX geometry/latitude and longitude, route name, waypoints, directions, and associated route metadata so saved routes can be restored. This is separate from ride-summary synchronization.

2. Publishing a route is an explicit optional action and is off by default. Saving privately is not publication.

3. Maps, place search, route planning, and place-name lookup may call Apple map or system services, governed by their applicable rules. Finding nearby group events sends the query location to the BikeX service.

1. Inspect the public preview before publication. The public route snapshot removes points/waypoints within 100 meters of the recorded start or finish; the remaining geometry, route name, waypoints, and author nickname/member number can still identify places or people. This is not an anonymity guarantee for all location processing.

2. Other users can access public routes. Normal route actions cannot unpublish or rewrite an already-published snapshot; deleting a local or private route does not delete the public copy. Account deletion removes author identity, but the published route may remain as an unattributed community route.

3. Selecting a public route for a qualifying ride and synchronizing that ride can display your nickname, member number, and chosen avatar among its recent riders. This does not have an additional opt-in sharing switch.

1. After joining a group, an event-linked ride uploads up to about 120 real WGS-84 latitude/longitude coordinates and relative times after its summary synchronizes. These are recorded replay samples, not live location streaming. Unrelated ordinary rides do not upload this group trace.

2. Joining a public event makes your name and recorded GPS replay for that event visible to other signed-in BikeX users, not only group members. Password-event replay is members-only. Sharing is part of Join, without a second privacy toggle.

3. Group uploads do not first apply the public-route 100-meter start/end trim. Public-route previews or share-poster protection must not be treated as protection of the original group samples. Event status expires within at most 24 hours; that is not a 24-hour track-deletion promise.

4. Deleting a cloud ride deletes its group track. Deleting an account removes its memberships and tracks, and events it organized. Public route snapshots have different retention boundaries from group tracks.

1. PostHog initializes only after you separately enable product analytics. Declining does not limit features, and you can disable it in Settings. Your existing analytics choice continues to apply when upgrading to 1.5.4, without another confirmation page. Events from before opt-in are not replayed; disabling analytics does not automatically delete previously stored events.

2. Analytics uses a random installation identifier and is not bound to your BikeX account. It sends manually defined product interactions, broad distance/duration buckets, app version/build and language, and legacy subscription entitlement status where applicable with associated purchase/restore interactions. It does not include bank-card or payment details.

3. Starting with 1.5.4, opted-in events also include source IP and approximate geography derived from it; device model and type, OS version, screen dimensions, Wi-Fi/cellular status, and time zone. IP geography describes a network-exit location, which can be affected by VPNs or carrier routing; it is not a verified ride location. User-assigned device names, Wi-Fi SSIDs, and advertising identifiers are not collected.

4. Starting with 1.5.4, ride analytics also sends the first and last valid GPS latitude/longitude samples actually written into the ride, their recording times and horizontal accuracy, the final-sample age at ride stop, and country, first-level region, and city when available. The final recorded sample may precede the physical stopping point. Apple system services resolve the administrative areas; a lookup failure does not invent locations or alter valid recorded coordinates. Earlier versions may have different analytics fields, and historical locations are not backfilled.

5. Precise endpoints can reveal home or work locations. The 30-meter endpoint protection on shared images/videos does not mask coordinates sent for analytics; enabling analytics is not public route publication. Analytics does not upload the full route, route names, weight, calories, health data, photos, video, or audio. Autocapture, session replay, surveys, advertising, and cross-app tracking are not enabled.

6. PostHog uses its United States service to process connection IPs, events, and approximate IP geography. IP-based geographic enrichment is distinct from recorded ride GPS locations. Optional analytics may be processed outside your location.

1. Firebase/Google Analytics and Firebase Crashlytics share the optional analytics choice above. They supplement PostHog and are not linked to your BikeX account. When enabled, Google Analytics receives separately filtered product events, broad ride distance/duration buckets, automatic session and engagement events, app/device/OS information, and random installation identifiers; it may derive approximate geography from network requests. BikeX uses FirebaseAnalyticsCore without advertising-identifier collection: no IDFA or IDFV collection, ad attribution, personalized advertising, or cross-app tracking. BikeX does not forward PostHog GPS endpoints, administrative regions, or ride-session identifiers to Firebase.

2. Firebase Crashlytics detects and diagnoses crashes. Reports include the crash reason and stack, occurrence time, app version/build, device/OS and installation diagnostics, and filtered analytics breadcrumbs. BikeX does not actively attach account identity, raw routes/coordinates, health data, weight/calories, photos/video/audio, or local log files to either Firebase service. The crash SDK can initialize and record reports locally; this does not authorize upload without consent.

3. Crash reports are handled on the next launch and authorized for sending only when both the previous execution and current diagnostics choices permit it. A declined or disabled choice requests deletion of pending reports; later opt-in does not replay reports from a declined execution. Disabling also stops Google Analytics collection and resets its local analytics data, but cannot recall an already-authorized in-flight report or automatically erase historical server data. This choice never limits riding, account, or feedback functionality.

1. Starting with 1.5.4, feedback and replies are available only in Settings after sign-in. This is BikeX’s access rule, not a login rule added by the shared support SDK; feedback does not require analytics consent. Only an active submission sends the subject, message, follow-up messages, optional email, app version/build, platform, OS version, language, and necessary Apple App Attest verification and conversation-access materials.

2. Feedback does not automatically attach BikeX account identity or login credentials, rides, routes, coordinates, weight, health data, photos/videos, audio, or logs. If you type these details into a message, the support service receives that text; avoid unnecessary sensitive information.

3. XUNOVA operates a separate support service to answer and investigate requests, not for marketing, advertising, or binding product-analytics identity. Support text and an optional email may identify you and are not necessarily anonymous.

4. Unsent drafts stay only in the current Settings page owner’s memory; recovery after sign-out or restarting the app is not guaranteed. Submitted-conversation credentials stay in this device’s Keychain, not account cloud sync; recovery after reinstalling or changing devices is not guaranteed. After sign-in, replies are viewed in the feedback section on the same device, without automatic email or push notifications. Signing out or deleting a BikeX account does not automatically delete support conversations.

1. Camera and microphone support your chosen video/audio recording; recording video is not required for a ride. Location powers speed, distance, grade, routes, and nearby-event queries, with separate location uploads when saving routes, joining groups, or enabling product analytics as described above. Photo Library Add saves exported videos; avatar selection sends only the photo you choose.

2. Account/route diagnostic logs stay on device and may contain ride summaries, route points, names, and request/response information. Feedback does not automatically upload them. They leave the device only when you deliberately share the diagnostic logs; review their content first.

1. Use the app’s ride, route, and account deletion actions as applicable. Account deletion clears private account/profile data, cloud rides, and private routes, and handles the group memberships/tracks described above. Public route copies may remain after author identity is removed.

2. Signing out removes this account’s local records and app videos. Full raw GPS and video cannot be restored from cloud summaries alone. Copies already exported to system Photos are not deleted with app records; preserve media you need before signing out.

3. Disabling analytics does not erase historical analytics, and sign-out/account deletion does not automatically erase support conversations. Contact info@xunova.tech for access, correction, or deletion requests with the account or conversation reference needed to locate them; do not send identity tokens, passwords, or private keys. This policy does not promise an unverified fixed retention period or automatic deletion deadline.