Privacy

Last updated 23 September 2026.

This page says what Hemmingway keeps when you use it, on your computer and on our server, in plain terms.

Who we are

Hemmingway is made and run by the Commons Lab, in Switzerland. We are responsible for the data described here, and we follow the Swiss Federal Act on Data Protection (FADP). You reach us at support@hemmingway.io.

The desktop app

The desktop app keeps your chats, people and memory in files on your own computer. Your sign-in token is kept separately, in your operating system's secure keychain.

The Chrome extension

The Hemmingway extension for Chrome can see the pages you open, because it puts its H button in text boxes and offers to fill in forms. It reads a page only on your computer, to know where those buttons go. A page's content leaves your computer only when you ask Hemmingway to do something there: then the page's text, the list of what can be clicked or typed in on it, and a picture of the screen if it needs one, go to the model with your request, as described under Requests to the model, and aren't kept.

Your sign-in token, the chat you have open, your settings, and any files you attach with the + button (such as a CV to put into upload fields) are kept in the extension's storage on your computer. Files you attach are sent only to the web page you ask it to upload them to, never to our server. The chats you have in the extension are saved to your account like any other chat, and never used for training.

It never fills in passwords or card numbers, and it doesn't read pages in the background, keep a history of the pages you visit, or sell or share what it sees.

Your account

When you make an Hemmingway account, our server keeps:

• Your email address and name.
• Your picture from Google, if you sign in with Google.
• If you sign in with Google, the sign-in token Google gives us, which only reaches your name, email address and picture.
• Your password, if you set one. We keep only a hash of it, never the password itself.
• A record of each sign-in, with the device's IP address and the name of the app or browser you used.
• How much you have used Hemmingway in each 5-hour period.

We keep your email, name, picture and password hash for as long as your account exists. We keep a sign-in record for up to 90 days after you last used it, then remove it. We keep usage counts for 90 days.

Your chats, memory and People

When you are signed in, our server keeps your chats, memory and People, and your name and appearance settings, so they are the same in the desktop app and on the web. They stay until you delete them.

Chats only on this device

On the web and in the Android app you can keep chats on your device instead, when you start or later in Settings, under Account. Chats you start while that is on, and anything Hemmingway is asked to remember while it is on, stay in that browser or app on that device. Our server never stores them, so we can't read them, and they aren't on your other devices. Each message still goes to the model to be answered, as described below, and isn't kept. Clearing that browser's or app's data deletes them.

How we use your chats

We don't train our models on your chats, memory or People. That holds whether they are saved to your account or kept only on your device. We never sell them. What is saved to your account is kept so it is there for you on every device you sign in on.

Requests to the model

When Hemmingway asks the model a question, from the desktop app or the web, the request passes through our server and on to the machine that runs the model. Our server doesn't keep the request itself. It logs the request's token counts, how long it took and whether it worked, never its content.

The API

Requests made with an API key, directly or through a partner that offers our API, are handled like this:

• We don't train our models on them.
• We don't keep their content. Prompts and replies are not stored or logged, anywhere. Every API request is zero data retention.
• Our server logs only each request's key, token counts, cost, time, and whether it worked. This is the account's billing record and stays while the account exists.
• No one else handles them. A request goes from our server to the machine that runs the model, and the answer comes straight back. It is never sent to another company's AI model.

Visits to this website

We count visits to hemmingway.io ourselves, with no cookies and no outside analytics service. For each page opened, and a few actions such as a download or a click into the app, our server keeps the page, the site or link you came from, your country as guessed from your IP address, and the kind of device, system and browser. It doesn't keep your IP address.

Your browser can keep one random number for this site, in the site's storage rather than a cookie, so we can tell when someone comes back another day and what first brought them. The number doesn't say who you are. In Europe we ask first, with a small card at the bottom of the page: until you say yes, or if you say no, your browser keeps no number. A browser that asks not to be tracked (Global Privacy Control or Do Not Track) keeps no number and isn't asked. Without the number, a visit is counted with a code made from the IP address that changes every day. If you sign in, the visits from that browser count with your account, earlier ones included. Clearing this site's data in your browser removes the number. We keep these records for about 13 months. Ask me again

In Hemmingway on the web and in the Android app, when you are signed in, the same records are kept with your account, so we can see where people get stuck and what goes wrong: which of the first steps you finished, when you send a message and at which thinking level, which features you use (such as Try again, Copy, Save or a voice note), whether a reply failed and why, whether you opened the plans or a checkout, and errors the page ran into. They never include what you wrote or what Hemmingway wrote. If you delete your account, these records stay without it.

Payments

Stripe handles payments and sees your card. Our server never does. It keeps your plan, your Stripe customer id, and the amounts of API credit you buy and use.

Crash reports

If you turn on crash reports, a report can hold the app's version, your operating system, where the crash happened, the error message and the names of the functions involved. We remove anything that looks like a folder path or an email address before we keep it. A crash report never includes your messages, prompts or name, and is not tied to your account. We keep crash reports for 90 days.

Services we use

Hemmingway runs on a few outside services. None of them is another AI company, and none gets your chats to train on.

• Vercel hosts our server and this website.
• Neon holds our database.
• Resend sends the sign-in code emails.
• Stripe handles payments.
• Google, if you choose to sign in with Google.
• A rented machine that runs the model. It answers requests and keeps nothing.

Your data, and deleting it

From Hemmingway's settings you can download everything our server keeps for you as one file, or delete all your chats, memory and People and keep your account. You can also delete your account at any time. This removes everything listed above that our server keeps for you.

Contact

Questions about this page go to support@hemmingway.io.