Security at BankerBro

The application runs on Cloudflare's global edge with TLS 1.2+ enforced. The database, auth and storage layers are provided by Supabase (built on PostgreSQL) hosted in an AWS region. Both providers publish their own security and compliance documentation.

Data in transit is encrypted with HTTPS. Data at rest is encrypted by our storage providers. Access to production infrastructure is limited to named administrators and gated by strong authentication.

Every database table uses row-level security. Members can only read and write rows they own, unless a specific policy (for example a moderator role) grants access. Community content in a bank-specific community is limited to verified members of that bank.

Sign-in is by email + password or Google OAuth. Passwords are hashed by our auth provider — we never see them. Verification codes expire after 10 minutes and are rate-limited.

Uploaded files are placed in a private storage bucket, scanned for size limits and served over signed URLs to the uploader and to reviewers only. We do not make uploads public unless the user explicitly shares them.

Even with these controls, please do not upload your employer's internal circulars, SOPs, customer data or system screenshots. See our Acceptable Use Policy.

Please email hello@bankerbro.com with a clear description and steps to reproduce. Do not test on other users' accounts. We will acknowledge within 3 working days.