Archived text. This is the privacy policy as published on 2026-09-10. It is kept here word for word so that anyone who read or agreed to it can still read it. It does not apply to anything done on or after 2026-09-30; the current version is here.
Privacy policy
No servers, no analytics, no account
This policy is written to be checked rather than believed. Every network request Whet can make is named below, with what causes it and what it carries. Point a packet capture at the application and this page should match what you see. If it does not, that is a defect in this page and it will be fixed.
This website
- No cookies are set, of any kind, including the ones usually called essential. There is nothing to consent to and therefore no banner.
- No analytics, no tag manager, no pixel, no session recorder, no heat map.
- No fonts, scripts, images or stylesheets are loaded from another server. Everything a page needs comes from this domain, so no third party learns that you visited. The site ships no JavaScript at all, which you can confirm with view source.
- No contact form and no account. One page asks you for one thing: the Early Access page has a field for an email address, and it is the only field on this site. Every other page holds nothing back and asks for nothing.
- The web server keeps ordinary access logs, which include your IP address, for Vercel, Pro plan: runtime logs are kept 1 day; 30 days only if the paid Observability Plus add-on is enabled [https://vercel.com/docs/logs/runtime, page dated 2026-08-28]. They exist to keep the site up and are used for nothing else.
The one field: the Early Access list
Until 2026-09-10 this page said there was no email capture and no waiting list anywhere on the site. That became untrue the moment an Early Access sign-up was written, so it is corrected here rather than left to be found. This is the whole of what that field does.
- What is stored
- Your email address and the date it arrived. Nothing else: no name, no country, no company, no page you came from, no record of what you opened. There is no tracking pixel in any message sent to it.
- Why
- To send two messages and no more. One when the address is added, so that you can confirm it works and so that nobody can add you to a list you did not ask for. One on the day Early Access opens.
- How long
- Until Early Access opens, and then for the period stated on the Early Access page, which is where that number is written down. Before then, one email to [email protected] removes you on the day it is read, with no account to log into and no question asked.
- Who else holds it
- A form on this site is plain HTML posting to a named service, because the site ships no JavaScript. Today no service has been named, so the field is not live, no address has been collected, and there is nothing for this section to name. When one is chosen, its name, its country and the basis for any transfer outside the EU are written here, on this page, before the field is switched on.
- What it is not
- Not a newsletter, not a marketing list, not a profile, and not a thing that unlocks anything. Every price, every limit and every measured figure on this site is published to a reader who never gives an address.
The application: what never leaves your machine
Whet has no server of its own to report to. There is no account, no login, no telemetry, no analytics and no crash reporting. Your code cannot be seen by the seller, not because of a promise not to look, but because it is never sent anywhere.
That sentence was measured, and here is exactly how far the measurement reaches
On 2026-08-10 the packaged Linux build was watched on the wire from a cold start: a fresh profile, a fresh data directory, every screen under all four tabs clicked, eight minutes of untouched idle, and a graceful quit. Across the whole run the application's process tree made zero connect and zero sendto calls of any kind. No packets, no DNS query, not even to the local resolver. The app spawned its daemon and nine further engine processes during that run and not one of them opened a socket.
Now the limits, which are real and are not a formality. This was Linux, and it was the case where you ask the software for nothing. None of the allowlisted destinations was exercised, so it says nothing about whether each behaves as described once you switch it on. The Windows and macOS builds are unmeasured, and macOS is where the code that silences the spellchecker takes a path this capture never ran.
The reason that capture was run at all is that the same method caught us out earlier the same day: the packaged build was contacting Google 0.54 seconds after launch and pulling down a 451,968-byte Chromium spellcheck dictionary, which no scan of our own source could ever have seen because the request was Chromium's, not ours. It was fixed and re-measured, and the second measurement is the one quoted above. Source: Packet capture of the packaged Linux build, tcpdump plus a per-PID connect and sendto tracer plus the DevTools network log. Measured 2026-08-10.
All of this stays on your disk, in files you own, in open formats you can read, in one folder you can delete without asking anyone:
- your source code, your diffs and your git repositories, which Whet reads in place and never copies out;
- your AI agents' session transcripts, read in place, never uploaded;
- the claims extracted from them, the evidence, and the verdicts;
- the event log of everything Whet did;
- the vault, meaning your project memory and notes;
- the local index, your settings, your guard rules and your checkpoints;
- your licence key, and the record that you accepted the terms;
- the local embedding model, once downloaded, and any page the verifier fetched and cached.
Your licence is verified offline. The key carries a signature that is checked by arithmetic on your own machine. It is never sent to a server, because there is no licence server to send it to.
Every outbound request the application can make
Six kinds of request, and this is how they are counted, because a count is worthless without the rule behind it. Twelve hostnames are written into the shipped code. One is the update check, one the local matching model, one the price list, nine are AI providers you can configure with your own key, and one is your own machine. That is thirteen roles for twelve names, because openrouter.ai does two jobs: the anonymous price list, and a provider like the others if you give it a key. The sixth kind has no fixed host at all, because its destination is whatever URL you hand the verifier.
Until 2026-09-02 this page said eight hostnames and four AI providers. The code held nine providers: rows for Groq, Mistral, Together and Google Gemini had been added to the endpoint table and were named on no page here. Nothing was ever contacted that you had not asked for, because each of those is reached only when its own key variable is set and there is no key to set unless you go and get one. But the list you were handed to check against was short by four, and an incomplete list of what a machine may contact is not a smaller promise, it is an uncheckable one. What changed with the wording is that the audit now reads the provider rows out of the table the code iterates instead of being told about them separately, so this page cannot fall four behind that table again.
The tool that produces that list is node tools/gates/egress-audit.mjs. It runs on every build and fails if a destination appears that is not on this list, so this page cannot quietly fall behind the source. Two things it is not. It is a text scan of the source tree, not an observation of a running program, so it cannot see a request made by the Electron runtime, by a bundled dependency, or by an address assembled at runtime. It also prints its own blind spots on every run rather than leaving you to guess them. What can answer the question it cannot is a packet capture, and the section below is one.
The twelve hostnames, and where each one is written
Named, rather than counted. This is the list the audit prints, with the file each host is written in.
- getwhet.io
- The update check, and only when you run it. It reads the list of released versions to say whether a newer build exists.
- huggingface.co
- The weights for the local matching model. Once, and only if you opt in. Written in packages/core/src/weights.ts, pinned to one commit, and every file checked against a built-in hash before it is loaded.
- openrouter.ai
- The model price list, so Whet can say what your agents cost. No key, no account, none of your content. The same host is also one of the nine providers below, which is a different request with a different payload: set OPENROUTER_API_KEY and it is contacted with that key as well.
- api.anthropic.com, api.openai.com, api.deepseek.com, api.x.ai, api.groq.com, api.mistral.ai, api.together.xyz, generativelanguage.googleapis.com, openrouter.ai
- The nine provider endpoints you can configure with your own key. Written in packages/models/src/discover.ts, with four of the base addresses in packages/models/src/registry.ts. Each is contacted only when its own variable is set: ANTHROPIC_API_KEY, OPENAI_API_KEY, DEEPSEEK_API_KEY, XAI_API_KEY, GROQ_API_KEY, MISTRAL_API_KEY, TOGETHER_API_KEY, GEMINI_API_KEY, OPENROUTER_API_KEY. Set none and none of the nine is ever contacted.
- localhost, ports 11434, 1234, 8080, 8000 and 1337
- Ollama, LM Studio, llama.cpp, vLLM and Jan, on your own machine. It is on the list because it is a hostname in the code, not because anything leaves. One exception is stated under heading 5: if you run whet models discover --host with the name of another machine, those same probes go to the machine you named.
Twelve hosts. The last row the audit prints is not a host at all: it is whatever URL you or your agent handed the verifier. A thirteenth hostname does appear in the shipped files and is not a destination: www.creem.io, in the legal text the application shows you, because the refund policy names Creem as the merchant of record and links its buyer terms. It is a sentence in a document. Nothing fetches it, and it is not on the list of things this software contacts.
The audit is a gate in the build, not a report. A host literal in shipped code that is not on that list fails it, and the provider part of that list is read out of the source rather than typed beside it, so a tenth provider added to the code declares itself here or the build stops. Two literals are exempt and the audit prints both on every run rather than hiding them. packages/verify/src/counts.ts holds the npm registry address inside a startsWith, so the counting reader can answer whether every entry in a lockfile resolves to the public registry; that address is compared against, never fetched. And the legal text file quotes Creem's buyer terms address, described above. Each exemption is pinned to that address in that file, so the same address written anywhere else still fails the gate.
The scripts under tools/ reach further than the twelve, to the npm registry, to a NASA demo endpoint and to the OpenXML schema addresses. None of them is packaged, so none of them runs on a machine that bought Whet. The audit prints them anyway instead of filtering them out.
1. The update check, to this site
Only when you run the update check yourself. Never on a timer, never at startup, never in the background. It reads a list of released versions. It carries no cookie, no identifier, no licence key and no header saying when you last checked, because that last one would turn a one-off request into a usage pattern. The application prints what it is about to send before it sends it, which is nothing about you. The host sees your IP address and the time, as any website would. If you never run that command, the application never contacts this site at all.
2. The local embedding model, from Hugging Face
A one-time download, and only if you opt in to the embedder. The model is pinned to one specific commit and every file is checked against a built-in checksum list before it is used, so a substituted or corrupted file is refused rather than loaded. Hugging Face sees your IP address and which files you asked for. It receives nothing about you and nothing about your code. Once the model is on disk it runs locally and the request never happens again. Whet works without it.
3. The model price list, from OpenRouter
A public list of models and their prices, so Whet can tell you what your agents are costing you. No API key, no account, no identifier, and none of your content. If you have also given Whet an OpenRouter key, that is a separate request under heading 4 and it does carry the key. It happens when you refresh prices yourself, and also on its own when you start a marathon run, before the cost governor begins metering. That second case is narrower than it sounds and the narrowing is in the code rather than in this sentence: it only happens when the run uses a paid cloud model, because a run made entirely of local models has nothing to meter, and reaching a price server from one would break the promise that a local run makes no outbound connection.
- That second one is the only request in the whole product that you did not name yourself, which is exactly why it is called out rather than left in a footnote. It is best effort: if it fails, cached and built-in prices apply and the run carries on. Whet works offline.
4. AI providers you configured, with your own key
If you set up a cloud model with your own API key and ask Whet to use it, the text of that request goes to that provider, under their privacy policy, on your account and your key. That relationship is yours and the seller is not in it: nothing comes back to the seller and nobody here sees what you sent or what came back. Whet never picks a provider you have not configured and never sends anything to one on its own. Configure none and none is ever contacted.
There are nine of them and there is one other request they receive, which is not a prompt. Run whet models survey and Whet asks each endpoint whose key variable is set which models it offers: one GET, carrying that key in its header and nothing else. No prompt, no code, no filename, no identifier. An endpoint whose variable is unset is not contacted at all, which is why the command prints the ones it skipped and why setting a key in a shell profile does not affect an application launched from the desktop. Sending an actual prompt is a separate deliberate act, and the one command that exists to do it, whet models prove, prices the call and refuses to spend anything without --yes.
5. Local model runtimes, on your own computer
If you run a local model, Whet talks to it on the loopback address of your own machine, and the discovery probe knocks on five ports there: 11434 for Ollama, 1234 for LM Studio, 8080 for llama.cpp, 8000 for vLLM and 1337 for Jan. It does not leave the machine and it does not touch the internet.
One exception, and it is yours to cause: whet models discover --host <machine> sends those same five probes to the machine you name, which is how a homelab box or a machine on your Tailnet gets found. It goes where you typed and nowhere else, and the address ends up in your own event log.
6. A source URL an agent cited, when you ask Whet to check it
When an agent says a page supports its claim, Whet fetches that page to see whether it says what the agent said it says. Only the URL that was cited, nothing else. Nothing about your code goes in the request. The site you fetch sees your IP address, as it would if you had clicked the link yourself. Every fetch is written to your own event log with the address, the time and the claim that caused it.
What the fetcher refuses
A cited URL is an instruction from something that may be lying to you, so it is treated as one.
- Addresses on your own machine or your own network are refused: loopback, private ranges, link-local, carrier-grade ranges, and names that always mean here, including .local, .internal, .home.arpa and hostnames on a private mesh.
- The name is resolved and the refusal is applied again to the address it resolves to, so a public hostname pointing at an internal machine does not get through.
- Anything that is not plain HTTP or HTTPS is refused.
- A redirect from HTTPS down to unencrypted HTTP is refused, because anyone on the network could rewrite it.
- Redirects are followed at most three times, the request times out, and the response is read only up to a fixed size.
- If you set an allowed-hosts list, anything outside it is refused as well.
Every refusal is written to your log with the reason.
Telemetry, and the log
- There is none
- No usage statistics, anonymous or otherwise. No crash reports. No error reporter, no session recorder, no licence server, no beacon. There is no setting to switch off, because there is nothing running to switch off.
- The log is tamper evident
- Each entry carries the fingerprint of the entry before it, so an edited log does not read as a clean one. That is aimed at anyone with access to your machine, and it includes the seller. How far it reaches, and where it stops, is set out below.
- Taking your data out
- One command copies everything Whet holds about your work into a readable export, at any time, with nobody's permission. Deleting it is deleting a folder.
What tamper evident means here, and what it does not mean
The log is one JSON object per line. Every line after the first carries a field called prev, holding the SHA-256 of the whole line before it. Next to the log sits a small anchor file with two values in it: how many entries the record held, and the hash of the last one.
Checking the log replays those hashes from the top. There are four answers.
- Every entry links and the last hash is the anchor's. Nothing was changed, removed or truncated.
- An entry does not match the one before it. The check names the entry by number and stops there, and says that everything after that point is untrustworthy.
- Fewer entries than the anchor counted. It says how many are gone.
- The right number of entries, but the last hash is not the anchor's. Entries were removed from the end, or replaced.
Entries written before this protection existed carry no prev. They are counted on their own and reported as unprotected, rather than counted in with the ones that verified.
Now the limit, which matters more than the mechanism. The anchor is an ordinary JSON file on the same disk as the log. It is not signed and it is not sent anywhere, because there is nowhere to send it. Anyone who can rewrite the log can rewrite the anchor and recompute every hash in between. So this catches an edit, a deletion and a truncation, which is what an accident and a careless hand both look like. It does not stop someone with write access to your machine from rebuilding the whole record. Tamper evident is not tamper proof, and we are not going to use the second word.
One more. The log rotates once it passes fifty megabytes: the old file is renamed and a new chain starts from nothing. The check reads the current log only, so it says nothing about a rotated file.
What is held about you as a customer
Buying a licence creates a small amount of ordinary commercial data. This is the complete list.
- Your name, because it is inside your licence key and it goes on the invoice.
- Your email address, to send you your key, resend it if you lose it, and answer support.
- The record that a licence was issued to you, and when.
- Invoices and payment records, kept for as long as Hungarian accounting law requires them to be kept.
- Support emails you send, because you sent them.
Card details are never seen by the seller. Payment is handled by Creem as merchant of record and the card data goes to Creem, which is a separate and independent controller for it. No profile is built, no behavioural data is collected, and nothing is sold or shared for advertising, ever.
Your rights
The seller is established in Hungary, in the European Union, so the General Data Protection Regulation applies. You may ask for a copy of what is held about you, ask for it to be corrected, ask for it to be deleted, ask for it in a portable form, object to processing, and complain to your national data protection authority or to the Hungarian one.
Most of this resolves quickly, because there is so little of it. An access request returns your name, your email address, the fact that a licence was issued and when, your invoices, and any support emails. That is the whole file. Everything Whet produced is already on your own disk and you can export or delete it without involving anybody.
Two limits on erasure are worth stating rather than letting you discover them:
- Invoices cannot be deleted on request. Hungarian accounting law requires them to be kept and data protection law lets that obligation win. Everything else gets deleted.
- Your name is inside your licence key, which is signed and lives on your machine. The seller's copy of your name can be deleted. A key that has already been issued cannot be reached into and cannot be un-signed. That is the same property that makes your licence work forever without a server, and it is a fair trade, but it should be disclosed rather than found out.
Requests go to [email protected] from the address you bought with. There is no form and no account to log into, so there is no dark pattern between you and a deletion request. An answer comes within one month, as the Regulation requires.
Security research
If you find something in Whet that contradicts this page, that is the most useful email anyone can send. No legal action will be taken against good faith security research, and the licence expressly permits you to take the software apart and look at it, including the licensing code.
Changes to this policy
If the facts change, this page changes with them, dated, with the previous wording kept readable. In particular, if the list of network destinations above ever grows, it will be said at the top of this page, noted in the release notes of the version that introduces it, and it will not be done quietly. The whole product depends on this document being checkable.
One detail on this page is marked as unsupplied and is shown as a gap rather than guessed at.
This version was published on 2026-09-10. It changed one thing from the version of 2026-08-09, and the old wording is quoted where the change was made: the line saying this site had no email capture and no waiting list anywhere, which an Early Access sign-up made untrue. The section headed The one field states what the sign-up does instead. Nothing in the list of network destinations moved.