For security review

The questions your security review asks, answered before you ask them.

Tenant isolation, GDPR erasure, and audit logging aren’t a checkbox added before a sales call — they’re how the data layer is built.

Feature by feature

	Qmatrix	Typical QA tool
Tenant isolation enforced at the data layer	✓	Often UI-only
GDPR export, anonymize, and true hard-delete	✓	Soft-delete only, commonly
Audit log on sensitive actions	✓	Varies
Signed, replay-safe webhooks	✓	Varies
Server-side enforcement of plan/billing state	✓	Frontend-only in some tools
A lapsed subscription goes read-only, never deletes data	✓	Varies

1
Isolation is structural, not conventional
Every tenant-scoped query is filtered at the data-access layer itself, not left to individual endpoints to remember. Audited across every entity in the schema; the one gap the audit found was closed and shipped with a regression test.
2
Deletion means deletion
Account removal runs export → anonymize → hard-delete: personal data is actually gone from the database, with associated content preserved under a placeholder account rather than orphaned or silently retained.
3
Billing failure is never a data-loss event
A failed payment gives a 5-day grace period, then the workspace goes read-only. Nothing is ever auto-deleted for a billing reason — reactivating restores full access with the data exactly as it was left.

We’d rather walk you through the actual architecture than hand you a compliance PDF written by someone who’s never seen the code.