A summary of the security posture that’s actually built into MFLIX today. Unlike our Privacy Policy and Terms of Service, this page describes shipped functionality rather than legal commitments.
Every table is protected by row-level security policies enforced by the database itself, not just application code. A company’s data is never reachable by another company’s members, regardless of what the application layer does.
Every admin-gated mutation is written to an append-only audit log with the acting user, timestamp, and action metadata, visible on each company/group/user’s history. That covers role changes, deactivations, content grants, and moderation actions.
Authentication and other abuse-prone actions (sign-in, password reset, invitations, broadcast sends) are rate limited by IP or account to reduce credential-stuffing and spam risk.
Platform staff roles are split by capability: a read-only support role can view account and usage data to help troubleshoot, without the ability to grant admin access, delete data, or otherwise mutate your account.
Deactivating a company, group, user, or learning path hides it from active views without deleting the underlying data: most administrative actions can be undone rather than being immediate and permanent.
Unhandled errors are captured by real-time error tracking so issues are found and fixed proactively, rather than relying solely on users to report them.
If you believe you’ve found a security issue, please report it to your account owner or platform support rather than disclosing it publicly.