Map visibility and story audience: privacy set per act, not once for your account

Location and audience aren’t account-level settings you configure once and forget about in RippleCore — they’re attached to each act, because what feels safe to share can change from one act to the next.

Map visibility is per act

Every act carries its own map-visibility level: exact, approximate, town-level (the recommended default), or hidden entirely. That reuses the same status-colour language as the rest of the product — danger, warning, success, neutral — and it’s always paired with a label, never colour alone. No member’s real-world location is exposed by default.

Story audience is per story

Just me, your Circle, or public — chosen per story, with member-protective defaults. A member can log something just for themselves, share it with their Circle, or make it public, without that choice carrying over to the next act.

Defaults protect the most vulnerable member

Location and map-visibility controls are treated as an accessibility-of-safety concern, not an afterthought — the defaults are set to protect whoever in a Circle is most exposed, not the median case. Members can still change their own defaults from their profile, and override either setting on any individual act.

Accessibility runs alongside this: WCAG 2.1 AA contrast in light and dark, prefers-reduced-motion honoured throughout, and colour that’s never the only signal. See the full picture on Safeguarding.