01
Payments
Payments are processed through Stripe. Benebid keeps event orders, transactions and payment references; card entry is handled by Stripe.
- Card numbers and security codes do not belong in Benebid event records.
Security & trust
Trust is part
of the product.
Fundraising events involve people, relationships and money. Protecting them is a core product requirement.
Clear protections. Clear boundaries.
02
Authentication
Customer sign-in uses Amazon Cognito and email verification codes. Access is checked by the server.
- Session cookies are encrypted, HttpOnly and secure over HTTPS.
03
Access controls
Organization membership and event roles determine access. A URL or an organization identifier alone does not grant permission.
- Private drafts and contributor information stay separate from approved public content.
04
Infrastructure
Benebid runs on AWS with HTTPS and a private PostgreSQL database.
- Database connections use verified TLS. Storage and database encryption are configured at rest.
05
Logging
Administrative and financial changes have audit records. Infrastructure logging supports investigation.
- Authorization headers and cookies are redacted from security request logs.
06
Agents
The public MCP surface reads public product information. It cannot read guest records, change events or move money.
- Customer operations follow organization permissions. Model-provider and retention questions can be directed to our security team.
A question about security?
Report a suspected vulnerability or ask about data handling at security@benebid.org. Please avoid sending passwords, payment details or guest data in an initial report.