Privacy policy
Weft is open-source software (the @celador/weft CLI, its agent adapters, the Claude Code and Copilot CLI plugin, the VS Code extension and the gateway) plus an optional hosted gateway. By default Weft runs on your machine and sends nothing to us. This page says what each part sends, what the hosted gateway stores, for how long, and how to delete it. In short: Weft handles code-coordination data, not personal data. We don't sell it, show ads, or use it to train models.
What the plugin and the CLI send
The plugin's hooks do nothing, and send nothing, in a repository that Weft hasn't been set up in (no .weft/ folder). In a checkout set up with npx @celador/weft or /weft:setup, the Weft adapter sends this to the gateway that checkout is configured to use, and nowhere else. By default that gateway runs on your own machine, so none of this leaves it:
- for each edit an agent makes: the repo-relative file path, a unified diff of the change (left out when it is larger than about 900 KB), and the names of the code symbols (functions, classes, types) it reads and writes;
- the agent's id in the space (for example
claude-a), the harness it runs in (for exampleclaude-code), and its task and change ids and task title; - git commit hashes when the agent commits, and the coordination messages agents send each other (claims, negotiations, notes);
- when a space is created: the repository's folder name, used as the repo's name in the space.
Weft does not send your prompts, the agent's conversation, files the agent didn't edit, environment variables or credentials. The CLI, the plugin, the adapters and the VS Code extension contain no telemetry or analytics. Running npx downloads the CLI from the npm registry, which is covered by npm's own privacy policy.
The hosted gateway (opt-in)
Only if you choose it (npx @celador/weft --hosted or npx @celador/weft use hosted), or if you already had a hosted space before local became the default, the CLI uses the hosted gateway at weft-hosted.elier.ai. It runs on Cloudflare Workers and stores data in Cloudflare Durable Objects (SQLite storage) in Weft's Cloudflare account. Cloudflare is our only hosting provider. It stores:
- your space: a random id, the repo names in it and the time it was created. The space stores no IP address and no value derived from one;
- signup counters: to limit how many spaces one network can create per day, the gateway counts new spaces under a keyed hash of the network (IP) address that rotates daily, so one day's counters can't be linked to another's. The counters are deleted after 48 hours;
- activity counts: to tell whether a space is still in use, the gateway keeps, per space, the time of its latest event and how many events it sent on each UTC day. These are numbers only: no IP address, no repo name, no file path and no content. Day counts older than 90 days are deleted, and deleting your space deletes its counts;
- keys: only SHA-256 hashes of the space's keys. The keys themselves stay on your machine (
~/.config/weft/and each checkout's git-ignored.weft/); - each repo's event log: the edits, diffs, symbol names and messages listed above, in order.
There is no account or login, and the gateway stores no email address. Only someone holding one of your space's keys, or a browser or phone you paired with a one-time code, can read the space. The feed address has no key in it; a paired device holds a session that expires after a week of not being used, and you can unpair it at any time with npx @celador/weft viewers.
Billing (only if you buy Pro). Free needs no payment details. When you buy Pro, Stripe Checkout collects your email address, your card and any billing details it asks for; Stripe stores them as our payment processor, and Weft never sees the card. A purchase started on weft.mx carries the page's utm_* tags (for example, which video you came from) into the Checkout, and Stripe keeps them with it. The gateway stores, for a purchase: the Checkout session id, the Stripe customer and subscription ids, the plan, the billing period, the number of users, a salted hash of the one-time claim code (never the code itself), whether it has been claimed and, once claimed, which space has Pro. For every space it also keeps a monthly event count, which shows whether a Pro space is within fair use. It sends Stripe no code, path or repo name. Erasing a space cancels its subscription first and keeps nothing but the tombstone described below. Stripe keeps its own records of past invoices as the law requires.
How long: the event log and the space are kept until you erase the space. They don't expire on their own, so expect them to be kept for more than 30 days unless you erase them. Signup rate-limit counters use a daily-rotating keyed hash of the network address and are deleted after 48 hours. Activity counts are deleted after 90 days. Cloudflare keeps the gateway's operational request logs for a few days for debugging.
Deleting your space: run npx @celador/weft uninstall --space in the repo (it asks first; --yes skips the question). This erases the space immediately and for good:
- deleted at once: every repo's stored event log (the edits, diffs, symbol names, intents, transcript pointers and messages), the repo names, the space's keys and their hashes, the space's label and its activity counts. The storage of each repo is deleted from Cloudflare Durable Objects as part of the request, not on a schedule. If a repo can't be erased on the first try, the space is already unreachable and the erase is retried every minute until it is done;
- irreversible: there is no undo, grace period or backup on our side. Asking us to restore an erased space is not possible;
- what remains: a tombstone with the space id, the time it was erased and the day it was created, with no content. It lets a second erase request give the same answer and keeps the count of new spaces per day correct. Cloudflare documents point-in-time recovery for Durable Object storage over the last 30 days; Weft's code never uses it, and we can't promise that nothing is left inside Cloudflare's systems for up to 30 days after an erase;
- on your machine: the command also removes
.weft/space-tokenand the space from~/.config/weft/cli.json.
The same erase happens if the space's owner key calls DELETE /v1/space directly. A space that was already marked deleted by an earlier version of the gateway is erased the same way when the new version starts. If you have lost your keys, email john@elier.ai with the space id (shown by npx @celador/weft status) and we erase it for you.
The gateway on your machine, or your own
By default (npx @celador/weft; --local means the same) the gateway runs on your machine, and with npx @celador/weft deploy it runs in your own Cloudflare account. In both cases the data stays with you: Weft (the operator) receives none of it.
This website
weft.mx uses Cloudflare Web Analytics, which counts page views without cookies. When you view a page, copy the install command, click Get Pro on the pricing page, or come back from Stripe Checkout, the page also records an anonymous event in Cloudflare Workers Analytics Engine: the event name, where it happened, the referring site or utm_source, the utm_campaign, and which command was shown. To count a buy click for the campaign you came from, the page keeps those tags in your browser tab's sessionStorage, which the browser clears when you close the tab; it is not a cookie, and it leaves the browser only in these events and in the Get Pro link. No cookies, no IP address, no user agent, no identifiers.
The page you land on after paying (/welcome/) reads the Checkout session id from its address, removes it from the address bar (keeping it in the tab's sessionStorage so a reload still works), and sends it to the hosted gateway once to fetch your claim code. That page loads no analytics script and sends no referrer. The site has no forms and no accounts.
Children
Weft is a developer tool and is not intended for anyone under 18.
Changes and contact
If this policy changes, we update this page and its effective date; the history is public in the repository. Questions or requests: john@elier.ai.