Tenant isolation
Application requests carry an authenticated tenant context. API authorization and database policies scope access to that tenant, including operator and customer-portal views.
Current controls
Security at Terminal
Terminal coordinates commercially sensitive master data, allocations, and terminal-system messages. These are the controls implemented for the current platform and the boundaries customers should understand.
Authentication and access
Terminal uses Supabase-issued sessions and server-side role checks. Administrative, operator, viewer, and customer capabilities are enforced at protected API boundaries.
Integration credentials
Tenant integration secrets are written through restricted administration endpoints and stored using per-tenant envelope encryption. Saved secret values are not returned to the browser.
Transport and storage
Production traffic is expected to use TLS. Managed infrastructure encryption protects supported database and backup storage at rest.
Audit and operations
Operational changes, allocation runs, publication attempts, and approval decisions produce tenant-scoped audit records for investigation and reconciliation.
Secure development
Changes pass automated tests, static checks, dependency review, and security-focused release checks. Confirmed vulnerabilities are prioritized by impact and exploitability.
Assurance status
Terminal is not currently certified under SOC 2 or ISO 27001. We do not present pilot controls as independent certification. Customers can request current architecture and security-review material from security@terminaliq.io.
To report a suspected vulnerability or tenant compromise, email the security address above. Do not include credentials, private keys, or production data in the initial message.