WI.RUN BY KOMARSHWI.RUN / KOMARSH LLC
Your privacy choices
WI.RUN's automatic account-history update is built and its database functions are deployed; signed-in cross-device verification remains outstanding. The choices below describe that update. Account and leaderboard functions are already hosted; email and signed-in hosted journeys still need verification. The same-WI.RUN-account race database update is deployed; signed-in two-device verification remains outstanding. The development social feed still uses its separate account and deletion controls; it is not a hosted WI.RUN social service.
Choose whether to keep precise routes
- Open Settings → Privacy center.
- Leave route retention off to save future run summaries without precise route points.
- If you choose to retain a route when saving, it will be included in your private account history after the automatic-history update is deployed.
- Delete an older run to remove its retained route. Changing the preference alone affects future saves.
Appearance and route-retention preferences will be saved with your WI.RUN account. Private route retention does not publish a post or turn on your race map marker.
Check that your run is saved
Saving a run queues its summary and any explicitly retained route for automatic account upload. The account screen shows pending work and a Retry control. Wait for a confirmed save before relying on a backup; removing the app can erase changes that have not uploaded. Signing in restores the account's saved history when account access and the connection are available.
Older history that is not linked to an account requires an explicit import confirmation naming the destination account. It is not silently assigned to the next person who signs in. Server-confirmed daily points use the account's goal timezone, frozen on the first valid submitted run.
Delete runs or your account
Delete an individual run from its detail screen or use the all-history deletion control to request removal from your account. An offline deletion is pending until the server accepts it; retry errors rather than assuming deletion completed. Deletion markers prevent stale devices from restoring deleted runs. Use the separate discard control for an active or interrupted recording.
The WI.RUN account deletion control requires confirmation and removes the account's owned profile, runs, retained routes, preferences and points. Other runners' shared history remains without your host identity. Signing out or removing the app is not account deletion. Provider logs and backups can have separate retention. Hosted signed-in deletion still needs end-to-end verification.
The separate local-beta account has its own deletion and recovery controls. Own-post management remains available when the daily feed is locked. Deleting your WI.RUN account does not delete this separate beta account. Contact support@komarsh.com if a deletion cannot be completed; do not send a password or recovery code.
Location and media choices
Pause or finish a run to stop GPS recording, or revoke location permission in iOS Settings. Route retention does not control the GPS processing needed to measure an active run.
Configured local-beta map sharing starts hidden. Explicit opt-in can show an approximate marker to race participants; hiding does not hide your distance standings. Publishing a photo or short video is a separate choice. Optional trimmed route artwork appears within the statistics poster and as normalized replay geometry; recognizable images, audio or route shapes can still reveal a location. Friends and Everyone are feed filters, not private-post audiences. Remove a friendship or block a runner in the local-beta community controls. Account history does not publish this media or replay geometry. An explicitly retained precise route in private account history is separate from a publicly shared, trimmed route shape.
Prepared WI.RUN-account racing
The normal app’s small-room racing database update is deployed; signed-in two-device verification remains outstanding. Its map marker starts hidden; opt in separately for each race and choose Hide to stop sharing. Room members still see your handle and distance standings. Rounded latest positions expire from visible snapshots after 15 seconds, but database rows can remain until a later race request cleans them up. A successful hide or leave also removes applicable markers. This is not the same as retaining or deleting a precise route in your private run history.
Comments, mentions, bookmarks and reposts
In the separately configured development community, posting a comment or reply shares its text and your handle. Use @handle only when you intend to mention that runner; mentions can create in-app activity notifications. Delete your own comment from its menu or report another comment. Deleting a parent comment removes its replies. Reporting and blocking affect what you see; they are not a promise that every copy has been removed.
Bookmark saves a private reference for your account; it does not repost or download an unrestricted copy. Repost is an attributed community action and can appear with the original author. Tap the selected bookmark or repost control again to undo it. Daily access and block/deletion controls still apply to saved posts and notification targets. In-app Activity lets you mark events read; read status does not delete the underlying activity. Debug preview actions use fictional data and stay in the preview.
Optional weekly leaderboard
Your account starts hidden from the weekly leaderboard. If you choose Join in the app, signed-in runners can see your handle, display name and weekly points. Your email, biography, run summaries and coordinates are not included. Leave the leaderboard to stop appearing in future requests; this cannot erase information someone already saw. The board excludes blocked runners, shows up to 50 entries and uses self-reported daily points. Signing out does not change your saved visibility choice; use Leave leaderboard before signing out if you want to be hidden.
Website and support requests
This website has no advertising or behavioral analytics controls because those features are not installed. Hosting still processes technical request information. For privacy requests, email support@komarsh.com. Do not send routes or identity documents unless a specific, proportionate verification step is needed and explained.
Read the full privacy policy.