Security

Security as an architectural property.

MS Global Growth treats isolation, identity and auditability as design constraints rather than later additions. This page describes the controls actually implemented in the platform.

Identity management

Email and password authentication with verification and recovery, plus Google sign-in. Sessions are token-based and revocable.

Role-based access control

Roles are stored separately from user profiles and evaluated server-side. User, staff and admin scopes are enforced in the database, not the interface.

Organisation data isolation

Every tenant row carries an organisation reference, and row-level security policies restrict reads and writes to members of that organisation.

Encryption

Traffic is encrypted in transit with TLS. Data at rest is encrypted by the managed storage layer, and secrets live in a managed secret store.

Audit logging

Privileged actions, access changes and workload operations are written to an append-only audit log, scoped per organisation.

Monitoring

Platform metrics, traces and logs feed anomaly detection for availability, latency, error rates and cost.

API security

API keys are scoped per organisation, hashed at rest, individually revocable and rate limited at the gateway.

Secure infrastructure architecture

Private networking, deny-by-default service policy, allow-listed egress and infrastructure defined as reviewable code.

Scope and honesty

What we do not claim

MS Global Growth holds no security certifications and makes no compliance claims on this site. We do not claim SOC 2, ISO 27001, HIPAA or PCI attestation. Where a control is contractual — data residency, retention windows, incident response times — it is agreed in writing, not implied here.

Reporting a vulnerability

Send findings to security@msglobalgrowth.com with reproduction steps. We acknowledge reports and share remediation status with the reporter. Please do not test against customer environments.