Operator review draft — public legal approval pending

# Soulr privacy — owner review draft

Controller/operator: Christopher Campbell, operating Soulr as an individual. Contact for support, privacy and safety requests: soulrmatch@gmail.com. These details were supplied by the owner on October 18, 2026. Inbox delivery, response coverage and legal notices are not yet verified. This draft is not an approved public notice.

The account implementation processes email and authentication data through Supabase Auth; birthday/adult consent, profile name, bio, city, interests and discovery choice; mutual likes/matches, participant messages; posts, audience, comments and reactions; blocks, reports and moderation evidence; and personal visual preferences/shared-glow consent. Do not request health, identity-document, precise-location or sensitive spiritual information in this release.

The server verifies issuer identity and current sessions. Encrypted HttpOnly browser cookies carry authentication grants; access and refresh tokens are not returned to browser application storage. Database roles and eligibility are owned by server/database rules, not editable profile metadata. The app uses Netlify hosting/functions and Supabase authentication/database. Auth email sender/SMTP arrangements and any international transfers must be verified and described by the operator before launch.

Signed-in adult-member posts are accessible to eligible members; connection-only posts require a current mutual connection. Messages are participant-only. Blocking and suspension restrict current access. A report may preserve a snapshot for a human moderator, including after the post is removed. Administrators do not receive unrestricted private-feed access.

The optional Umbrella Hub stores the offer selected, its description at submission, your enquiry text, submission time and explicit consent to share the enquiry and your confirmed account email with the operator for answering that enquiry. Other members cannot read it. Authorized operators can record internal review notes and status; members do not receive those internal notes. Enquiry consent is not marketing consent. Enquiries, audit evidence and some associated identifiers currently remain after account disablement. The operator must approve retention periods and an erasure procedure before activating this feature for real people. No automatic customer email or purchase follows an enquiry.

In-app account disablement immediately revokes app sessions and hides account content. The current schema retains some disabled-account identifiers and moderation records; complete erasure requires the operator's documented process. Specify retention periods, lawful bases, user access/correction/deletion procedures, appeal contacts, applicable regional rights, processor agreements and breach handling before collecting real-user data.

No payment processing, advertising trackers, customer-facing model agents or model training is activated in this release. Shared visual preferences are symbolic and consensual; the application does not infer emotions, ethnicity, love or spiritual status. Future analytics/AI/commerce use requires separately reviewed disclosures and consent where applicable.