Security and information handling
Toolora protects records through authenticated identity, company and resource checks, database policy and scoped publication. Credentials remain outside browser configuration and Git. Authorization establishes who may act on a record. Information handling also covers what enters files, logs, AI context and retained operational evidence.
Trust boundaries and privileged access
Section titled “Trust boundaries and privileged access”Browser Supabase access is constrained by RLS. Server-side service-role calls bypass that policy and therefore require explicit authorization and resource checks. Provider calls add another boundary with externally visible effects. Route policy and database policy must each be reviewed on the paths that use them.
Trust and privilege boundaries explains the detailed rules, examples and evidence limits.
Credentials and configuration
Section titled “Credentials and configuration”The runtime broker supplies protected server configuration files. The frontend receives only browser-safe values. Human recovery uses the existing shared credential source rather than application credentials copied into documentation. Rotation verifies a replacement before revoking the old value. Configuration ownership identifies the relevant component without exposing secret values.
Credentials and protected configuration explains the detailed rules, examples and evidence limits.
Personal data, originals and retention
Section titled “Personal data, originals and retention”Personal and business data can appear in records, messages, original files and review evidence. Access and retention depend on the owning source and product policy. The mail archive’s source policy does not establish an additional Toolora expiry schedule. Signed retrieval links do not replace a retention or deletion policy.
Records, originals and data lifecycle explains the detailed rules, examples and evidence limits.
Audit, logs and incident evidence
Section titled “Audit, logs and incident evidence”Operational evidence should identify the affected component, operation and outcome while keeping credentials and personal data out of logs and Git. Tool events and full business payloads serve different purposes. Incident response preserves useful diagnostic evidence and routes privacy or customer communication to the responsible owner.
Audit, logs and incident evidence explains the detailed rules, examples and evidence limits.