Security
How Zest signs you in, what its tokens can do, what it can read on GitHub and Slack, how each workspace is kept apart, and how long anything is kept.
Sign-in and device login
- The app and the web sign you in with an emailed 6-digit code (valid 10 minutes, 5 tries, stored hashed), or with GitHub, Google or Apple. There are no passwords. On iOS and Android the session never travels in a URL: the app swaps a one-time code for it.
- Plugins use device login. The plugin asks Zest for a code, valid 10
minutes, and opens
/devicein your browser. You sign in and type the code yourself, so a link someone else sends you cannot fill it in. The page shows which plugin asked, its operating system, roughly where from (city, region and country, never the IP address) and how long ago, then Approve or Deny. - The one-command installer (
npx @winding-labs/zest) signs in once the same way, then mints a separate token for each plugin it set up. It can do that only within 10 minutes of its own sign-in, and each token can be revoked on its own.
Tokens on your laptop
- Where. Each plugin keeps its token in
zest2-auth.jsoninside its own folder (for example~/.claude-zest/). The file is readable only by you (0600) in a folder only you can open (0700), and the permissions are set again on every write. The VS Code and Cursor extension keeps its token in the editor's SecretStorage, which the operating system's keychain backs. - What a plugin token can do. Upload sessions, read the plugin settings,
refresh itself, switch workspace, read and request your standup and level, report a
problem, and use MCP. Everything else answers
403: the app's screens and transcripts, sharing, invites, settings, billing, API keys and account deletion. - How long. 60 days, extended when it is used (at most once a day). Signing out in the plugin revokes it on the server and removes it from your laptop; a revoked token can keep working for up to 60 seconds.
- Where it goes. Only over HTTPS, and only to the Zest API that issued it. A plugin pointed at any other address over plain HTTP ignores it (localhost excepted, for development).
- Earlier logins. A plugin that was signed in before Zest 2 exchanges its old login once for a Zest 2 token and never rewrites the old file, so nobody signs in again.
GitHub App access
- What you grant. When you install the Zest GitHub App, GitHub lists its permissions, all read-only: administration, contents, issues, members, merge queues, metadata, organization administration and pull requests. You pick every repository or only some.
- What Zest uses. Every token Zest asks GitHub for is limited to reading metadata, contents and pull requests. Zest never writes to a repository.
- What it keeps. Pull request titles, authors, branches, states, sizes and times, reviews, comment counts and default-branch commits. Pull request descriptions, comment text and the code around review comments are dropped before anything is stored.
- Linking. An installation links to your workspace only if your own GitHub account can see it and it is not already linked to another workspace. The connect flow uses a signed, single-use state in a cookie, and every webhook is signature-checked.
Remove access at any time from your GitHub organization's settings, or untrack a repository in Zest. Connect GitHub.
Slack access
The Zest Slack app asks for these scopes, to post standups, list channels, match members by
email and answer when mentioned or messaged:
chat:write chat:write.public chat:write.customize channels:read groups:read users:read users:read.email app_mentions:read im:history .
Its bot token is encrypted before it is stored, is never sent to the app or written to a
log, and is dropped the moment Slack reports an uninstall.
Encryption
- In transit. Every connection is HTTPS, and every response sends Strict-Transport-Security. Plugins refuse to send a token over plain HTTP.
- At rest. Zest's index lives in Cloudflare D1 and its content in Cloudflare R2, both encrypted at rest with AES-256-GCM (D1, R2). Integration secrets such as the Slack bot token are also sealed with AES-GCM under a key only the Zest server holds.
Workspace isolation
- Every route checks who you are, except a short public list: the health
check, sign-in, signature-checked webhooks, signed share links and email links, the device
page and the web app's shell. A test walks every route and expects
401from all the others. - Every request checks your membership in the workspace it acts in: an active, unsuspended member with the right role. Ids in a request are checked against that workspace again.
- Storage keys are built on the server. Every stored object sits under
w/{workspace_id}/, from the workspace the server just checked. No route accepts a key, path or URL from a client, and both storage buckets are private. - Share links open with a random token, can be revoked, and show a frozen copy.
- Zest support access needs a second factor every 10 minutes, is read-only, is logged request by request, and shows in your workspace's audit to owners and admins.
- Logs never hold tokens, keys, codes, message text or email addresses.
Redaction
Every plugin redacts on your laptop before anything is queued, and the API redacts again
before anything is stored. Both run the same 89 patterns, and a match is
replaced with [REDACTED] in full. No setting, settings file or repository can
turn one of them off. They cover every text field: prompts, replies, titles, folder names and
metadata.
API keys and access tokens (31)
- API keys and access keys (unquoted)
- JWT tokens
- Zest API keys
- Zest one-time setup codes
- GitHub personal access tokens
- GitHub App installation access tokens
- GitHub OAuth access tokens
- GitHub fine-grained personal access tokens
- GitLab personal access tokens
- Bitbucket app passwords
- Atlassian API tokens
- GitLab runner, deploy, trigger, feed, CI build and SCIM tokens
- Postman API keys
- Bitbucket access tokens
- Meta (Facebook) and Square access tokens
- Mapbox secret tokens
- npm authentication tokens
- Docker Hub personal access tokens
- PyPI API tokens
- Linear API keys
- Notion integration tokens (secret_..., ntn_...)
- Figma personal access tokens
- PostHog personal API keys
- OpenAI API keys
- OpenAI project, service-account and admin API keys
- OpenRouter API keys
- Anthropic API keys
- Truncated Anthropic API keys
- Groq API keys
- xAI API keys
- Hugging Face tokens
Passwords, secrets and auth headers (9)
- Generic secrets and passwords (quoted)
- Generic secrets and passwords (unquoted)
- Unquoted env-style secret assignments (CLOUDFLARE_API_TOKEN=..., SECRET_KEY_BASE=..., SMTP_PASS=...)
- Secret key/value pairs in config lines, CLI flags and query strings
- Authorization Bearer tokens (any case)
- Authorization and API-key header values
- Session and token cookies and parameters (zest.session_token=..., app_session=...)
- Credentials embedded in URLs (scheme://user:pass@host)
- Passwords on command lines (sshpass -p, mysql -p, --password)
Cloud providers (20)
- AWS access key ids (long-term AKIA and temporary STS ASIA)
- AWS secret access keys
- Google OAuth access tokens
- Google OAuth refresh tokens
- HashiCorp Vault tokens
- Databricks access tokens
- Netlify personal access tokens
- Fly.io tokens
- Terraform Cloud / HCP tokens
- Pulumi access tokens
- Firebase API keys
- Google Cloud API keys
- Google OAuth client secrets
- Azure connection-string keys (AccountKey=..., SharedAccessKey=...)
- DigitalOcean personal access tokens
- Doppler tokens (dp.st., dp.pt., dp.ct., dp.sa.)
- Sentry DSN keys
- Vercel access tokens
- Netlify access tokens
- Railway API tokens
Messaging and email services (9)
- Slack API tokens
- Slack incoming-webhook URLs
- Discord bot tokens
- Discord webhook URLs
- Telegram bot tokens
- Twilio account and API key SIDs
- SendGrid API keys
- Mailgun API keys
- Resend API keys
Payments (7)
- Stripe secret keys (live and test)
- Stripe live publishable keys
- Stripe restricted keys (live and test)
- Stripe webhook signing secrets
- Square access tokens
- Shopify access tokens
- Shopify shared secrets
Database credentials (7)
- Supabase personal access tokens
- PlanetScale database passwords
- MongoDB Atlas connection strings
- MongoDB connection strings with credentials
- Supabase service role keys (JWT format)
- Supabase secret API keys
- Database connection strings with credentials
Private keys (2)
- age encryption secret keys
- Private keys in PEM format (with or without the END line)
Personal data (4)
- Email addresses
- Credit card numbers (continuous digits)
- Credit card numbers (with dashes or spaces)
- Social Security Numbers
An aggressive mode adds 24 broader patterns, such as private IP addresses, at the cost of more false matches. Beyond secrets, you decide what is sent: an admin or you can stop collecting prompts or agent replies (Settings → Privacy), and each plugin can ignore a folder or stop syncing. How the data flows.
Retention
Every stored row has an expiry date, and an hourly job deletes what has expired: the stored files first, then the rows. A workspace owner or admin can shorten each class in Settings → Privacy, and you can shorten your own transcripts. Nobody can lengthen one. Shortening deletes older data within the hour.
| Data | Kept | Can shorten to |
|---|---|---|
| Raw uploads What plugins and GitHub send, as received | 30 days | 1 day, 7 days, 14 days |
| Transcripts The text of your prompts and your agents' replies | 30 days | 1 day, 7 days, 14 days |
| Sessions and standups Session cards, timeline entries, standups and invites | 180 days | 30 days, 90 days |
| Daily numbers Daily totals and AI cost records | 400 days | 90 days, 180 days |
| Weekly numbers Weekly totals and your stack's weekly counts | 3 years | 1 year |
Transcripts never outlive their session. The workspace itself, its members, teams, projects, integrations, stack, prompts and reports are kept while the workspace exists.
Deleting your data
Delete your account in the app (Me → Settings → Delete account). It deletes at once your personal workspace and, in shared workspaces, your sessions and transcripts, raw uploads, timeline entries about you, your line in team standups, invites, to-dos, totals, scheduled reports and personal prompts, then your sign-in records. Every plugin token stops working. Delete your account has the steps and the email route.
Sub-processors
Cloudflare · Supabase (hosted on AWS) · OpenRouter · Anthropic, OpenAI and other model providers · Firecrawl · Resend · PostHog · Stripe. What each one does.
How security is tested
- On every change. A smoke test walks every API route without credentials
and expects
401, and tests cover sign-in, webhook signatures and support access. - Before launch. Zest 2 was built against a written baseline of security
rules (2026-11-12), then tested three times on 2026-11-13: the API's authorization and
sign-in flows; the plugins, extension, site and supply chain; and the features finished last.
Each read the code against the rules, ran a two-workspace test where every foreign id must
answer
403or404, and probed production without credentials at low rates. Cross-workspace isolation held in every run. Findings go to a fix round, and the next test checks them again. - Plugins end to end. A run installs every plugin the way a user does, signs in a test account, uploads a session, then deletes the account and counts what is left: no rows and no stored files.
Report a vulnerability
Email support@winding.ai with the subject "Zest security report", the steps to reproduce it and what it exposes. Please test only against your own account and workspace. The same contact is in security.txt.