Privacy Policy

Version 7 · Map-provider supplement October 29, 2026 · TianDiTu permission v1 / Global map disclosure v3

Shanghai Fun Pizza Software Technology Co., Ltd. operates Sport Master, an Android fitness and AI coach app. This page covers the current Android release, including its overseas distribution; it does not announce an iPhone or Apple Watch release. This policy explains what data we collect, how we use it, which processors receive it, and how you can exercise your rights. AI-generated content is for training reference only and is not medical advice.

1. Data We Collect

DataWhenPurpose
Phone numberSMS loginAccount authentication and abuse prevention
Other onboarding and profile data: adult age, gender or prefer-not-to-say, longest recent run, training goal, coach style, primary running mode, nickname, height, weight, max heart rate, and injuriesWhen you submit onboarding or edit your profile. Adult age and the initial training profile are required for an account; expanded profile fields are optional.Confirm adult eligibility, establish your training profile, personalize plans, calculate heart-rate zones and calorie estimates, and provide safer coaching
GPS route, distance, pace, altitude, duration, sport, and activity notesDuring an outdoor activity you actively start, including while the app is in the background or the phone is locked, using an active-workout foreground service. Location is not required for indoor trainer riding; Android 9–11 may require location permission to discover Bluetooth devices.Activity history, summaries, maps, and optional coaching. For a signed-in Android account, complete route points are uploaded and stored by our Shanghai backend. Imported or hand-drawn routes may also be stored under your account when you explicitly save or upload them. Permission to record is not permission to publish a route.
Heart rate, cadence, steps, speed, power, distance, duration, and supported device metricsWhen you connect a compatible Bluetooth heart-rate sensor, smart ring, Garmin watch, or indoor trainer, or use phone sensors. Availability depends on the device, firmware, protocol, and your permissions.Live phone/glasses display, activity recording and fitness summaries. Indoor trainer discovery reads nearby device names and Bluetooth addresses locally; the selected trainer address is stored in account-isolated local settings. Resistance, target-power and simulation commands are sent locally over Android Bluetooth, not through an AIUI app or a Wahoo cloud account. Indoor sessions do not create an outdoor GPS track.
Coach text and actively requested voice inputWhen you ask the AI coach a questionPhone microphone input is transcribed by the selected system speech provider and the app sends the resulting text. If you explicitly select the Rokid glasses microphone and confirm audio sharing, a WAV recording of at most 8 seconds is sent through our server to Tencent Cloud ASR in Shanghai for transcription. We do not persist or log that audio. The transcript can then enter coach chat and its separately permitted memory flow. There is no continuous background microphone capture.
Coach schedule answers: goal, weekly frequency and duration, unavailable days, injuries, race details, and refinement textWhen you choose to create or revise a scheduleOur Shanghai backend combines your trusted running history with server rules and safety checks. Drafts and revisions are stored under your account and can be deleted separately; an adopted weekly plan remains a separate record.
Nutrition photo and extracted meal textOnly when you choose the photo recognition featureFood recognition and nutrition logging. We do not store the original photo; the new Android app previews the result and stores a meal only after your confirmation or edits. Manual entry requires no AI call. Older app submission endpoints remain compatible.
GPX route files, run notes, and other content you actively submitWhen you import a route, save a run, send feedback, or complete a training profileAccount routes, run history, support, and personalization
App events, device model, OS/app version, crash stack, run-quality diagnostics, and server logsUse of the app and backend; uploaded only for signed-in accounts, optional usage analytics separately require opt-in; guests do not queue analytics eventsSecurity, debugging, service reliability, and aggregate product analytics
Server-issued AI-glasses installation ID, long-lived opaque device credential, 8-character AIUI ID, and binding state (the device SN is neither read nor uploaded)On first registration the server issues an installation_id and signed device_credential. The glasses use them for later identity refresh only after a verified local write; the server separately assigns a cryptographically random AIUI ID.Anonymous use before phone binding, offline retry, de-duplication, abuse prevention, and optional account binding when a signed-in app submits the current AIUI ID

AI glasses identity and optional binding: The normal SmartRun AIUI registration flow does not read, simulate, hash, or upload the device SN, and the glasses do not generate an authentication secret. On first registration the server issues an installation_id and a signed, long-lived opaque device_credential. The glasses use that pair for low-privilege identity refresh only after a verified local write. The server separately assigns a cryptographically random current 8-character AIUI ID. That ID locates an unbound device but cannot authenticate the device or read data by itself. Binding requires a signed-in companion app, and a device that is already bound cannot be claimed by another account. Before binding, run summaries and coach memory belong to the glasses' anonymous identity. After binding, that anonymous history moves into your account. Unbinding requires verification of the current ID, changes the glasses to a fresh anonymous owner, and immediately generates a new AIUI ID so the former ID no longer works; prior history remains in the former account.

Release scope: This Android release does not read Apple Health or provide an Apple Watch app. Do not infer iPhone or Apple Watch support from older product material. Cadence and other measurements are shown only when supported by an actual sensor or clearly identified derivation; missing values are not invented.

Garmin Connect IQ: Only after you start a workout on the Garmin watch or in the companion phone app, the watch app accesses the workout data needed for live metrics and activity recording: GPS position, distance, speed, altitude, heart rate, cadence, pressure and Pulse Ox when supported; Garmin profile heart-rate zones, max/resting heart rate and weight; and the latest Body Battery and stress values. During a connected workout, these values and derived coaching metrics are relayed through Garmin Connect Mobile to the Sport Master Android app and, when you are signed in, to our backend for the purposes listed in this policy. In standalone mode the watch app can save the workout to Garmin Connect without our backend. Denying a permission limits the related metric but does not cause background collection before a workout starts. Data you send to Sport Master is submitted to us, not to Garmin; Garmin is not responsible or liable for our processing of that data.

Android routes and weather: Signed-in Android activity summaries and complete route points remain stored by our Shanghai service. New domestic builds adopting this map split use TianDiTu HTTP tiles; the overseas integration candidate uses Google Maps SDK for Android as described below. Older clients retain their actual provider behavior and historical disclosures. The new map split does not silently fall back to Tencent, OpenStreetMap or another online basemap. Missing configuration, network or provider failures produce an unavailable/retry state; your selected imported offline map may remain usable locally. Weather rounding and forwarding to QWeather or Open-Meteo remain unchanged.

Optional Android features and local files

Usage analytics are off by default. A signed-in user can separately enable them in Me → Settings & About → Usage Analytics. Only approved event names, random event IDs, timestamps and bounded mode/step/channel values are accepted. Tokens, phone numbers, precise coordinates, health values, chat and free-form input are excluded. Turning this off immediately clears the local owner queue; server confirmation deletes that owner's analytics events. Offline withdrawal remains pending and cannot silently enable collection again. Consent and queues are isolated by account and are not restored from backups. Necessary security and failure diagnostics remain separate.

Local backups are unencrypted ZIP files saved only to the location you select through the system file picker. Selected domains may contain activity tracks, pending uploads, GPX, roadbook photos, offline maps and local settings, including sensitive location and fitness data. Choose a trusted location; any selected storage provider processes files under its own policy. Restore validates the same owner and API environment (and the same installation for guests), previews the replacement scope and does not restore login credentials, device authorization, paid rights, cloud chat or canonical workout execution rights. Selected local clearing does not delete cloud records or another account. Ordinary sign-out preserves local owner data.

Public sharing requires confirmation. Preview alone creates no public link. A published link reveals the nickname, activity summary and protected track to anyone with the link. Points within 500 metres of either endpoint and segments that could cross that area are removed; short routes may have no visible track. This does not guarantee anonymity. Revocation disables our public page and image, but cannot retrieve copies or screenshots already saved by others.

Manual thresholds and wellness: FTP, threshold pace, wheel circumference, hydration goals and confirmed nutrition values are stored per account. Activity threshold snapshots keep their source and revision; missing measurements are not fabricated. A deleted activity leaves only its owner, upload retry key and deletion time until account deletion, so a restored old queue cannot recreate it. No deleted track or score is retained in that retry marker. Account deletion removes local service records and revokes sessions; third-party cloud deletion is a durable retry and cooling sweep, not an immediate completion guarantee. User-exported files must be deleted by the user.

2. Sensitive Data

Precise location, health and fitness metrics, nutrition photos, and injury or health profile fields may be sensitive. We process them only for the product features you choose. System location permission allows the device to record your own active run; it is not consent to publish or contribute location to a leaderboard, group, or anonymous heatmap. Anonymous location sharing is off by default and starts only after you separately and explicitly enable it in the app. You may deny system permission and use an indoor mode, turn sharing off, delete records, or delete your account.

3. Storage and International Transfers

Our primary website, API and account database are hosted in Tencent Cloud China (Shanghai), at sportmaster.arfunpizza.com. If you use the app outside mainland China, the account data you submit is transferred to China for these services. Singapore remains an auxiliary location for legacy traffic forwarding, some map-service forwarding and recovery copies; it is not a second active account-database writer. Third-party providers may process data in other jurisdictions. We do not claim that selecting an overseas build creates an overseas-only data residency arrangement.

If you separately connect EverMe, memory queries and coach turns are also sent to that service. Its privacy policy says the service is generally provided from Singapore and data may also be processed in other jurisdictions.

Separate third-party AI permission: Before a signed-in user sends the first AI coach message, the app identifies DeepSeek, EverMind, optional EverMe, the data categories and purposes, and offers “Allow and Continue” or “Not Now.” Until permission is recorded, the server does not call these providers or trigger third-party AI for new runs, weekly reports, or plans. The rules_v1 coach schedule draft runs only on our Shanghai backend and does not send its questionnaire or draft to DeepSeek, EverMind, or EverMe; it remains available without third-party AI permission. EverMe additionally requires you to confirm its specific data scope in the app and authorize read, search, and write access to your own EverMe account in the system browser. General AI permission alone does not connect EverMe. You can withdraw general permission under Me → Settings & About → Third-Party AI Data Permission and disconnect EverMe in the devices/platforms screen. Disconnecting stops future access and requests token revocation but does not automatically delete memories already saved by EverMe.

4. AI and Third-Party Processors

ProcessorDataPurpose
DeepSeek (Hangzhou DeepSeek Artificial Intelligence Basic Technology Research Co., Ltd.)The current question and recent chat, selected coach style, and relevant EverMe memory excerpts if you connect EverMe; nickname, sex, height, weight, resting/max heart rate, longest run, 5K result, goals and streak; training/weekly insights including date, distance, pace, heart rate and cadence; daily nutrition and hydration summaries. We do not separately attach phone numbers, login credentials, or raw GPS tracks; information you put in your chat may include them.Only after separate permission: AI plans, post-run reviews, weekly reports, and coach replies
Tencent Cloud ASR (Shanghai)At most 8 seconds of explicitly requested Rokid glasses WAV audioEphemeral voice transcription after general AI permission and explicit audio-sharing confirmation; no stored raw audio in our service
Tencent Cloud TTS (its configured API region is Singapore)Coach speech text without direct identifiersSynthetic voice coaching
Tencent TokenHub / Hunyuan visionNutrition photo provided by youFood and portion recognition
Tencent Cloud SMSPhone numberLogin verification code
EverMind AI / EverOS Cloud (api.evermind.ai)Pseudonymous training summaries (date, distance, pace, heart rate and cadence), AI insights, the user's question, and the AI reply. We do not separately attach phone numbers, names, login credentials, or raw GPS tracks; information you put in your chat may include them.Only after separate permission: long-term AI coach memory and personalized coaching context
EverMe (Evermind AI, Inc.; privacy policy)After you connect your account, memory-context requests and a bounded search-keyword query based on your question; after an eligible successful coach reply, we attempt to save the complete question and answer, which may include training, health or other information you put in the chat or that appears in the answer. We do not separately attach your Sport Master phone number, login credentials, raw GPS tracks, or live sensor stream.Only after general AI permission, separate in-app scope confirmation and your EverMe OAuth authorization: cross-session coach memory. Relevant retrieved excerpts are also sent to DeepSeek to generate a reply. Disconnecting stops future read/write access and requests token revocation, but does not automatically delete memories already stored in EverMe.
Google Play services location, Garmin Connect IQ / Garmin Connect Mobile, and Rokid CXR-L SDKDevice-side location; Garmin workout, profile and sensor metrics described in Section 1; HUD data as neededLocation, watch-to-phone relay and activity recording, and glasses HUD
TianDiTu HTTP tiles (new domestic map split; no TianDiTu Android SDK)IP, tile rows/columns and zoom, ordinary request information and app service identifier; the requested area can correspond to your route/current-position areaBasemap and labels after separate map permission; future requests stop on revocation
Google Maps SDK for Android / Google LLC (overseas candidate, not yet configured/released)The map-view area and metadata, IP, Maps identifier, crash and interaction data described belowMaps after separate v3 acceptance; no native map engine without configuration
Tencent Maps / Tencent Location Services (older or other clients as actually used)IP, requested tile coordinates, and planning endpoints/waypointsHistorical map/routing behavior, not an online fallback in the new map split
OpenStreetMap (older or other clients)IP address and requested map-tile coordinatesDisplay the route basemap
Public OSRM routing service (older or other clients as actually used)Start/loop waypoints and IP when the old client actively requests route planningHistorical routing behavior, not an online fallback in the new map split
QWeatherCity-level coordinates rounded by our backend to about two decimal placesCurrent conditions and short forecast when configured as the primary provider
Open-MeteoCity-level coordinates rounded by our backend to about two decimal placesCurrent conditions and short forecast as the current default or QWeather fallback
System speech-recognition provider (for example, Google Speech)Your voice for transient speech-to-text processing; our backend receives only the transcriptVoice input you actively start

Equivalent protection: Through applicable service agreements and data-processing terms, data minimization, pseudonymous identifiers, and access controls, we require third-party AI providers to protect received data to the same or an equivalent level as this policy and applicable law, and not to use it for advertising, sale, or unrelated purposes. If we cannot confirm that a provider continues to meet this requirement, we stop sending new personal data to it.

Domestic TianDiTu map permission v1 · October 29, 2026

Domestic builds adopting this split request basemap and labels directly from official TianDiTu HTTP tile services, without integrating a TianDiTu Android SDK. The provider, the National Geomatics Center of China, receives your network IP, tile row/column and zoom, ordinary request information and the app's service identifier. Tile requests can reveal the area you view, which may be near a route or your current position. We do not attach your Sport Master phone number, login credentials, health metrics, AI chat or complete activity track. See TianDiTu and its service terms.

Online tile requests require separate map permission for the current local account. You may decline, review the first-map prompt or revoke permission in Settings. Revocation clears the old map and attempts to cancel pending requests; already transmitted requests and information received by the provider cannot be recalled. No permission or configuration means no online TianDiTu tile request. Revocation does not automatically delete activities, route files or your imported offline maps. Provider limits, permitted uses and application review remain governed by the actual platform rules and status; this policy promises neither unlimited free use nor review approval.

Overseas Google map disclosure v3 · October 29, 2026

The overseas integration candidate uses Google Maps SDK for Android. Google processes the map view/camera area, device and SDK metadata, crashes, IP addresses, a Maps-specific pseudonymous identifier and interaction events arising from map-camera calls to provide and improve its services. A viewed area can be near your route or current position. We do not attach Sport Master login credentials, phone number, health metrics or AI chat. Processing also follows the Google Privacy Policy; see the SDK data disclosure. Maps permission is separate from AI, Firebase notifications and EverMe.

Before creating the native map engine, the overseas app requires explicit acceptance for this installation and signed-in account. Earlier overseas v1/v2 or domestic privacy v7 acceptance does not authorize v3. You may decline or revoke map permission in Settings; revocation destroys the old map and removes its displayed content. It cannot recall requests already sent or erase data already received by Google. You may separately accept again to restore an available map. System location permission and active-workout recording remain independent choices.

The overseas Google map integration still awaits actual API, billing, Key configuration and release verification; this disclosure is not an announcement that it is live. Missing configuration, offline or unavailable services show an explanation/retry state and do not silently switch to another online provider. The Android channels share package identity com.funpizza.sportmaster; changing channel does not change account ownership. Map availability, store approval and support in every region are not guaranteed. Google Maps and data-provider attribution remain visible. Shared posters and videos use our own route rendering rather than exporting Google map screenshots.

Bluetooth fitness devices and local control

Connecting a trainer such as Wahoo KICKR ROLLR uses the phone's Android Bluetooth functions. Scanning and connecting require your applicable nearby-device permission; a system pairing request may also appear depending on the device. Only supported and acknowledged controls are available; a connected trainer is not proof that power, heart rate, or control data are present. Some trainer functions need another compatible sensor. Workout metrics and source labels may be saved with the activity and, for signed-in synchronization, uploaded to our backend. A trainer's saved local Bluetooth address is not sent as part of an AI prompt. Standard heart-rate sensors and supported rings transmit actual samples, not an assumed heart rate merely because a connection exists.

Huawei Health Kit and Account Kit: This optional Android integration requires separate in-app consent and official Huawei authorization. Its current device-side page observes supported speed, distance, duration and heart-rate values while visible; it does not create an activity or upload that page's samples. Huawei processes its own authorization and device-service data under its privacy policy. Compatibility and approved package/signing credentials determine availability.

5. Retention

Account and profile data are kept until you delete your account. Run, chat, plan, nutrition, and our AI memory records are kept until you delete the record or account. Coach schedule draft answers and refinements remain until you delete that draft in the app or delete your account; deleting a draft does not delete an already adopted weekly plan. Server logs are kept on a rolling basis for security and debugging. Backups roll off automatically. Disconnecting EverMe or deleting your Sport Master account stops our future access and requests revocation, but does not automatically delete memories already stored in your EverMe account; manage those through EverMe or contact its provider.

6. Your Rights

7. Children

Sport Master currently provides account services only to adults who are 18 years of age or older. Anyone under 18 must not register an account or submit a training profile; the current version does not open minor accounts even with guardian consent. If we learn that an account user is under 18, we will stop providing account services and delete or otherwise handle the related personal information as required by applicable law. The guest demo does not require an account, uses isolated on-device sample content, and must not upload personal, location, or health data.

8. Contact

Operator: Shanghai Fun Pizza Software Technology Co., Ltd.
Support email: 2630281760@qq.com
In-app support: Me → Settings → Contact us.

9. Updates

Material changes, such as new data categories, processors, or cross-border transfers, will be announced in the app and may require renewed consent.

Optional coach system notifications — 17 October 2026 supplement

Firebase Cloud Messaging and Firebase Installations (Google LLC) are enabled only after separate opt-in on the coach system-notification settings page. Google processes installation/registration identifiers and network information such as IP addresses, potentially outside your country. We encrypt the registration token and retain its account association, a hash of a random installation credential, registration generation, login-isolation identifier, and reminder status. Provider messages contain only opaque reminder and binding identifiers, never health data, GPS, phone numbers, coach text or account login tokens. The App checks the current authenticated account online before showing a generic notification, and fetches personal content only after a tap. Turning the feature off, signing out or switching accounts immediately blocks old local notifications and attempts an exact unbind; an offline unbind failure does not restore display. Account deletion deletes our associated records. Devices without usable Google services do not currently have an OEM channel. Provider acceptance is not delivery; network, notification permission and power restrictions can prevent it. In-app care remains available without this feature. See Firebase privacy and security and our SDK list.