Whet pixel markWhet

Privacy policy

Your projects stay on your machine by default

The application works offline. It has no account, no telemetry and no analytics, and it goes online only for an action you choose; every such request is named in section 3 with what it carries. The website, the account page and the Early Access list are different: they run on outside services that see your IP address, and they keep what sections 4 and 5 list, including a record of each licensed download request.

1. Who is responsible

The controller of the personal data described here is the seller named on the legal notice, a sole trader established in Hungary, so the EU General Data Protection Regulation (GDPR) and the Hungarian Act CXII of 2011 apply. Write to [email protected] about anything on this page.

No data protection officer is appointed, because Article 37 GDPR does not require one here: the seller is not a public body, and its core activities involve neither regular and systematic monitoring of people on a large scale nor large-scale processing of special categories of data. The address above reaches the person who decides.

2. The application: what stays on 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. The seller cannot see your work, not because of a promise not to look, but because it is never sent.

All of this stays on your disk, in files you can read and delete:

Your licence is checked on your machine by verifying a signature. It is never sent to be checked, because there is nothing to send it to.

3. Everything the application can send, and when

Nothing is sent by default. Each of the requests below happens only when you do the thing named. The list is checked on every build by tools/gates/egress-audit.mjs, which fails if a destination appears in the shipped code that is not on it. That tool reads the source; it cannot see a request made by a component at run time, which is why each row also says what causes it.

Checking for versions, to getwhet.io
Only when you open the version list or run whet updates. Never on a timer, never at start-up. It reads the signed list of released versions. It carries no cookie, no identifier and no licence key. The server sees your IP address and the time, as any website would.
Downloading a version with a licence, to getwhet.io
Only when you ask for a version with whet updates --get or from the version list. A licensed copy sends its licence id, the version, the platform, the time and a signature made from the key. It never sends the key itself. The licence id is what lets the seller confirm that the licence exists; the download service keeps a record of the request for 2 years. Until that service is running, the request is answered "not found" and the file comes from the public link in the signed list. A copy without a licence sends nothing but the request. The file is then fetched from the same host and checked against the signed list before it is saved. Nothing is installed by itself.
Cloud AI models you attach
If you attach a cloud provider with your own API key (Anthropic, OpenAI, Google Gemini, xAI, DeepSeek, Groq, Mistral, Together or OpenRouter), Whet sends that provider the questions you route to it, on your account and under its privacy policy. Listing a provider's models sends your key and nothing else. A provider you have not attached is never contacted. What you send and what comes back never reaches the seller.
The price list, from OpenRouter
A public list of model prices, so Whet can tell you what a cloud model will cost. Fetched when you refresh prices, and at the start of a long run that uses a paid cloud model. It carries no key, no account and none of your content.
Local models
A model running on your machine is reached on your machine's own loopback address and nothing leaves it. When you set up a local model, Whet asks the model runtime you installed (for example Ollama) to download it, and that runtime fetches it from its own registry under its own terms.
Your own machines, over ssh
If you name a second machine for models, solves or renders (the settings models.host, compute.host and render.host), Whet sends that job's files, or the questions for the model, to that machine using the ssh program and keys already on your computer. The files go to a temporary folder there, which Whet deletes after the job. Whet stores the machine's address in your settings and no password or key of its own.
The embedding model, from Hugging Face
Once, and only if you turn on the local embedder: a pinned model file, checked against a built-in hash before use. Hugging Face sees your IP address and which files were asked for.
A web page you ask Whet to check
Only when you give Whet a URL as a source, it fetches that page to compare it with a claim. Addresses on your own machine or network are refused. The site sees your IP address, as if you had opened the link.
Blender
The Blender you installed is started in offline mode and asked for nothing over the network.

Of these, only the version list and the licensed download reach a server the seller runs. The basis for answering them is the contract with you (Article 6(1)(b) GDPR), and for the server's ordinary request logs the seller's legitimate interest in keeping the service working and safe (Article 6(1)(f)). Every other request goes to a party you chose, under that party's terms, and the seller is neither its controller nor its processor.

4. This website

The services behind the website

Cloudflare, Inc., United States
Every request to getwhet.io passes through Cloudflare's network, which terminates the encrypted connection and filters abusive traffic. It sees your IP address and the request. It also runs Turnstile, the check on the sign-in and sign-up forms, and its bot protection can add a script to a page that tells people from automated traffic. Legal basis: the site's legitimate interest in staying up and stopping automated sign-ups and abuse (Article 6(1)(f) GDPR).
Vercel Inc., United States, running in Frankfurt, Germany
Hosts the pages and runs the sign-up function. It sees your IP address and the request. The function passes the address you type to the two services below and keeps nothing itself. It also runs Vercel Web Analytics, which counts page views, the referring page, the country and the type of device and browser, without cookies and without storing your IP address; visits are counted in aggregate and cannot be linked to you. Legal basis: the site's legitimate interest in knowing which pages are read (Article 6(1)(f) GDPR).
Supabase, Inc., United States, database in Frankfurt, Germany
Holds the Early Access list and the short-lived rate limit counts, in the AWS region eu-central-1. Only the sign-up function can read or write them.
Resend, United States, sending from Ireland
Sends the messages of the Early Access list. It keeps a delivery log of each message, including the address, for 30 days on the Free, Pro and Scale plans (Enterprise is negotiable); the figure is for the Free/Pro/Scale plans [https://resend.com/docs/knowledge-base/account-quotas-and-limits]. Open and click tracking are off.

These companies are established outside the EU or may reach data from outside it. The basis for that transfer is Cloudflare: EU standard contractual clauses (Modules 2 and 3), UK Addendum, and EU-US/UK-US/Swiss-US Data Privacy Framework, plus Global CBPR/PRP certification [https://www.cloudflare.com/cloudflare-customer-dpa/]. Vercel: EU-US Data Privacy Framework and standard contractual clauses with UK Addendum [https://vercel.com/legal/dpa, https://vercel.com/legal/privacy-policy]. Supabase (Supabase Pte. Ltd., Singapore): standard contractual clauses with UK and Swiss Addenda; stored and primarily processed in the region the customer selects; no Data Privacy Framework stated in the DPA [https://supabase.com/legal/dpa]. Resend: EU and UK standard contractual clauses and EU-US Data Privacy Framework with UK Extension [https://resend.com/legal/dpa].

The Early Access list

What is stored
Your email address; when you signed up and when you confirmed; the version dates of the terms and of this policy you agreed to; the name of the form; and a salted hash of your IP address, never the address itself. Nothing else: no name, no country, no record of what you opened.
For rate limiting
A salted hash of your IP address and one of your email address, each with the time of the attempt. Deleted within a day.
Why, and on what basis
To send three messages and no more: one asking you to confirm the address, one saying it is confirmed, and one on the day Early Access opens. The basis is your consent, given with the tick on the form (Article 6(1)(a) GDPR). Withdraw it at any time with the link in each message.
How long
An address whose confirmation link is never opened gets no further message and is deleted after 30 days. A confirmed address is kept for 12 months, or until the person unsubscribes, whichever is first after Early Access opens, and then the whole list is deleted. The link in any message, or an email to [email protected], deletes your record at once.
The beta application
The beta form on the Early Access page also stores your operating system and one optional line about what you build. We reply by email; the requirements of the programme and any questionnaire are sent to the testers we pick, not collected here.
What it is not
Not a newsletter, not a marketing list and not a profile. Signing up buys, reserves and unlocks nothing.

5. Buying a licence

When the checkout is open, payment is handled by Creem as merchant of record. Creem collects your payment details and billing address as an independent controller, under its own privacy policy: https://www.creem.io/privacy [https://www.creem.io/privacy]. The seller never sees your card.

The seller receives and keeps:

The basis is the contract with you (Article 6(1)(b) GDPR) and, for invoices, a legal obligation (Article 6(1)(c)). For a seat bought by an organisation, the basis for the named person's data is the seller's and the organisation's legitimate interest in issuing and administering the licence the organisation bought (Article 6(1)(f)); the organisation tells its people that it has given their name and address. Nothing is sold, shared for advertising, or used to build a profile.

The account page and licence emails

What is stored
When Creem confirms a purchase, the order is recorded in the account database (Supabase, Frankfurt, described in section 4): your email address, the licensee name, the order number, the product, the seats, the purchase date, the licence ids and, once issued, the key in sealed form. Signing in to the account page stores a one-time sign-in link, valid for minutes, and a session, valid for 12 hours. Each purchase, issue, withdrawal and sign-in is logged against the account.
Who sends the emails
The sign-in links and the account messages are sent through Resend, described in section 4. Open and click tracking are off. The licence key is never sent by email: you download the licence file from the account page, signed in.
How long
For as long as the licence exists, because the licence is perpetual and a lost licence file can be downloaded again from the account page at any time. You may ask for the record to be deleted; after that, the licence file can no longer be downloaded from it.

The student price

To give the student price, the seller processes only the university email address you write from and your request, to check that you are a student and to send you the discount code. Nothing else is asked: no student card and no document. They are kept as long as the sale records.

Support email

Mail to [email protected] is received and stored in Google Workspace, provided in the EEA by Google Ireland Limited, which acts as the seller's processor under its data processing terms. Google may process data outside the EEA under standard contractual clauses and the EU-US Data Privacy Framework.

Organisations

Whet itself processes no personal data on the seller's behalf, so using it does not make the seller anyone's processor. If an organisation sends the seller personal data for support, for example a model or a log that names its staff, the seller handles it only to answer the request, and the organisation can adopt the data processing terms for it.

6. Your rights

You may ask for a copy of what is held about you, have it corrected, have it deleted, receive it in a portable form, restrict or object to its use, and withdraw a consent at any time. Write to [email protected]. There is no form and no account. The answer comes within one month, as the GDPR requires.

Two limits, stated now rather than found later:

No decision about you is made by automated means alone, and nothing on the website or in the application is directed at children.

You may complain to the Hungarian authority, the Nemzeti Adatvedelmi es Informacioszabadsag Hatosag (NAIH, 1055 Budapest, Falk Miksa utca 9-11, [email protected], naih.hu), or to the data protection authority where you live, and you may go to court.

What Whet made on your machine is already yours to copy or delete without asking anybody.

7. Security research

If you find Whet doing something this page does not say, please write to [email protected]. No legal action will be taken against good faith security research. You may observe, study and test how Whet behaves, including what it sends over the network, as the terms and the law allow. The security overview says how reports are handled.

8. Changes and change log

If the facts change, this page changes first, with a new date, and the earlier version stays readable at its own address. If the application ever gains a new destination, it is named here and in the release notes of the version that adds it.

This version was published on 2026-10-31.