Privacy

The short version

Magpie learns private things about your household so that it can be useful. What it knows comes from one calendar you connect and from the rhythm and messages you write yourself. We do not sell your information, we do not show advertising, and we do not train models on your household content.

The rest of this page says exactly what is collected, where it is kept, who else sees it, and how to get a copy of it or have it deleted. Where a control does not exist yet, we say so rather than leaving you to guess.

What Magpie reads

The calendar you connect, and nothing else on that account. The connection is read only: Magpie cannot create, change or delete an event. It asks for one permission, calendar reading, and no profile or identity permission at all.

One identifying detail does come with that connection. To show you which account you connected, Magpie stores the address of the connected calendar, which for a personal account is usually an email address. We use it as a label on the connection screen and for nothing else.

Everything else Magpie holds is something you gave it directly: the household rhythm you write, the messages you send it in the app, the display name on your account, the passkey your device registers so that you can sign in, and a delivery token from your phone so that we can send you a notification.

Magpie is not connected to your email, your files, your photos, your location or your contacts, and it has no access to your camera or microphone. Those absences are the product rather than an oversight.

If you write to us to ask for early access, we hold that message and whatever you chose to put in it.

What Magpie remembers

There are two kinds of thing, and the difference matters. The household rhythm is yours: you can open it in the app, read all of it, and change it. Nothing is written there that you cannot see.

The rest is what Magpie produces for you and keeps so that the app can show it to you again: the reports it writes about your week, and your conversation with it.

We do not delete this on a timer, and we would rather say so than invent a retention schedule we do not run. Your household content is kept for as long as your household is active, and we delete it when you ask.

Where it is stored

On servers in the United States. Everything is encrypted in transit, and the fields holding household content are encrypted at rest: your rhythm, your reports, your messages, and the credentials for the accounts you have connected.

We keep routine backups so that your data survives a hardware failure, and we test that those backups can actually be restored. Superseded backup copies age out on their own schedule.

People at MagpieAI can reach household data, and we would rather be plain about that than imply otherwise. What limits it is the rule in What we never do below, not a technical impossibility: an operator-run service has to be able to read your content in order to answer your questions at all.

Children

A Magpie account belongs to an adult. Children do not have accounts, do not sign in, and are not users of the service.

Magpie does hold information about the children in a household, because a family calendar and a household rhythm are largely about them. That information reaches Magpie only through the adults: the calendar they connect, and the rhythm and messages they write. Magpie collects nothing from a child directly, and it offers a child no way to send it anything.

Magpie is not directed to children and is not offered to them, so it is not a child directed service under the Children's Online Privacy Protection Act. The adult who sets up the household is the person consenting, and that adult can ask us to delete everything at any time.

Who else sees it

Running Magpie means relying on a small number of service providers. The list is short deliberately, and it is the whole list.

• A cloud hosting and storage provider runs the servers and holds the backups.
• An AI model provider answers what you ask. Your question, and the household context needed to answer it, go to whichever provider account your household runs on.
• A content delivery network sits in front of both the app's connection and this website, and can see that traffic as it passes.
• Web search services (Exa, Parallel, Firecrawl and Keenable) answer when you ask Magpie something only a public web page can, like opening hours. They receive only the search words, made from what you asked, the names of your places and titles on your calendar, plus your home town, never your street. The answer shows you exactly what was searched for.
• A cookieless analytics service counts visits to this website. It sets no cookies and does not follow you to other sites.
• Apple delivers push notifications. Notifications carry no household content: they say that something is ready, and the app fetches the content itself once you are signed in.
• A hosted continuous integration service builds and tests our code, and is where we verify that a backup can be restored.

On training, because this is the question people come to this section for. MagpieAI does not train models on your household content. If you connect your own AI provider account, that provider's terms decide what it keeps and whether it may use what it receives to improve its own models. Some consumer plans permit that by default, and the setting that controls it lives inside your provider account, where we can neither read it nor change it. The app tells you this on the screen where you connect the account, and for as long as the account stays connected.

What we never do

• We do not sell your personal information, and we do not share it for cross-context behavioural advertising.
• We do not show advertising in Magpie, and we do not use your household content to target any.
• We do not train models on your household content.
• No person at MagpieAI reads your household content except to diagnose a fault you have reported to us, or where the law requires it.

Your controls

Write to privacy@withmagpie.ai and we will answer within 30 days. You can ask for a copy of everything we hold about your household, ask us to correct it, or ask us to delete it.

Deleting removes your household and everything under it: the rhythm, the reports, the conversation, and the connection to your calendar. Backups already taken are not edited. Superseded copies age out on their own schedule, and we do not use a backup to bring a deleted household back.

Being straight about how this works today: these requests are handled by a person, not by a button in the app. There is no account deletion control in Magpie yet, and no way to disconnect a calendar from inside the app. Disconnecting the AI provider account is something you can do yourself, in Settings. If a control is not described here, assume it does not exist yet rather than that we left it out.

Independently of us, you can revoke Magpie's access to your calendar from your calendar account's own permissions settings. That stops any further reading immediately.

Your rights

Magpie is offered in the United States.

If you live in California, the California Consumer Privacy Act gives you the right to know what personal information we collect and how we use it, the right to a copy of it, the right to correct it, the right to have it deleted, and the right not to be treated differently for exercising any of those rights. We neither sell nor share personal information, so there is nothing there to opt out of.

Exercise any of these by writing to privacy@withmagpie.ai. We will need to confirm that you are a member of the household before we act, so that we do not hand your household's information to somebody else.

Changes to this policy

When this policy changes, the date at the top of the page changes with it. If a change materially affects what we collect, what we do with it, or who else sees it, we will tell you in the app before it takes effect.

Contact

Magpie is made by MagpieAI. Questions about any of this: privacy@withmagpie.ai