Security

Last updated: August 2026

Organizations trust OurCharter with their member rosters, governance records, and — eventually — their money. Here is plainly how we protect that, and what we deliberately do not do ourselves.

Authentication

Sign-in is handled by Clerk, a dedicated identity provider. We never see or store your password. Sessions are short-lived signed tokens verified on every request; the mobile apps keep credentials in the device’s secure enclave (Keychain / Keystore).

Payments

Card numbers never touch our servers. All payment processing runs through Stripe, a PCI-DSS Level 1 certified processor; each organization connects its own Stripe account, and funds flow directly to the organization.

Data & infrastructure

  • Application data lives in Convex, encrypted in transit (TLS) and at rest, with continuous backup managed by the platform.
  • Every server-side action is permission-checked against your role in the organization, and administrative actions are recorded in an audit log your organization can review.
  • Anonymous elections are engineered so that ballots cannot be joined back to voters — not even by us. Receipts prove that you voted, never how.
  • The web app ships strict security headers (CSP, HSTS, frame denial) and sanitizes all member-authored content.

Responsible disclosure

Found a vulnerability? Email support@ourcharter.org and we will respond promptly. Please give us a reasonable window to fix the issue before public disclosure.