Security
Draft placeholder. This page describes current architectural practices, not a completed audit. Proximo does not currently hold SOC 2, ISO 27001, HIPAA, PCI or GDPR compliance certification. Do not represent this page as a compliance attestation.
Tenant isolation
Every tenant-owned record is scoped to an organization and enforced at the database layer with row-level security, in addition to server-side authorization checks. Organization identity is never accepted as authoritative from a client request.
Separate credentials per role
Staff, devices, the realtime publisher, the retention job and the public lead-capture form each connect to the database through their own isolated, minimally-privileged login — never a shared or superuser connection. The migration owner that applies schema changes is never available to the running application.
Authentication
Staff authentication uses Amazon Cognito with the authorization-code/PKCE flow. Session tokens are stored in HttpOnly cookies and are never exposed to browser JavaScript. Device credentials are separate from staff credentials and cannot impersonate a staff user.
Devices
Kiosks and displays are paired through a manager-issued, short-lived code and receive their own revocable, location-bound credential.
Reporting a concern
If you believe you've found a security issue, contact us through the contact page.