A running map can reveal more than distance. Repeated start points, exact times, photos, route frequency, and club information can identify routines. Privacy controls should be chosen before a route becomes public, not added after it spreads.
Protect start and end points
Use route masking around home, work, school, or another sensitive location. Consider starting the public record from a nearby non-sensitive public point. A hidden dot is not enough if the visible route repeatedly ends at the same boundary, so review the whole pattern.
Remove unnecessary context
Check activity titles, photos, captions, precise timestamps, heart rate, calories, and friend tags. Reflections, house numbers, work badges, and location metadata in photos can reveal details the map does not. Share only what supports the intended story.
Choose the correct audience
Private, followers-only, clan, and public visibility serve different purposes. A public territory contribution does not require publishing every personal metric. Runquest separates activity visibility, route masking, and public territory consent so a user can participate without exposing an exact private route.
Audit old activities
Privacy needs change. Review previously shared routes after moving, changing work, joining a club, or changing account visibility. Remove public access when the original reason for sharing no longer applies. Never assume that deleting a social post removes copies already saved elsewhere.
FAQ
Is hiding the first 200 metres always enough?
No fixed distance is universally safe. The surrounding street pattern and repeated activities can still reveal a sensitive point.
Can territory be public while my route is private?
A product can separate aggregated territory from route detail. Verify the specific consent and visibility controls before sharing.