WHAT MOTION MIRROR HANDLES
Motion Mirror handles information needed to connect a coach and runner for a live session and preserve a useful coaching record. Depending on how a coach sets up a runner, this can include a runner name or assigned identity; a four-character session code and session identifier; precise location and route coordinates; GPS accuracy, altitude, speed, heading, source, and timestamps; distance, pace, time, mile and coach splits, elevation, run mode and status; connection and delivery diagnostics; saved summaries, weather information, coach notes, receipt notes, and homework; and a coach’s email, display name, password hash, and signed authentication session.
WHY IT IS USED
Live location and run metrics let the selected coach follow an active session. Session identifiers connect the correct runner and coach. Diagnostics help identify missed, duplicate, delayed, foreground, or background updates. Saved summaries and notes support later coaching review. Account information restricts coach dashboard and runner records to the authenticated coach.
WHO CAN SEE IT
During an active session, the connected coach can receive the runner’s live session information. If a run is saved, the coach can review its route, splits, history, summary, and notes. A transparent route graphic may be shared by a runner or coach, but Motion Mirror does not publish it automatically.
INFRASTRUCTURE & MAP SERVICES
The current mobile beta sends session data to Motion Mirror’s hosted application on Render. The application is designed to use PostgreSQL for coach accounts, runner profiles, saved runs, routes, splits, histories, notes, and live-session metadata when a database is configured. The coach interface uses Leaflet with OpenStreetMap street tiles and optional OpenTopoMap terrain tiles. Weather summaries may request data from Open-Meteo. These providers may process technical request information needed to deliver their services.
STORAGE & PROTECTION
Current code supports signed, HTTP-only coach session cookies, password hashes, coach-scoped database queries, and encrypted network transport on the hosted URL. Some development and fallback flows can also use browser local storage. No service can promise perfect security.
TECHNICAL LOGS
Motion Mirror and its hosting providers may create technical logs when a request succeeds or fails. Those logs can include timestamps, request paths, response status, and device or network information used to operate the service and investigate beta problems. The exact production log-retention settings require confirmation.
RETENTION & DELETION
The code does not define a fixed retention period. Saved runner profiles and runs remain until deleted by an authorized coach or until a production retention policy is applied. Active live state may be temporary, while saved routes and summaries can persist in the configured database. Contact support to request access, correction, or deletion; the verified production process and response timeline still require confirmation.
CONSENT & CONTROL
The runner is asked to consent before tracking starts. Tapping Pause or Stop stops active sharing in the normal app flow. A runner can also revoke Motion Mirror’s location access in iPhone Settings, which prevents further location collection. Force-quitting may stop background collection. Revoking consent does not automatically erase information already saved.
CHILDREN
Motion Mirror is not intended for independent use by children. Any use by a minor must be arranged and supervised by a parent or legal guardian together with the runner’s coach.
UPDATES & CONTACT
This policy may change as the beta and production infrastructure develop. Material updates will be reflected by the date above. Questions or requests can be sent to support@motionmirror.run.