Security at SignM8
We are responsible for the security of your screens, your clients' data, and the platform you rely on. Here's how we protect it.
Summary
How SignM8 protects your data
SignM8 uses industry-standard encryption, role-based access control, and Australian cloud hosting to protect your account. Device credentials are hashed before storage. Sensitive actions are logged to an audit trail. IP whitelisting lets you add an extra layer of network-level access control. We operate on a least-privilege principle: every user and every device only has the access they strictly need.
Security practices
Data encryption
All data is encrypted in transit using TLS 1.2+. Device credentials are stored as bcrypt hashes — plaintext tokens are never persisted.
Australian cloud hosting
All infrastructure is hosted in the AWS ap-southeast-2 (Sydney) region. Your data stays in Australia.
Role-based access control
Four roles (platform admin, integrator admin, customer admin, content manager) enforce strict data isolation. Each user sees only the data they are authorised for.
IP whitelisting
Three-tier IP access rules let you restrict dashboard access to known IP ranges at the platform, integrator, or customer level — with full IPv4 CIDR support.
Audit logging
Sensitive actions — including integrator impersonation of customer tenants — are written to an append-only audit log with timestamps and actor details.
Responsible disclosure
We welcome security researchers. If you discover a vulnerability, please report it privately to our security team before public disclosure.
Device security
Each paired screen receives a unique device token at provisioning time. This token is hashed (SHA-256) before storage — even if the database were compromised, raw tokens could not be recovered. Devices authenticate every heartbeat and command acknowledgement using this token.
Screens can be revoked from the dashboard at any time. Revoked screens immediately lose their authentication and can no longer receive content or commands.
The emergency broadcast feature uses a separate site token that is scoped to a single tenant and can be regenerated without affecting screen pairing.
Responsible disclosure
If you discover a security vulnerability in SignM8, please report it to us privately before any public disclosure. We will acknowledge receipt within 2 business days and aim to resolve confirmed issues promptly.
Questions about our security practices?
Contact us