- Encryption in transit
- All traffic to PointMintz is served over HTTPS with modern TLS. HTTP requests are redirected to HTTPS, and HSTS is enabled so browsers refuse to downgrade the connection.
- Encryption at rest
- Tenant databases, uploaded files, and off-host backups are stored on encrypted volumes. Secrets and API keys are held in the platform secret store, never in application source.
- Per-tenant data isolation
- Every tenant runs against its own isolated database. One business can never read or write another business’s bookings, customers, or payment references, and every request is scoped to a resolved tenant before any data is touched.
- Payment security
- Card details are collected and stored by Stripe, our PCI-DSS Level 1 payment processor, under SAQ-A scope. PointMintz never stores full card numbers — only Stripe payment references and non-sensitive transaction metadata.
- Access controls
- Staff and admin accounts use role-based permissions, and platform-operator access to the control panel requires multi-factor authentication. Sessions are protected with secure, host-locked cookies and CSRF tokens on every state-changing request.
- Backups
- Tenant data is continuously replicated to off-host, encrypted backup storage in a separate region, so a single host failure never means data loss. Backups are tested for restorability.
- Vulnerability management
- Dependencies are monitored for known vulnerabilities and patched on a regular cadence. Production changes pass an automated test and validation gate before deploy, and we welcome responsible disclosure from security researchers.
- Incident response
- We maintain an incident-response process with defined severities and on-call ownership. Tenants affected by a confirmed security incident are notified without undue delay, consistent with our breach-notification commitments.