Trust
Security and data
How Webtick protects your data and limits what it can do.
- Workspace isolation: every row belongs to one workspace, enforced by PostgreSQL row-level security.
- Least privilege: Google access is read-only; other sources are read-only with your key; GitHub is pull requests only; the CMS is drafts only.
- Secrets: OAuth tokens and API keys are sealed with AES-256-GCM, bound to their record, never returned and never logged.
- Models: a language model receives text and returns text. It never receives a credential and never calls GitHub or a CMS; its output goes through the same validation as a person's draft. Site text is passed as untrusted data.
- Outbound requests to user-supplied hosts go through a guarded client: public addresses only, pinned, and no redirects for anything that carries a credential.
- Approvals are bound to the exact proposal; schema changes and external-agent proposals always need a person.
- Every state change is recorded in Activity.
Google user data is used only to provide the features you use, is never sold or used for advertising, and is never used to train AI models. The privacy policy at webtick.app/privacy has the details, including the Limited Use disclosure.