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.

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.

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.

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.

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.