PRIVACY · LOCAL DEVELOPMENT DRAFT
Your presence. Your choice.
Visibility is opt-in. Your contact details are private.
What this local build stores
The application stores your verified email, profile, event opt-ins, visibility choices, consent history, and connection requests. OTP codes are hashed and expire. Session tokens are hashed in the database.
Who sees your profile
The member directory is available to signed-in members and only includes profiles that opt in. Event profiles are visible to signed-in members only when the participant enables event visibility. Member pages are not indexed by search engines.
Organizer access
Hosts see participation totals. Your first name is included in their roster and export only if you explicitly share it. Email and phone are not part of those exports.
Your controls
Change discoverability and notification preferences from your profile. Leave events and update their visibility individually. A profile data export is available in privacy settings. Account deletion, production retention automation, and privacy contact details remain pre-launch requirements.
Development use
This notice describes the local prototype and is not a reviewed production privacy policy. Use fictional information during development. No analytics service or advertising tracker is installed.