Security

Organization-scoped access

Every user belongs to an organization. Users can only read or change records belonging to their organization. This is enforced by database row-level security policies, not just in the user interface.

Role controls

Roles (president, treasurer, board, staff, volunteer) determine what a user can do. Sensitive views and actions require the appropriate role.

Audited privileged transitions

Reimbursement approvals, rejections, payments, and destructive transaction deletions run through server-side functions that record an audit entry with the acting user, the previous state, and the new state.

Receipt access

Receipts and event documents are stored in access-controlled storage. Links are short-lived and only issued to authorized users.

Responsible disclosure

If you believe you have found a security issue in Board Ripple, please email hello@boardripple.com with a clear description and reproduction steps. Please do not include production data, credentials, or the personal information of other users in your report.

We ask reporters to give us a reasonable window to investigate and remediate before public disclosure. We will acknowledge receipt within five business days and share a remediation plan or timeline with the reporter. We do not currently operate a paid bug bounty program.

We will not pursue legal action against good-faith researchers who follow this process, avoid privacy violations, and do not degrade the service for other organizations.

Response transport headers

Production responses set a restrictive Content Security Policy, HSTS on the production custom domain, referrer, permissions, and framing protections. See the security baseline for details.

What we do not claim

Board Ripple does not claim any specific security certification. We do not claim "bank-grade," "military-grade," or similar security on this page. Security is an ongoing practice.