Security at Strabora

Workspace data is designed to remain isolated between organizations. Database authorization policies provide an additional control layer for tenant-scoped access.

Strabora separates authenticated user access from privileged server-side operations.

Sensitive operations are subject to authorization and governance controls rather than relying solely on client-side restrictions.

Privileged operations such as sensitive AI result writes and server-owned records are handled through trusted server pathways.

Browser users are not granted direct access to protected server-only tables where such access is not required.

AI-generated work is separated from human authorization for consequential actions.

Draft generation does not automatically mean approval, authorization or execution.

Strabora uses authenticated access controls and provides account security functionality appropriate to the application.

Users should protect their credentials and report suspected unauthorized access promptly.

Relevant AI task and governance workflows can create structured events and records to support review, accountability and troubleshooting.

No online service can guarantee absolute security. Strabora continuously evaluates and improves its security controls as the platform develops.

If you believe you have discovered a security vulnerability or unauthorized access involving Strabora, report it promptly through an appropriate Strabora security or support channel.