Privacy
What we store, and who can read it
Storing your email is the entire product, so a privacy policy that talks around that would be useless. This one says what is kept, where it sits, who can reach it, and how to make it go away.
Last updated 11 September 2026
Who this is about
imado is operated by Zivaro Software Inc., a Delaware C corporation. When this page says “we”, it means that company. Questions go to ashish.so@zivaro.ai.
What we hold
- Your account. Name, email address, and a hashed password. We never store the password itself.
- Your domains. The domain names you connect, the DNS records we ask you to publish, and the identifiers our mail provider issues for them.
- Your mail. The messages you send and receive, their attachments, and the original raw message exactly as it arrived. The raw copy is kept so a message can be processed again if we improve how mail is parsed, so a parsing bug can be fixed without losing what it damaged.
- Operational records. Sign-in times, the IP address a request came from, and delivery outcomes such as bounces. The IP address is used for rate limiting and abuse investigation, and nothing else.
- Site analytics. Vercel Analytics on our public pages and on sign-in, never inside your mailbox. It counts visits without cookies and without building a profile of you.
Who can read your mail
Nobody at Zivaro Software Inc. can sign into your account and read your inbox.
Our staff tooling has no way to sign in as someone else, so there is no support button that opens somebody's mailbox. The operator's view of the product (how many accounts and domains there are, what is in flight, how mail is landing) shows counts and domain names, never a message and never an address.
A small number of people can reach the underlying storage, because somebody has to be able to operate and repair the system. They do so to fix a fault, to answer a request you made, or to investigate an abuse report, and not otherwise.
We do not read your mail to target advertising, we do not sell it or share it with data brokers, and we do not use it to train machine learning models.
Why we hold it
- To run the product: deliver your mail, show it to you, and keep your account working.
- To protect it: rate limiting, abuse investigation, and keeping the service delivering for everyone on it.
- To talk to you: service notices, and replies when you write to us.
- To meet a legal obligation, where one genuinely applies.
Where it lives, and who else touches it
Everything is hosted in the United States. If you are writing from elsewhere, your mail is being stored there.
- Amazon Web Services — sending and receiving mail, and storing the raw messages.
- PlanetScale — the database holding accounts, domains, and parsed messages.
- Vercel — hosting for the application and the marketing site, and the site analytics above.
These are the only third parties that hold your data. If that list changes, this page changes with it.
How long we keep it
Your mail stays for as long as you want it. Deleting a mailbox in the product stops it receiving and frees its addresses while keeping what it holds; a click never destroys mail. When you want a mailbox's mail, a domain's, or your whole account removed, write to us and it is done within 30 days: the parsed messages, the attachments and the raw copies together. Backups roll off a little later, and nobody can search them in the meantime.
Operational records (sign-in times, the address a request came from, delivery outcomes) are kept for the life of your account and removed with it. A shorter window is planned, and this page will carry the number when it applies.
Getting your data, or getting rid of it
You can ask us for a copy of everything we hold about you, ask us to correct it, or ask us to delete your account entirely. Write to ashish.so@zivaro.ai and we will do it within 30 days.
During the alpha this is handled by a person rather than a button in the settings. That is a gap we intend to close, and saying so is more useful than describing a screen that does not exist yet.
How it is protected
- Everything travels over TLS, and our storage providers encrypt it at rest.
- Passwords are stored hashed, never in a form anyone can read.
- Sign-in and mail-sending endpoints are rate limited, in shared storage so the limit holds across every server.
- Access to production storage is limited to the people who operate the service.
The security page lists what is in place and what is not yet; what alpha means says what that implies for your mail.
Images in the mail you read
When you open a message, the images its sender included load from the sender's servers, as they do in most mail apps. That can tell the sender that the message was opened, when, and from which network. We intend to load images through our own servers instead, so that a sender sees us rather than you, and this page will say so when that is live.
Cookies
One cookie, and it is the one that keeps you signed in. Your light or dark theme preference is stored in your browser and never sent to us. There are no advertising or tracking cookies.
Children
imado is not intended for anyone under 16, and we do not knowingly create accounts for them.
Changes to this page
When this policy changes in a way that matters, we will email account holders before it takes effect rather than quietly editing the date at the top.