Product
Security is a design constraint, not an afterthought.
Benefitly handles member, benefit, and financial-adjacent data for real associations. Our security model is built around limiting access by default and proving, not assuming, that it stays limited.
Data isolation between organizations
Every organization's data — members, dues, benefit claims, events, campaigns — is scoped with database-level row-level security, enforced against the running application role, not just in application code. A user only ever sees the organizations and records their permissions actually grant.
Encryption
- Data encrypted in transit (TLS) between clients, our servers, and our database and payment providers
- Data encrypted at rest in our managed database and storage infrastructure
- No card numbers or bank account numbers are ever stored on Benefitly's own infrastructure — that data lives only with our regulated payment providers
Access controls
- Role-based permissions at the organization level (owner, staff, member)
- Platform-level administrative access limited to a small, audited set of accounts
- Every security-definer database function performs its own authorization check before writing data
Monitoring & audit trails
- Moderation actions, payout approvals, and benefit claim decisions are recorded with an actor and reason
- Fraud signals and campaign reports route to manual review before funds move
- Webhook events from payment providers are signature-verified before being trusted
Responsible disclosure
If you believe you've found a security issue in Benefitly, please report it through Contact Us rather than filing a public issue. We investigate every credible report.