Security

What is in place

• Each organisation's records are separated at the database level, so one organisation cannot read another's information even if the application misbehaves.
• Every screen and action is checked against the permissions of the signed-in account, on the server rather than in the browser.
• Access decisions fail closed: if a permission or an organisation cannot be established, access is refused rather than allowed.
• Evidence records — audits, approvals, incidents, exports — are written to an append-only trail that cannot be edited or partly deleted. Corrections are made by adding a superseding entry.
• Sign-in attempts are rate-limited and locked out after repeated failures, and security events are recorded.
• Traffic is encrypted in transit, and the database is encrypted at rest by the hosting provider.
• Privileged access requires two-step sign-in; permissions are not relaxed for live purchasing.
• Every change to the platform goes through automated checks covering permissions, data separation, secrets and dependencies before release.

What we do not claim

• We state no recovery time or maximum data-loss figure and give no recovery guarantee.
• We hold no independent certification such as ISO 27001 or SOC 2, and have not had an independent audit or penetration test.
• We make no assurance about a fixed backup-deletion period or provider incident-notification timescale.

Customers may ask us for our written security description and evidence pack. We do not offer live access to systems holding another organisation's information.

Reporting a problem

If you believe you have found a security weakness, write to the Data Protection Contact, MW CARE 4 U LIMITED at 71–75 Shelton Street, Covent Garden, London, WC2H 9JQ, United Kingdom. Please do not test against other people's information. We will confirm receipt, investigate, and tell you the outcome.