How we keep your chamber's data safe.
Member records, invoices and your board's numbers deserve care. This page lists what Chamberly does today, and what it doesn't do yet.
Isolation
Your chamber runs on its own.
-
One instance and one database per chamber
Your members, invoices and events live in a database that holds only your chamber's data. There are no shared tables with any other chamber.
-
Hosted and run by Chamberly
We operate each chamber's instance for you. There's nothing for your staff to install or maintain.
-
Automated backups
Every chamber's database is backed up automatically each day, on servers in the United States. Each backup is kept for 3 days.
-
Sent over HTTPS
Data travelling between your browser and Chamberly is sent over HTTPS.
Access
The right people, and only while they should be.
-
Two staff roles
Every staff user is an admin or staff. New users join by an invitation link you send, and there are no shared logins to pass around.
-
Deactivation ends sessions immediately
When someone leaves your team and you deactivate them, every session they have ends at that moment, not when a token expires.
Record
Every change leaves a trail.
-
An activity log of who changed what
Each change shows who made it, when, and the old value struck through beside the new one. Failed attempts are logged too.
-
Money and permission changes kept for 7 years
The history of changes to money and to permissions is kept for seven years, so a treasurer's or auditor's question has an answer.
-
Secrets are never logged
Passwords, API keys and other secrets are never written into the activity log.
Payments
We never store card numbers.
-
Stripe handles cards
Online payments go through your chamber's own Stripe account. Card details are handled by Stripe, and Chamberly never stores card numbers.
-
Payments go to your account, not ours
Money from dues, tickets and sponsorships lands in your chamber's Stripe account. Each payment shows what the member paid, Stripe's fee, Chamberly's fee and your net.
Developers
Integrations with limits built in.
-
Scoped, revocable API keys
Each key is limited to the scopes it needs, can expire, is rate-limited, and can be revoked at any time. Give your website agency a key for what the site needs, and nothing more.
-
The MCP server never returns member records
Our MCP server gives AI coding tools your branding, schemas and integration guide so they can build on the API. It does not serve member data.
Not yet
What we don't have today.
If one of these is a requirement for your board or your insurer, tell us on the demo. We'd rather you know now.
- Two-factor authentication Not yet
- On the roadmap, not built yet.
- Single sign-on with your identity provider Not yet
- Signing in through your own Google Workspace, Microsoft or Okta account isn't available yet.
- Certifications Not yet
- Chamberly does not hold a third-party security certification today, and we won't claim one until an audit says so.
Reporting a vulnerability
Found something? Tell us.
If you believe you've found a security issue in Chamberly, email [email protected] with a description and the steps to reproduce it.
Please don't access or change data that isn't yours, and give us a reasonable chance to fix the issue before you share it publicly. We'll keep you updated while we work on it.
For questions about how we handle personal data, see our privacy policy or write to [email protected].