Tenant isolation
Each tenant runs on its own tenant database file, with host-based tenant resolution and application authorization checks before tenant data is read or mutated.
PointMintz protects tenant and customer records with per-tenant isolation, role-based access, audit logs, hardened browser policies, encrypted transport, backup discipline, and compliance workflows surfaced in the product.
Each tenant runs on its own tenant database file, with host-based tenant resolution and application authorization checks before tenant data is read or mutated.
Tenant admin, staff, customer, and platform admin sessions are separated. Sensitive exports and privacy queues are restricted to privileged roles.
Local and hosted surfaces use HTTPS. Production secrets are kept out of source code and referenced through environment or managed secret stores.
Security, admin, billing, privacy, and compliance events write audit evidence. Audit-retention exceptions are disclosed in the privacy policy and DPA materials.
Tenant backups use bounded restore windows and are tied to erasure workflows so verified deletion cannot silently reappear from stale replicas.
Tenant admins can review DPA, PCI, HIPAA safeguards, licensing, insurance, and privacy-request posture from the Compliance Dashboard.