Trust Center

Security, privacy and compliance, with nothing overstated

This page lists what we do, what we build to, what is planned and what we do not have yet. It is written for boards, finance teams and IT reviewers who need straight answers. Read the security overview for the story behind it.

Security controls

In placeBuilt to standardPlannedNot yet
Missionly security controls and their status
AreaControlWhat it meansStatus
IsolationTenant isolationEvery database request runs inside an explicit tenant session with row-level security, so one organisation can never read another’s data.In place
IdentityRealm per organisationEach organisation has its own identity realm with its own users, roles, MFA policy and branded sign-in page.In place
IdentityMulti-factor authenticationAuthenticator or one-time-passcode MFA, brute-force protection and session timeouts are set per organisation.In place
AccessPermission-based accessAccess is granted by permissions, never by role names, with project, country and partner scopes for sensitive records.In place
AuditAudit trailCreates, updates, deletes, sensitive views, exports, permission changes and sign-ins are logged. Organisation admins can read their own audit log.In place
PaymentsCard data stays with the processorCard details are entered only in Stripe or SumUp hosted fields and read only by certified readers. Missionly servers never see or store card numbers.In place
DataEncryption in transitTLS 1.2 or later everywhere, HSTS, strict content security policy, secure HttpOnly SameSite cookies and CSRF protection.Built to standard
DataField-level protectionHighly sensitive fields such as bank details, beneficiary health fields and screening numbers are designed for application-level encryption.Built to standard
SafeguardingChildren’s data protected by defaultSponsor-facing profiles contain approved fields only, photos are stripped of location data, updates and letters are moderated, and contact details are blocked.In place
PrivacyConsent and data-subject toolsPer-purpose consent records, supporter data export, correction and anonymised erasure that keeps statutory financial records.In place
ApplicationOWASP ASVS Level 2ASVS Level 2 is the verification standard we build and test against.Built to standard
AccessibilityWCAG 2.2 AAStaff app, supporter portal and public forms are built to WCAG 2.2 AA with automated accessibility audits.Built to standard
AssuranceExternal penetration testAn independent penetration test is planned before launch and annually after.Planned
AssuranceISO 27001 or SOC 2 certificationWe do not currently hold a third-party security certification. Ask us for our security questionnaire answers instead.Not yet

Receipts and tax rules by country

Rule packs decide whether a gift is receiptable, the eligible amount, the required wording and the numbering. Thresholds live in configuration, not code, and each pack is tested against sample donations.

  • AUAustralia

    DGR-endorsed gifts, ABN on receipts, event contribution rules kept in configuration

  • UKUnited Kingdom

    Acknowledgement receipts and Gift Aid declarations

  • USUnited States

    Written acknowledgements and quid pro quo disclosure

  • CACanada

    Official donation receipt fields and serial numbers

  • NZNew Zealand

    Donation receipts for approved donee organisations

  • GENERICEverywhere else

    Acknowledgement receipt with no tax claim

Product features support compliance but are not legal or tax advice. Confirm requirements with your own accountant or regulator.

Privacy

We design to the strictest common denominator so organisations in any country can comply. Missionly acts as a data processor for your organisation.

Regimes we design for

  • Australian Privacy Act 1988 and the Australian Privacy Principles
  • EU and UK GDPR
  • Canada PIPEDA
  • New Zealand Privacy Act 2020
  • US state privacy laws where they apply

Email consent

Every marketing email carries sender identification and a working unsubscribe. Consent is checked at send time, and transactional and marketing messages are classified separately.

Rules the product follows

  • Australia: Spam Act 2003
  • UK: PECR
  • EU: ePrivacy
  • US: CAN-SPAM
  • Canada: CASL

Sub-processors

Third parties that may handle organisation data on our behalf.

Missionly sub-processors
ProviderPurposeUsed when
Amazon Web ServicesHosting, storage and email deliveryAll organisations
StripeOnline card and wallet payments, recurring giftsOrganisations that choose Stripe
SumUpOnline payments and in-person card readersOrganisations that connect SumUp
Keycloak (operated by Missionly)Sign-in, MFA and single sign-onAll organisations
Error monitoringCrash and error reports with personal data scrubbedAll organisations

Backups and recovery targets

These are our engineering targets, not a contractual service level. Your agreement states what is committed.

Backups
Full nightly, log backups every 15 minutes, off-box and cross-region copies
Retention of backups
35 days, plus monthly copies for 12 months
Recovery point objective
15 minutes
Recovery time objective
4 hours
Restore drills
Monthly
Audit log retention
7 years or more

Documents and requests

  • Data Processing Agreement

    Standard DPA covering Missionly’s role as your data processor.

  • Security questionnaire

    We answer your questionnaire against the real product.

  • Data export or deletion

    A full machine-readable export of your organisation’s data on request or at closure.

Request a document

Questions your board will ask? We have straight answers.

Book a guided demo and we will walk through the modules that matter to your organisation, from fundraising to field work.