Privacy Policy
Last updated: November 13, 2026
Introduction
This Privacy Policy explains how Zest (the "Service") collects, uses, and protects information when you use our
products: the Zest installer (npx @winding-labs/zest), the Zest plugins for coding agents (such as Claude
Code, Codex, Cursor, Hermes and Grok Build), the VS Code extension, the Zest apps for iOS, Android and the web
(meetzest.com/app), and our websites. Zest is made by Winding Labs.
Information We Collect
General Data Collection
- Account information: such as your name, email address, profile picture and workspace details, and the sign-in provider you chose (email code, GitHub, Google or Apple).
- Usage data: interactions with the Service, device information, diagnostics, and logs.
- Content: data you provide through the Service (for example, questions you ask Zest, posts on a timeline, cards you pin) as necessary to operate features.
- Cookies and similar technologies: to keep you signed in, remember preferences and analyze usage.
Coding-agent sessions
When you connect a coding agent, its Zest plugin or extension sends the events of each session: your prompts and the agent's replies, the model, token counts, the skills, MCP servers and tool calls it used, timings, and the repository and branch it worked in. Secrets such as API keys, tokens and passwords are redacted on your machine before anything is sent. Zest collects no code diffs. You can pause syncing, ignore a folder, or sign out of a plugin at any time.
GitHub
When a workspace installs the Zest GitHub App, Zest reads pull requests, commits, reviews, checks and their metadata for the repositories you pick. It never writes to your code.
The phone apps
The iOS and Android apps show the same workspace as the web app. If you allow notifications, we keep your device's push token to send your standups and the alerts you turned on. The apps do not sell anything: plans are bought on the web.
Earlier Zest extensions
The Zest Chrome extension and the Zest Claude Desktop extension (MCPB) are no longer distributed. Legacy installations used tab URLs and metadata, locally stored sign-in tokens and preferences, and content you chose to capture (Chrome), or messages, tool uses and session metadata from Claude Desktop's local audit log for sessions started after login (Claude Desktop), with the same on-device redaction. You can remove either one from your browser or from Claude Desktop at any time.
How We Use Information
- To provide, maintain, and improve the Service: your standups, levels, rings, team views and answers.
- To personalize experiences and develop new features.
- To communicate with you, including standups you subscribed to, service updates and security alerts.
- To ensure security, prevent abuse, and comply with legal obligations.
Summaries, standups and answers are written by AI models from your workspace's own data. No customer data is used to train AI models.
Legal Bases for Processing
Where applicable, we process personal data under legal bases such as performance of a contract, legitimate interests, consent, and compliance with legal obligations.
Where Data Is Stored
Zest runs on Cloudflare. Account and index data (who, which workspace, what happened when) lives in a Cloudflare D1 database; raw session payloads and transcripts live in private Cloudflare R2 storage, under keys the server builds from your workspace, so one workspace can never read another's. Data is encrypted in transit and at rest.
Sharing of Information
We share information with trusted service providers who assist in operating the Service, subject to contractual safeguards. We do not sell personal data. Leaderboards and named comparisons stay inside your workspace; Bench compares you with other companies only in anonymized totals.
Third-Party Services
- Cloudflare: We use Cloudflare to run Zest: our website, apps and APIs run on its Workers, account and index data live in its D1 database, session payloads and transcripts in private R2 storage, and it sends our email.
- Supabase (hosted on AWS): The earlier version of Zest stored data with Supabase. We read it once to move each workspace to Zest 2, and delete it when the move is finished.
- OpenRouter: We use OpenRouter to reach the large language models that write standups, answers and reports from your coding activity.
- Anthropic, OpenAI and other model providers: Model providers reached through OpenRouter. Your data is not used to train their models.
- Firecrawl: We use Firecrawl when Ask Zest searches or reads public web pages; it receives the search query, not your workspace data.
- Resend: We use Resend to send transactional email, such as account, standup, and notification messages, when Cloudflare's email service is unavailable.
- PostHog: We use PostHog for analytics to understand how users interact with our Service and improve functionality. Analytics data is aggregated and used solely for product improvement.
- Stripe: We use Stripe for billing and payment processing.
These service providers have access only to information necessary to perform their functions and are obligated to maintain confidentiality and security. The current list, including which providers process data originating from Slack, is maintained on our Sub-processors page.
Payments
Paid plans are bought on the web through Stripe (card, Apple Pay, Google Pay or Link). Your card details go to Stripe and never reach our servers; we keep the plan, its status and Stripe's customer and subscription ids.
Website analytics and advertising measurement
Our website measures visits and sign-ups with PostHog, Google Analytics and Ahrefs, and measures our ads with the Google Ads tag and the Meta pixel (Facebook and Instagram). The Meta pixel tells Meta when you view a page and when you finish signing up, and keeps a random browser id in a cookie (_fbp) and, if you came from one of our Meta ads, which ad that was (_fbc). In the Zest app, the Google Ads tag and the Meta pixel load only in its web version, and only right after you create your account, to report that sign-up; the iOS and Android apps load no advertising pixels.
When you sign up in a web browser, our server also reports the sign-up itself: to Google Analytics with its cookie id, and to Meta with a one-way hash of the email address and of the account id, your browser type (user agent), the page address without its query string, and those two cookies, so Meta can tell us which ads worked. Our server sends neither of them your IP address. If you came from one of our Google ads, we keep the ad click id (gclid) and the campaign with your sign-up and tell Google Ads which click led to a sign-up (and to a first connected coding agent), and when.
We honour Global Privacy Control: when your browser sends it, our website and the web app load no advertising pixels and we send no sign-up event to ad networks. You can also manage the ads Meta and Google show you in their ad settings.
Data Retention
We keep each kind of data only as long as the Service uses it, then delete it automatically:
| Data | Kept for |
|---|---|
| Raw logs (the session events your agents send, as received) | 30 days |
| Analyzed data (sessions, standup cards, timeline entries) | 180 days |
| Daily rollups (per-day totals behind the charts) | 400 days |
| Weekly rollups (per-week totals, levels and trends) | 3 years |
A workspace can change these in its settings. Storage deletes on a schedule, so "30 days" can mean up to 31. When a workspace leaves Zest, its raw data is deleted right away and the rest on the schedule above. Account details are kept while your account exists; billing records are kept as long as tax law requires.
Your Rights and Choices
- Access, correct, or delete your personal information.
- Object to or restrict processing in certain circumstances.
- Withdraw consent where processing is based on consent.
- Portability of certain data, where applicable.
You can delete your account yourself in the app or ask us by email: how to delete your account.
Security
We implement appropriate technical and organizational measures to protect information, recognizing that no system is completely secure.
International Transfers
Information may be processed in countries other than your own. Where required, we use appropriate safeguards for cross-border data transfers.
Children’s Privacy
The Service is not directed to children under the age where parental consent is required by law. We do not knowingly collect personal information from such children.
Changes to This Policy
We may update this Privacy Policy from time to time. If changes materially affect your rights, we will provide notice where required. Your continued use after changes take effect constitutes acceptance.
Contact
For privacy questions or requests, contact hi@winding.ai.