Legal

Privacy Policy

Last updated 24 July 2026

Eaon is made by one independent developer. This policy is written to describe what the software actually does, in plain language, rather than to cover every hypothetical. If something here is unclear or looks wrong, email support@eaon.dev and it will be fixed.

1. What this policy covers

Three separate things carry the Eaon name, and they handle data differently:

• This website (eaon.dev), including the pages you are reading now.
• The Eaon API and Eaon Studio (api.eaon.dev and eaon.dev/tokenmaxxinglol), which route chat requests to AI models and include an optional account system.
• The Eaon desktop app for macOS and Windows, which runs on your own computer.

Each is described separately below, because what applies to one often does not apply to another.

2. This website

The marketing pages on eaon.dev set no cookies, use no local storage, and load no analytics or advertising scripts. We do not build a profile of you and we cannot identify you from visiting.

The download counter

When you click a download link, your browser sends a short signal to our API noting which installer was chosen. What gets written down is exactly two things: the asset name (for example mac or windows) and a timestamp. That is the entire record. It contains no IP address, no browser fingerprint, no cookie and no identifier of any kind, which means the total shown on the site is a real count of downloads but is not traceable back to any individual.

Third parties your browser contacts

Some parts of the page are served by other companies. Any time your browser requests a file from another company's server, that company necessarily sees your IP address and basic request details, because that is how the web works. On this site those are:

• Fontshare and Google Fonts, which serve the typefaces the site uses.
• Simple Icons (cdn.simpleicons.org), which serves a few of the model maker logos.
• Discord, which the page asks directly for the live member count shown in the footer.
• Cloudflare, which hosts and serves this site.

GitHub and Ko-fi are only contacted if you actually click through to them. None of these companies are given any information about you by us; they simply see the request your browser makes.

3. The Eaon API and Eaon Studio

Accounts

You do not need an account to use the free Instant tier. If you create one to reach the higher tiers, the sign-up is handled by Appwrite, which stores your email address, your password (hashed by them, never visible to us in readable form) and an optional display name. You can instead sign in with GitHub, Discord or Google, in which case that provider confirms your identity to us and we receive the basic account details they choose to share.

In our own database, the record attached to your account is deliberately thin. It holds an internal user ID, which plan you are on, a few flags recording whether an upgrade has been applied, and optionally your timezone. Your email address is not copied into it.

API keys

If you create an API key, we store the key itself along with the name you gave it, the account it belongs to, a count of how many times it has been used, when it was last used and when it was created. We need the key on our side in order to recognise it when a request arrives. Treat an API key like a password: anyone holding it can spend your quota, so do not share or publish it. You can delete a key at any time from the dashboard, which removes it permanently.

Your prompts and the replies (please read this part)

This is the most important thing in this document. Eaon does not train on your data and does not keep your conversations on its servers. But it is a router, and routing means your messages travel.

When you send a message to a hosted model, that message is forwarded to the upstream company that actually operates the model so that it can generate a reply. Those companies receive the content of your prompt and are able to handle it according to their own privacy policies and retention rules, which we do not control. Depending on which model you pick, the upstream operator may be one of several services we route through. If a conversation is sensitive, the honest advice is to run a local model instead, where nothing leaves your machine.

On our own side, what we record about a request is deliberately limited to operational metadata: which model was asked, whether it succeeded or failed, how long it took, which plan tier made the request, which endpoint was used, and an error message if something broke. This record contains no prompt text, no reply text, no account ID and no IP address. It is held in memory only, capped at the most recent few hundred requests, and is wiped whenever the service restarts or is redeployed. It exists so the status page and the usage charts can work, and it is not a conversation archive.

Eaon Studio stores your chats in your browser

The conversations you have in Eaon Studio, and any API key you paste into it, are saved in your browser's local storage on your own device. They are not uploaded to us. Clearing your browser data for this site erases them, and because they live on one device they will not follow you to another.

Keeping the free tier usable

Because the Instant tier needs no account, it has to be protected from abuse in other ways. Two things follow from that. First, rate limits are counted per client in memory, and those counters are ephemeral and are not written to a database. Second, some sign-up and key-request flows are protected by Cloudflare Turnstile, an anti-bot challenge; verifying a challenge sends the challenge token and your IP address to Cloudflare, which is what allows it to tell a person from a script.

The free week of Plus

If you claim the free trial through the desktop app, we store a SHA-256 hash of the trial key, a hashed identifier for your device, your platform (for example macOS), the app version, a usage count, and the created and expiry dates. Both the key and the device identifier are hashed rather than stored directly, which lets us stop one machine from minting unlimited trials without keeping a readable device ID on file.

4. The desktop app

The Mac and Windows apps run on your computer, and the design intent is that your data stays there.

• Your API keys are kept in the macOS Keychain, the same place the rest of your passwords live, rather than in a plain text file.
• Your chat history is ordinary files on your own disk. You can export it, import it or delete all of it from the app's privacy settings.
• Local models run entirely offline. With a local model loaded, neither your prompt nor the reply leaves the machine, and the app keeps working with the network switched off.
• Hosted models are the exception, and they behave as described in section 3: the message has to reach the model's operator to be answered.
• Update checks fetch a small static file from downloads.eaon.dev to see whether a newer version exists. It is an ordinary file request that sends no information about you or your usage.
• There is no analytics or telemetry SDK in the app. It does not report how you use it back to us.

5. Donations

Donations are handled entirely by Ko-fi, and your payment details never reach us; Ko-fi processes them under its own privacy policy. What we receive and store for the funding total shown on the site is the amount, the currency, the donation type and the display name Ko-fi passes along, which is usually a first name or a nickname.

6. How long things are kept

• Request logs: in memory only, a few hundred entries at most, wiped on restart.
• Rate limit counters: ephemeral, minutes to a day, never written to a database.
• Download events: kept indefinitely as an anonymous asset plus timestamp pair, since there is nothing personal in them to expire.
• Account, profile and API key records: kept while the account exists, and removed when you delete them or ask for the account to be closed.
• Trial records: kept until the trial expires, plus a short period afterwards to stop the same device immediately re-minting.

7. Your choices and your rights

You can delete an API key or a stored conversation yourself at any time, from the dashboard and from the app respectively. Clearing site data in your browser removes everything Eaon Studio has saved locally.

For anything held on our side, email support@eaon.dev and ask. That includes a copy of what is stored about your account, a correction, or full deletion of the account and its records. Depending on where you live you may have a formal right to these things under laws such as the GDPR or the CCPA; either way, the request will be honoured. Because so little is retained, the answer to "what do you have on me" is often shorter than people expect.

The most complete privacy choice available in Eaon is not a setting at all: use a local model, and there is no request for anyone to log.

8. Children

Eaon is not directed at children under 13, and accounts are not knowingly created for them. If you believe a child has created an account, email support@eaon.dev and it will be removed.

9. Security, stated honestly

Sensitive material is handled with the mechanisms described above: keys in the Keychain on macOS, hashing for trial keys and device identifiers, and passwords managed by Appwrite rather than by us. No service can promise perfect security, and this one is maintained by a single developer, so it would be dishonest to claim otherwise. If you find a security problem, please report it to sanscreates@eaon.dev rather than posting it publicly, and it will be taken seriously.

10. Changes to this policy

If this policy changes, the date at the top changes with it. Eaon is open source, so the history of what changed and when is public in the repository. Substantive changes, meaning ones that affect what is collected or where it goes, will be noted in the release notes rather than made quietly.

11. Contact

For privacy questions, data requests or corrections: support@eaon.dev. To reach the person who builds Eaon directly: sanscreates@eaon.dev.