1. Information Bro Code collects

Bro Code may collect account information such as your email address, first name, account status, role, policy-acceptance records, authentication information handled by Supabase, and activity needed to operate moderation and security features.

People using Privacy & Report Help verify an email sign-in identity and provide a request type, their connection to the concern, optional limited profile descriptors or a reference ID, and request/reply text. This does not create community membership or unlock reports. Do not submit identity documents, attachments or private contact details in request text.

2. Community submissions

Members may submit limited profile descriptors such as first name, city, approximate age range, and first-hand dating experiences. Bro Code is designed to avoid collecting home addresses, phone numbers, workplaces, exact birth dates, government identification numbers, financial information, and other unnecessary sensitive identifiers.

3. How information is used

Information is used to authenticate members, manage membership approval, provide member search, review reports, process disputes, prevent abuse, enforce community rules, investigate security incidents, and maintain moderation records.

4. Access controls

Member content is intended to remain behind authenticated and approved membership. Database access is restricted using Supabase Row Level Security and role-based permissions. Moderators and administrators may access additional records needed to perform review and enforcement duties.

Privacy-request conversations are accessible to the verified requester and approved moderators. Email verification establishes mailbox access, not that a person is the subject of a report or that a claim is accurate. Moderators may ask for appropriate non-sensitive context before deciding.

5. Automated protections

Bro Code uses technical rules to reject certain contact details and identifiers from reports and review requests, and to limit excessive submissions. These protections reduce risk but cannot guarantee that every prohibited detail will be detected automatically.

Member content-use limits keep per-account time-window counts for searches, experience pages, dashboard totals, report-profile lookups and review-request context. These quota counters contain the account ID, window times and counts; they do not contain search phrases or report text.

6. Service providers

Bro Code currently relies on service providers including Supabase for authentication and database services, Vercel for website hosting and deployment, and GitHub for source-code hosting and deployment integration. Those providers process information according to their own terms and privacy practices.

7. Retention

Account, moderation, report, dispute, and audit records may be retained while needed to operate the service, enforce rules, resolve disputes, protect users, or satisfy legal obligations. A formal retention schedule should be established before public launch.

8. Corrections and removal

Bro Code provides a review-request process for published reports. Account or privacy requests may require identity verification before records are changed or removed. Some records may need to be retained for security, fraud prevention, dispute history, or legal reasons.

Members and nonmembers can use Privacy & Report Help to request correction, removal or privacy/account assistance. A verification email provides access to the private request conversation. Replies are posted in that conversation; return using the same verified email to check updates. No community membership is required, and the request form does not expose member content.

A request, reply or closed status does not by itself change a report or delete an account. An administrator must carry out any appropriate action and explain the outcome, including what was removed or retained and why. Do not submit a password or identity documents through the form.

Signed-in members can use Account → Settings to request an email change, open password recovery, or submit and track an account-deletion request. Moderators can review and respond to deletion requests. Submitting or closing a request does not itself erase an account or its content; any deletion and retention review is handled separately by an administrator. Private in-app notifications record new moderation outcomes and whether the recipient has read them.

9. Security

Bro Code uses access controls, authentication, moderation, server-side validation, submission limits, and browser security headers. No internet service can guarantee absolute security, so members should avoid submitting information that Bro Code does not need.

10. Beta notice and legal review

This privacy notice describes the current private-beta design. It is an operational policy draft, not a representation that every privacy law has been fully analyzed. Before public launch, Bro Code should obtain legal review and establish a formal retention, deletion, incident-response, and user-request process.