Trust comes from explicit boundaries.
Implemented controls and current limitations, without certification claims.
Accounts and workspaces
Argon2 password hashes, opaque hashed database sessions, HTTP-only cookies, exact origin checks and CSRF validation protect authenticated writes. Backend queries enforce workspace ownership. Personal email addresses are accepted.
OAuth and linking
One-time, expiring OAuth state is bound to a browser cookie. Google ID tokens require signature, issuer, audience, expiration, nonce and verified-email checks. GitHub uses stable user IDs and verified primary email. Existing emails require authenticated linking.
Source and provider privacy
Selected source is persisted in a bounded, tenant-scoped index until refresh, disconnect or retention cleanup. Provider keys remain in request memory. Excerpts leave the application only after explicit paid-operation consent. Provider terms govern external handling.
Execution boundary
Untrusted source never executes in the web/API process. The optional Linux runner uses rootless Podman, no network, read-only source, dropped capabilities and resource limits. High-assurance hostile-code isolation and live infrastructure validation are not claimed.
Before a public launch
Configure HTTPS, PostgreSQL, OAuth, GitHub App secrets and production origins. Independent security review, verified email/recovery delivery, distributed rate limiting and operational monitoring remain launch requirements.