Running privacy has several layers: who can see the activity, what the map reveals, who receives live links and which connected apps can read the data. Changing one setting may leave the others unchanged.
Review activity and map visibility separately
Strava provides activity privacy controls and map-visibility controls. Its documentation also explains that permission to read private activities can expose hidden activity information to a connected application. Review both the audience for an activity and the permissions granted to other apps. See Strava's privacy FAQ.
Do not assume switching to another running app automatically provides stronger protection. Compare the settings and test the public view. A useful check is to inspect a published activity while signed out, then compare what remains visible with your intended audience.
Consider the surrounding information
A hidden start point may still be inferable from repeated routes, photographs, captions or a regular schedule. Avoid publishing information that reveals a home, school or workplace if that exposure matters to you. A screenshot can reveal details that the platform's map controls would otherwise hide.
For public-facing people or anyone facing harassment, decide whether public live sharing is appropriate at all. Sharing a finished activity later may fit the purpose better. Discuss a specific threat with someone qualified to help assess it rather than relying on an app comparison article.
Treat a live link as access to the session
Send a live spectator link to its intended audience and explain that it should not be forwarded publicly. Check expiry and sharing controls in the actual released product. End sharing when the session is finished and review any replay or saved map separately.
Runwiv's public demo does not require publishing your own location. Its planned live sessions should be evaluated against the privacy policy, product facts and the controls available at release. No product is described here as guaranteeing anonymity or personal safety.