This page follows the same rule as everything else ORION discloses: a stated fact is checked against the running code, not aspirational. If something below isn't true yet, it says so, rather than staying silent about it.
Database tables have row-level security enabled. Browser sessions do not read or write database tables directly. One exception: a signed-in browser calls a single read-only database function that returns only that user's own report list. Every other read and write goes through ORION's servers, and the service-role credential is used only in server-side code, never in the browser.
Authentication tokens are re-verified against Supabase on every request. Account access is never trusted from anything the browser sends; it is re-checked on the server.
API keys and service credentials are environment variables on the backend only — never shipped to the browser, never logged in plaintext, never returned in any API response.
Failures are logged in a consistent, searchable format with masked identifiers — not left as unlabeled text an operator would need to happen upon by accident.
Investigation steps for incidents are documented in an internal operations runbook, not improvised during an incident.