Privacy policy

We're asking to read your household's mail. This page says exactly what happens to it, in plain English and without the lawyer voice.

Last updated: 25 October 2026

The short version

  • We store the email you forward or connect to us, and the calendar events, todos, chores and lists you build from it.
  • We use it to run household.email for you. That's the whole purpose.
  • There are no ads. We don't sell your data or share it with data brokers.
  • We pull dates and tasks out of your email with an AI model we run ourselves, on rented servers. No AI company reads your email, and nobody trains a model on it, us included.
  • You can disconnect a mailbox at any time, and you can delete your account yourself, from your account page. The last account to leave takes the household and everything in it with it.

Who we are

household.email is the service at household.email. If you want to talk to a person about anything on this page, email hello@household.email. We're small, so that address reaches us directly.

What we collect

Account details

Your email address, your name, your timezone, and optionally a date of birth. We sign you in with emailed codes and magic links rather than passwords.

Household members

The names and, if you enter them, dates of birth of the adults and children in your household. Dates of birth are used for birthdays and for showing age-appropriate task views. Only adults in your household can see or change this.

Email

Your household gets its own email address. Anything sent or forwarded to it is stored: the subject, the sender and recipients, the message body in full, and any attachments. If you connect Gmail, iCloud or another IMAP mailbox, we fetch and store the messages that match what you've asked us to watch, on the same terms. We also store replies and forwards you send from household.email, and a short AI-generated summary of each message.

Household content

Calendar events, todos, chores and who completed them, shopping lists, tags and labels — both what you type in yourself and what we suggest from your email.

Connected accounts

If you connect Google (Gmail, Calendar or Tasks), Apple iCloud, or a plain IMAP mailbox, we store the access credentials needed to keep syncing — OAuth tokens for Google, and the username and app-specific password you give us for IMAP accounts. We use them only to sync the mail and calendars you've connected.

Payments

When paid plans are switched on, payments are handled by Stripe. Card details go to Stripe and never touch our servers — we keep only the Stripe customer and subscription identifiers, your plan, and its status and renewal date.

Technical data

Ordinary server logs, and error reports when something breaks. Error reports go to monitoring software we run on our own infrastructure, configured not to include personal data.

Waitlist

If you join the waitlist we store your email address so we can tell you when your invite is ready. We also note which of our pages you signed up on and, if another site sent you to us, that site's address (never its search terms or anything after a "?"), so we know which pages are worth writing more of. Nothing else. Ask us and we'll take it off the list.

How AI is used on your email

Reading a school newsletter and spotting the one date that matters is the job household.email does for you, and it uses a large language model to do it. When an email arrives, we send its subject and the beginning of its body to that model and ask for the events, deadlines and tasks hiding in it. The suggestions come back to you to accept or reject — nothing is added to your calendar without you seeing it. Our AI assistant, when you use it, sends short extracts of your household's email, calendar, todos and lists so it can answer your question.

The model is an open-weights one, Qwen, and we run our own copy of it. It runs on graphics cards we rent from Modal, in a container we built and control. No AI company sees your email: the model only answers our requests and keeps nothing once it has replied. Modal provides the hardware, the same way a hosting company provides a server, and does not use what passes through it. If we ever send your data to an outside AI provider, we'll update this page first, and it will be one whose terms forbid training on it. We do not train any model on your data.

Google user data

If you connect a Google account, household.email's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

In plain English: your Google mail, calendar and tasks are used only to run the features you connected them for. We never use them for advertising, and we never sell them or hand them to anyone else except where it is needed to run those features for you, where the law requires it, or where you have asked us to. Nobody here reads them by hand, apart from the rare case where you ask us to look at something to fix a problem. Nothing from a connected Google account is used to develop, improve or train a general AI model, ours or a provider's.

Who else your data reaches

These are the companies involved in running the service, and why:

  • Modal — rents us the graphics cards our own AI model runs on. Email content passes through them while it extracts events and tasks and answers the household assistant's questions. They don't keep it or use it.
  • Migadu — hosts the mailbox behind your household's email address.
  • Mailgun — delivers the email we send you, such as sign-in codes and reminders.
  • Komoot — suggests addresses as you type an event's location. It sees only what you type in that field, not who you are.
  • Stripe — processes payments, once paid plans are switched on.
  • Meta — measures which of our Facebook and Instagram ads bring people to these marketing pages. It is told that a browser opened a public page, and nothing about your household.
  • Google and Apple — only if you connect their accounts, and only to sync what you've connected.

Everything else — the database, your attachments, error monitoring — runs on infrastructure we operate ourselves. We will also hand over data if the law genuinely requires it, and we'll tell you unless we're forbidden from doing so.

Our pages load a webfont from Google Fonts, so Google sees your IP address when a page loads. It sets no cookies and gets nothing else. The public marketing pages, this one among them, also load Meta's advertising pixel, which tells Meta that a browser opened the page. It is the only way we can see which of our ads work. It is not loaded on any signed-in screen, so it never sees anything about your household, and it is not loaded in the iOS or Android apps at all.

What we never do

  • No advertising, anywhere in the product, on any plan.
  • No selling your data, and no sharing anything about your household with data brokers or ad networks.
  • No profiling you for anyone else's benefit.
  • No AI model trained on your household's data, ours or anyone else's.
  • No reading your household's email by hand, except in the rare case where you ask us to look at something to help fix a problem.

Cookies

We set a cookie to keep you signed in. Before you sign in, it also remembers which site sent you to us, for the waitlist note above, and your invite code if you arrived on one. Signing in sets one more, in a browser as much as in the iOS and Android apps, which the apps read to tell a live session from a stale one; an admin gets a second cookie saying so. Those are all ours, and they are the only cookies anywhere you are signed in. On the public marketing pages, Meta's advertising pixel described above sets its own.

To see how the service is used, the app itself records in our own database which days you use it and through which app (web, iOS, Android or the API), which screens you open, how far you got through setup, and counts of actions such as todos added or emails handled, with no email content and nothing you type; the screen-by-screen record is deleted after 13 months.

Before you sign in, our public pages are counted by Plausible, an open-source analytics tool we run on our own server at analytics.household.email. It sets no cookies and keeps no identifier that follows you from one day to the next: it counts which page was opened, which site linked to it, and the country, browser and device type. Once you sign in, it stops.

Security

Traffic to household.email is encrypted over HTTPS. Your household's data is walled off from every other household, and access to the servers is limited to the people who run the service. Passwords and tokens are kept out of our logs.

Being straight with you: the credentials for mailboxes you connect are held in our database so that syncing can continue, protected by the access controls around that database rather than by per-field encryption. Encrypting them at rest is on our list. Your calendar feed URL contains a long random token and anyone who has the URL can read that calendar, so treat it like a password — you can regenerate it from your integrations page at any time.

Keeping and deleting your data

We keep your household's data for as long as the household is using household.email. You can disconnect Gmail, iCloud or an IMAP mailbox yourself at any time, from the integrations page, and we immediately stop fetching from it.

To delete your data, use the delete button on your account page. If yours is the only sign-in account in the household, it deletes the household and everything in it: email, attachments, calendar, todos, chores, lists and the household's mailbox, and cancels any subscription. If other people in your household have their own accounts, it deletes your account and leaves the household's shared data with them — the last account to leave takes the household with it. Deletion is immediate and permanent.

Prefer to ask a person, or want something more specific deleted? Email hello@household.email and we'll do it within 30 days and confirm when it's done.

If you want a copy of your data before you go, ask in the same email and we'll get it to you.

The step-by-step version, including what happens to a household someone else is still in, is on the deleting your account page.

Your rights

You can ask us what we hold about you, ask us to correct it, ask for a copy, or ask us to delete it. Depending on where you live you may have these rights by law; we'll honour the requests either way. One email is enough — we won't make you fill in a form.

Children

household.email is set up by adults. An adult in the household can add a child's name and date of birth so chores and birthdays work, and a child may use the household's account to see their own tasks. We don't advertise to anyone, and children's information is used only inside the household that entered it.

Changes to this policy

If we change something that matters, we'll update the date at the top of this page and tell household admins by email. We won't quietly start doing something this page says we don't do.