Account isolation
Your data is isolated at the database level. Row-Level Security is enabled on every table and scoped to the authenticated user, so one account cannot read another account’s rows. A small number of server-side operations run with elevated database privileges; these are limited to named API routes and are not reachable from the browser.
Audit trail: GHG, CBAM and Bill Review
Every change to your GHG inventory, CBAM disclosure and Bill Review bill-extraction data is written to an audit log by a database trigger, not by the application, so the entry is recorded even if the application is bypassed. Seven tables carry the trigger: the GHG inventory and entry tables, two CBAM disclosure tables, and the three Bill Review job, document and proposal tables. The log is append-only: no update or delete permission on it is granted to any signed-in account. Other modules are not yet covered.