Built to protect the people behind your data
Charities hold donors’ finances, volunteers’ screening checks and the details of children and people in crisis. Missionly treats protecting them as the default behaviour of the product, not an add-on.
Six layers of protection
Your data is isolated
Each organisation is a separate tenant. Every database request runs inside an explicit tenant session with row-level security, so a bug in one query cannot leak another organisation’s records.
Strong sign-in
Every organisation gets its own identity realm. Staff sign in once with single sign-on, protected by authenticator or one-time-passcode MFA, brute-force protection and session timeouts you control.
Least-privilege access
Access is granted by permissions, not role names, and scoped by project, country or partner. Sensitive beneficiary fields need their own permission, and every view of one is audited.
A record of everything
Creates, updates, deletes, sensitive views, exports, permission changes and sign-ins are logged. Organisation admins can read their own audit log, and financial records are immutable.
Card data never reaches us
Card details are typed only into Stripe or SumUp hosted fields and read only by certified readers. Missionly never sees, stores or logs a card number, which keeps your PCI scope light.
Children protected by default
Sponsor-facing profiles show approved fields only. Photos lose their location data, correspondence is read before release, and contact details are flagged and blacked out.
Protections across the platform
- TLS 1.2 or later everywhere, HSTS, a strict content security policy and secure cookies
- Application-level encryption designed for the most sensitive fields (bank details, health fields, screening numbers)
- Rate limiting and bot protection on public donation, ticket and intake endpoints
- No personal data, tokens or card data in logs, and personal data scrubbed from error reports
- Secrets kept in a secrets store and never in code, with least-privilege service accounts
- Dependency scanning in the build pipeline
- Safe by default for vulnerable clients: quick-exit intake forms, safety alerts, restricted notes and secure expiring client links
- Consent records, supporter data export, correction and anonymised erasure
Report a vulnerability
If you believe you have found a security issue in Missionly, email info@missionly.org with the details. Please do not access data that is not yours, and give us reasonable time to fix the issue before sharing it publicly.
What we are honest about
We build to OWASP ASVS Level 2 and plan an independent penetration test. We do not yet hold ISO 27001 or SOC 2 certification. The Trust Center lists every control with its real status.
Have a security questionnaire?
Send it over. We will answer it against the real product and walk your IT and compliance team through how it works.