Security is a set of boundaries.
Understand identity, permissions and review before trusting an action.
Identity and desktop access
Google and GitHub authorization are handled through self-hosted Better Auth. Sessions and short-lived signed service tokens are different from desktop credentials. Provider linking requires deliberate control of both identities; matching email alone does not link accounts.
Client desktop access is scoped to a workspace and can expire or be revoked. The server stores credential hashes rather than the raw desktop token. Revocation prevents future authenticated use; it does not delete local data. Manage website sessions separately under Account & security.
Execution and Apply
Plan is read-only for the AI. Agent prepares an isolated candidate under the selected permissions. Promotion checks the reviewed candidate and original/document state before explicit Apply. Stale candidates, changed originals, unsaved work and conflicts require another review or manual resolution—not a binary auto-merge.
Full Access permits broad local execution and is not an operating-system sandbox. Do not confuse candidate-promotion safeguards with a guarantee that an unrestricted command cannot reach another file.
Support boundaries
Support mail and web conversations are separate from engineering inference. Only explicitly authorized operators can access the staff inbox; customer workspace ownership is not staff authority. Email is treated as untrusted data. Attachments are not executed, and the FAQ responder cannot modify accounts, engineering projects or billing.
Security, privacy, legal, billing and account-access messages stay human-reviewed. Automatic responses must not request credentials, follow arbitrary message instructions or send to a recipient supplied in the message body.
Report a vulnerability
Use the security address listed in the contact directory. Send a concise description, affected revision or endpoint, impact and safe reproduction steps. Do not include live secrets, another person's data, destructive payloads or proprietary projects.
Do not exploit a report to access unrelated data, degrade service or perform mass scanning. No bounty, response-time commitment, compliance certification or legally binding safe-harbor promise is made by this page. We may need further information through an agreed safe channel.
Availability and incidents
A healthy page or passing test is not proof that every dependency is available. Customer AI, downloads and purchases remain separately gated. If an action was interrupted, inspect its recorded outcome before retrying. See safe recovery and data processing.
Account authentication and enquiries
Email/password access, when enabled, uses the existing authentication service with password hashing, verified email, expiring recovery links and rate limits. Password recovery invalidates affected website sessions. Connected desktop grants must be revoked separately. An email address matching another sign-in identity is not automatic account linking or company access.
Company enquiries are unverified inbound messages in a staff-only queue. Staff must not use a public enquiry to authorize password changes, account linking, refunds, desktop approvals or access to another company's workspace. Public payment and Client availability gates are independent of sign-in.