Privacy Policy

RunMate is operated by MMIX Lab. Contact: reona.murakami0731@gmail.com.

Data we process

We process account email, nickname, age category, profile, running pace, GPS run routes and statistics, optional private weight and meal logs, read-only treadmill speed and incline, messages, reports, blocks, profile photos if uploaded, and access logs needed for security. Google Identity Platform handles passwords and verification email; we do not store plain-text passwords.

Use and sharing

We use data for account operation, personal run records, optional online running, moderation, and support. Weight, meal logs, and private GPS records are not automatically shown to other runners. Routes explicitly published or shared by the user are visible to the selected audience. An opt-in public profile may be seen by other users. Activity areas and actual live positions are not displayed. Accepted contacts can see messages and shared online run progress. Live location sharing is not provided, including between mutual followers or during chats, meetups, and runs. Recommendations and their points/photos are published to followers only after the author consents. Explicitly published or shared courses reveal the selected route; do not include a home or workplace. Saving a plan with invited contacts sends invitations; acceptance adds the confirmed plan to both calendars. Feature availability depends on the build, age category, and operating configuration. Calls attempt peer-to-peer connections, with signaling relayed by the server, and may fail on some networks.

Maps and route planning

Map views request tiles from OpenStreetMap, which may receive your IP address and the map area being viewed. If you choose “Snap to walkable roads,” the start, finish, and intermediate coordinates you selected are sent to the external FOSSGIS routing service to retrieve a route. Do not select the exact location of your home or workplace. Saving a route alone keeps it private; publishing or sharing is a separate explicit operation.

Storage and deletion

We use Google Cloud services including Firestore, Cloud Run, Cloud Storage, and Google Identity Platform. Google may process data outside Japan. Data is retained while the account is active. In-app account deletion removes associated active account, run, weight, meal, and social data. See external deletion instructions. Limited safety or legal records and short-term backups may remain as needed; recovery backups, if retained, expire under their retention policy. Store records are handled separately.

Contact

For access, correction, deletion, or questions, email reona.murakami0731@gmail.com.

Interaction and visibility

World discovery lists opt-in runner profiles, without activity-area or live-position matching. Messaging requires acceptance. Existing under-18 social protections, reporting, blocking and content checks remain. In-person age/gender matching conditions do not apply to solo course browsing or creation.

Map delivery

Multilingual maps use OpenFreeMap, OpenMapTiles, and OpenStreetMap. Requests for the visible map area may disclose your IP address to the map providers.

Health and AI

Permitted Apple Health heart-rate data is read only on supported iOS devices, is not sent to our server or other runners, and is not used for advertising. Manually entered weight and meal records are saved privately to our API. Public-build AI uses compatible on-device models; iOS requires supported Apple Intelligence / Foundation Models hardware, OS, language, and settings. Prompts and model photo inputs are not sent to a developer-operated cloud AI. Account tokens and task types are sent for access checks. Plans and routes saved from suggestions go to the normal API. Photo analysis depends on device support. Development-only PC AI proxies and virtual billing are excluded from public releases.

Usage and purchases

Onboarding steps, active days, run-save dates, acquisition source, and optional satisfaction feedback are used to improve usability and measure continued use. We do not perform cross-app advertising tracking. iOS purchases use Apple App Store / StoreKit; Android uses Google Play Billing when enabled. We process store transaction identifiers, product, expiry, and purchase-account associations. The store processes payments; we do not receive card details. Google and Apple sign-in use Google Identity Platform / Firebase Authentication.

Communications and deletion

WebRTC peers and STUN connection services may receive device IP addresses. Account deletion removes bug reports and attached images and removes the deleted account from other users’ participation details, while preserving those users’ independent plans.

Voice connection services

Optional voice calls attempt WebRTC peer-to-peer connections. The default configuration uses Google STUN (stun.l.google.com) to discover connection paths, exposing device IP addresses and connection information to Google. STUN does not relay the call audio. If the operator configures TURN, that provider may relay audio traffic when needed and process IP addresses and connection information. Providers and retention depend on the deployed settings. Connection signaling is relayed through our API and can reveal IP addresses in those signals to our server and the call participant. Starting a call requires microphone permission. These connection details are separate from GPS live-location sharing, which is not provided.

Course rankings

For new accounts informed on the registration screen, completing a public course automatically displays rank, nickname, permitted profile icon and finish time. Rankings do not show live location, individual GPS tracks or health information such as weight and meals. Icons do not open profiles or messages. Settings → App → Ranking privacy lets you change record or icon visibility. Hiding removes ranking entries while retaining your own run history. Existing accounts’ privacy choices are not changed automatically.

Optional external account linkage

When you choose to link an account, official X, YouTube Data API or TikTok authorization provides account identifiers, display names, ownership confirmation time and available public audience counts. YouTube subscribers are provider-rounded public values; hidden or unavailable counts are not estimated. Account ownership is not government identity verification. Community publication requires your explicit choice, and changing the linked account requires confirmation again. TikTok private open_id is not published.

Authorization tokens are not retained. YouTube information expires after 29 days and stored copies are removed within 30 days. Reconfirmation requires your action. Delete linkage data from the leader page to remove the information stored by Vran. This does not delete an external account or revoke its permissions. Revoke Google access through Google permissions settings. See Google official linked-app management and Google Privacy Policy. Availability depends on operator API configuration and approved scopes.

RunMate product scope

RunMate lets your avatar run virtual world courses with friends. It does not offer physical meetup recruitment, nearby-person position search, actual live-location sharing, document/selfie verification for meetings, or phonebook matching. GPS virtual runs convert actual coordinates to distance on the device and send distance, speed and elapsed time for the virtual course. Personal outdoor run records and deliberately published route geometry are separate. Prior physical invitations are retired and never reused as consent to a virtual run.