Safety and moderation
Reports, verification states, and moderation actions should be stored so harmful patterns can be reviewed and audited responsibly.
Privacy overview
Member trust depends on clear data boundaries.
What we collect, why we use it, and the controls you have as a member. Designed to be understood, not buried.
Profile information
Basic account details, faith preferences, prompts, and media are used to build the member profile and improve match relevance.
Product operations
Usage events, notification preferences, and subscription status should support product delivery without exposing unnecessary private detail.
What control should members have?
Members should be able to manage visibility settings, pause discovery, control notification preferences, request data exports, and begin deletion requests from within their account settings.
Who should see admin-only data?
Only authorized staff should access sensitive member records, moderation evidence, or billing context, and those actions should be attributable through audit logs.
Is this the final privacy language?
Not yet. This page gives the experience a complete privacy surface, but production language should be finalized with policy and legal review.