SECURITY & TRUST

Clarity builds trust.

Here is what this build implements—and what a production operator still needs to own.

Account protection

Local passwords use scrypt. Sessions and recovery codes are hashed in persistent SQLite storage. Project endpoints check ownership. Public deployments must enable HTTPS and secure cookies.

Provider keys

Keys entered in Settings are sent through the Buildora server to the chosen provider. Saved provider keys are encrypted in browser storage and restored for the signed-in account; they are not synced to an account database. Only approved HTTPS provider endpoints are accepted.

Generated code

Review generated changes and dependencies. A working preview is not a security audit. Do not put service-role keys or private provider keys into generated frontend source.

Operations

Backups, monitoring, dependency updates, deployment review and shared rate limiting are operator responsibilities. This build has not undergone an independent security audit.