🛡️ Security

Your donor list is the most sensitive file you own

Names, capacity estimates, giving history and private notes about people who trust your organization. We built ChaiRaise on the assumption that this data must never be casually exposed, resold, mined or held hostage. This page describes exactly how it is protected, and every claim on it is something we have built.

Last updated: October 18, 2026

Your donors are yours alone

Every record belongs to one organization, and the server checks that you are a member of that organization before a single row is returned. Knowing an organization's id grants nothing: if you are not a member, the request is refused. There is no shared donor pool and no path to read another organization's data.

Roles enforced by the server

Admin, manager, fundraiser and viewer roles are checked on the server for every action, not just hidden in the interface. Administrators can also mask financial fields from everyone but admins, and contact details from viewers.

AI runs on our servers

AI features call Anthropic's Claude Opus 5.5 from our servers. The API key never reaches your browser and customers never supply their own. Donor details go to the AI provider only when someone on your team triggers an AI feature, and AI requests are authenticated and rate-limited.

Your mailbox, if you prefer

Connect your own mailbox and outreach is sent through your mail server, from your address. The mailbox password is encrypted with AES-256-GCM before it is stored and is never returned by our API, not even to you. Mail server addresses are checked so they cannot be pointed at internal networks.

Take your data with you, any time

Managers can export everything we hold for the organization as a single JSON file, and any single donor's full record on request. Exports are rate-limited and recorded in the audit log, administrators can restrict them to admins, and stored credentials are never included.

Deletion means deleted

Administrators can permanently erase an individual donor or the entire organization. Erasure removes the data from every table of our live database rather than hiding it behind a flag, requires typed confirmation and cannot be undone. An erased donor's address stays on the suppression list so it is never emailed again.

The controls, specifically

What a security reviewer on your board will want itemized.

Encryption in transit
TLS on every connection, with HSTS enforced.
Encryption at rest
Database storage is encrypted at rest by our database provider.
Stored credentials
Mailbox passwords are additionally encrypted by the application (AES-256-GCM), so a database copy alone does not expose them.
Passwords
Hashed with scrypt and a unique salt per password, and compared in constant time. We never store or log a plaintext password.
Email verification
New password accounts must verify their email address before they can reach any organization's data.
One-time links
Verification, password-reset and invitation links are random, single-use and expire. Only a hash of each token is stored.
Server-side secrets
API keys and other secrets live only in server configuration and are never sent to the browser.
Audit log
Donor edits, email sends, exports, erasures and administrative actions are written to a per-organization audit log that administrators can review and export.
Rate limiting
Sign-in, AI, email, export and public forms are rate-limited to slow down password guessing, scraping and spam.
Session safety
Sessions expire, and the app signs you out automatically after a period of inactivity that administrators can configure.
Browser hardening
A strict Content Security Policy, no framing by other sites, no MIME sniffing, a restrictive permissions policy and a strict referrer policy.
Error handling
Errors are logged on the server and the browser receives only a generic message with a reference id, so internal details never leak.
Payments
Card details are entered on Stripe's checkout page. ChaiRaise never sees or stores a card number.

Who else handles your data

The complete list of sub-processors. We do not sell donor data, we do not share it with advertisers and we do not use it to train AI models.

Vercel
Application hosting and content delivery
Neon
Managed Postgres database (hosted in the United States)
Anthropic
AI features (Claude Opus 5.5), only when a user triggers an AI feature
Resend
Email delivery, when an organization has not connected its own mailbox, and account emails
Stripe
Subscription billing and payment processing
Upstash
Rate limiting to protect the service from abuse
Google
Optional sign-in with a Google account

What we do not claim

We would rather be trusted than impressive. ChaiRaise is a young product: we do not hold a SOC 2 report or an ISO certification, and we have not commissioned a third-party penetration test. We will say so plainly here until that changes. If your organization needs a formal security review or a data processing agreement, contact us and we will work through it with you.

Found a vulnerability?

Email yuri.kruman@gmail.com with "SECURITY" in the subject line, the affected page or route, steps to reproduce and the impact you observed. Please do not access, change or keep other customers' data while testing. We acknowledge reports within two business days, tell you when a fix ships and will not take action against good-faith researchers.

Privacy PolicyTerms of Service