Privacy
Last updated 17 November 2026
This policy covers Clova.Email, the email service at clova.email. Clova.Email is run by Despoina Labs LLC, a California limited liability company; “we” and “us” below mean Despoina Labs.
The short version
- We do not sell your data. Not to anyone, not in aggregate, not ever.
- No human reads your mail unless abuse is reported and confirmed.
- No advertising and no trackers. We count visits to our public pages and how far people get through signing up — anonymously, without cookies, and never inside your mailbox (see Analytics).
- If you sign in with Google, we use your email address to know it is you, and your name and photo only to fill in your profile. Nothing else, and never for advertising (see Google user data).
- If you sign in with Apple, the same: the address Apple gives us — yours, or one it makes to hide yours — to know it is you, and your name only to fill in your profile (see Apple sign-in).
- Mail you forward leaves us for the mailbox you chose. What happens to it there is that mailbox's business, not ours (see Forwarding).
- The pictures beside names in your list come to you through our server, never straight from anywhere else, so nobody outside learns who writes to you or when you read it (see Gravatar and Libravatar).
- Your browser talks to four other companies, each for one thing: Google or Apple while you sign in with them, Backblaze for attachments — which it only ever sees encrypted — and Stripe while you pay.
The rest of this page is the same thing said precisely. It is worth reading — it names some things most policies leave out.
What we hold
Who you are
If you sign in with Google, we never see or store a password. What Google tells us, and exactly what we do with it, is set out under Google user data, below.
Signing in with Apple is the same: no password here, and what Apple tells us is set out under Apple sign-in.
If instead you chose a username and a password, we store the username and a scrambled form of the password — a hash, which cannot be turned back into what you typed.
If you signed in with a passkey instead, there is no password at all. Your device keeps the passkey's private half, unlocked by your face, fingerprint or screen lock; we keep only its public key, which can check a sign-in but cannot make one, with the name of what holds it — iCloud Keychain, say — and when it was added and last used. Your face and fingerprint never leave your device, and we never see them.
A username account can add a recovery email address. That is the one piece of information we hold purely so that there is a way back in; it is optional, and you can remove it.
Whichever way you sign in, we keep the time of your most recent sign-in and the IP address it came from — only the latest one, replacing the one before — to protect your account and to notice abuse. We also know when you sign in or use the app, which is part of authenticating and authorizing you.
Your profile holds what you choose to put in it: a birth year, optionally the day and month to go with it, and optionally a phone number and the country it belongs to. It also keeps the language you choose for the app, if you choose one. The phone number and the picture are genuinely optional and nothing stops working without them.
If you choose to show your picture to the people on Clova.Email you write to — the checkbox under the language in your profile — it appears beside your mail in their lists: only on mail from your permanent addresses, never from a one-sender, prefix or temporary one, and only on mail that proves it came from you. A picture you upload yourself starts out shown; one brought from Google, or one you had before this choice existed, starts out hidden. Untick the box, or remove the picture, and it stops being shown.
Your mail
We store the messages people send to your inboxes — the text, the attachments, and the full headers — because storing them is the service. Attachments are kept encrypted, each under a key of its own (see Backblaze, below).
Kept beside each message is what the delivery itself told us: the IP address the sending server connected from, the name it announced itself as, the envelope sender, and the results of the SPF, DKIM and DMARC checks we ran. That record is what makes it possible to answer "who actually sent this?" later, and it stays with the message for as long as you keep it. We also record when you first opened a message.
Anything you write is stored too: drafts, their attachments, and when they were last saved or scheduled to go out.
When another mail server refuses mail you send or forward, we keep what it answered and the domain the mail was going to, for 90 days — never the address, and nothing of the message. That is how we notice when a provider stops accepting our mail.
Forwarding
If you forward mail, we keep the addresses you forward to: when each was added and confirmed, which one new inboxes forward to, and, for an address that kept refusing what was forwarded to it, what it said. We use an address only to forward mail to it and to confirm it. If whoever reads one refuses forwarding from the confirmation email, we keep that address so it cannot be added again.
We keep a record of who changed forwarding, and when: the latest 200 changes, so that a change nobody here made can be found. Each message to an inbox that forwards notes whether it was forwarded, and if not, why. When forwarding changes, we email every member of the account at their confirmed address to say so.
A message waiting to be forwarded is held on our servers until the other mailbox takes it, and for five days at most: after that it is kept in your inbox instead. Once it has gone, or been kept, the waiting copy is deleted. A note of it stays for six days, without the message, so that the same message is not forwarded twice.
A domain you brought
If you brought a domain of your own, we keep the domain name, the verification token we issued for it, when it was last checked, and how many checks in a row have failed. The domain name is also your account's name, so it appears wherever the account does.
We look up your domain's DNS every week, for as long as the account exists, to confirm the verification record is still published. Those are ordinary public DNS queries about your domain — we ask resolvers what your domain says, which anybody can do, and it tells them nothing about you.
What you pay
No card details, ever. Not the number, not the expiry, not the last four digits. The form you type them into belongs to Stripe and runs on their site inside this page; what comes back to us is an identifier. If a screen ever shows you which card is on file, it is asking Stripe at that moment rather than reading something we kept.
What we do keep is the subscription itself: which plan, monthly or yearly, when the period ends, and whether the last payment went through. A free account has none of this, because there is nothing to record.
A plan bought in the iPhone app is bought from Apple, through the App Store, and Apple takes the payment: we never see how you paid. What Apple tells us, and we keep, is the subscription: which plan, monthly or yearly, when it was bought and when its period ends, whether it renews, and whether Apple has refunded a payment or could not charge a renewal. A random code we make for the account goes with the purchase, to tie it to this account.
A plan bought in the Android app is bought from Google, through Google Play, and Google takes the payment: we never see how you paid either. What Google tells us, and we keep, is the subscription: Google's token for the purchase, which plan, monthly or yearly, when it was bought and when its period ends, whether it renews, whether Google could not charge a renewal, and whether it has ended or been revoked. A change of plan is a new purchase, kept beside the one it replaced. The same random code goes with the purchase, to tie it to this account.
Logs
Our servers keep ordinary operational logs, and those include IP addresses — the machines connecting to deliver mail, and the ones connecting to read it. We use them to keep the service up and to see what is attacking it. Nothing advertising-shaped is built from them. (The one IP address we do keep beside your account is your latest sign-in's, described above.)
They age out on their own as the disk fills, which currently works out at roughly two weeks. We would rather state a firm number here, and intend to.
The phone apps
Each phone you sign in on with the iPhone or the Android app has a session of its own here. With it we keep the phone's model, the versions of its system and of the app, how and when it signed in, and when it was last active: what the Account page lists under Signed-in devices, so that you can tell your phones apart and sign one out. The address its push service has for the phone is kept with its session too, whether or not you let the app send notifications: Apple's push token for an iPhone, Firebase's installation ID for an Android phone. It is how a phone signed out from elsewhere is told to delete its copy of your mail, which needs no notification, and how new mail reaches it once you do allow them.
Signing a phone out deletes its session, and all of that with it, and closing the account does the same. A phone's session left unused for 90 days ends on its own.
Google user data
If you sign in with Google, Google shares three things from your Google Account with Clova.Email, after asking you on its own consent screen:
- your email address, with Google's confirmation that it is verified;
- your name;
- the link to your profile photo, if you have one.
That is all. We ask Google only for the basic sign-in permissions (openid, email and profile). We have no access to your Gmail, your contacts, your calendar, your Drive or anything else in your Google Account, and we never see your Google password.
How we use it
- Your email address is how we know it is you. It is the key your account is filed under: each time you sign in with Google we match the address Google confirms to your account and start a session for it, and we note when you signed in and from which IP address (only the latest, as above).
- Your name fills in the name on your profile so it is not empty on your first day. You can change it whenever you like.
- Your photo, if you have one and your profile has no picture, is downloaded by your browser from Google and saved as your profile picture. It is optional: you can replace it or remove it from your profile at any time, and once you have removed it we do not copy it again.
We use Google user data for nothing else. We do not use it for advertising of any kind, we do not sell it, and we do not use it to develop, improve or train artificial intelligence or machine-learning models.
Who we share it with
Nobody. We do not sell, rent or transfer Google user data, and we do not share it with advertisers, data brokers or information resellers. It is kept on servers we run, and in our nightly backups at Backblaze, which are encrypted before they leave our servers so Backblaze cannot read them. We would disclose it only where the law compels us to (see Law enforcement, below).
How we protect it
Everything between your browser and us travels over encrypted connections. Your email address is held in our own account database and your name and photo in your account's own profile, apart from every other account's, on servers only the people who run Clova.Email can reach. Backups are encrypted with a key that is kept off those servers. No third-party scripts or trackers run on our pages to see any of it, and the counting described under Analytics never includes it.
How long we keep it, and deleting it
- Your email address, name and photo are kept for as long as you have an account. You can change the name or remove the photo from your profile at any time.
- If you sign in with Google but never create an account, we keep the record of that sign-in — your email address, when, and from which IP address — for 30 days after your last one, and then delete it. The deleting is done by a weekly pass, so allow up to a week more.
- When you close your account, all of it is erased once the 30 days in which you can change your mind are up, and it leaves our backups about two weeks after that (see Deleting things).
- If we suspend an account for breaking our Terms, its mail, drafts and attachments are erased at once. We keep its profile, the sign-ins linked to it and its name, so that it stays shut.
- You can stop Google sharing anything more with us at any time by removing Clova.Email's access at myaccount.google.com/permissions. That stops sign-ins with Google; it does not delete what we already hold. To have that deleted, close your account or write to privacy at clova.email.
Clova.Email's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. If we ever change how we use Google user data, we will tell you in the app, and change this page, before the change takes effect.
Apple sign-in
If you sign in with Apple, Apple shares three things with Clova.Email, after asking you on its own sign-in screen:
- an ID Apple makes for you, for Clova.Email alone;
- your email address, which Apple has verified — or, if you choose to hide it, an address at privaterelay.appleid.com that Apple forwards to yours;
- your name, the first time only, if you choose to share it.
The address is how we know it is you, exactly as with Google: your account is filed under it. Apple's ID is kept beside it, so that if the address Apple has for you ever changes, you still reach the same account. Your name fills in your profile on your first day, and you can change it whenever you like. We use none of it for anything else, never for advertising, and we share it with nobody.
Apple's ID and the address are kept for as long as you have an account, and erased with the rest of it when you close it. If you sign in with Apple but never create an account, both go with the rest of that sign-in's record, 30 days after your last one. You can stop using your Apple ID with Clova.Email at any time in your Apple ID settings, under Sign in with Apple. That stops sign-ins with Apple; it does not delete what we already hold. To have that deleted, close your account or write to privacy at clova.email.
Reading your mail: what is automatic and what is not
Mail arriving here is inspected automatically, always. That inspection checks who sent it and looks for spam, abuse, and material that is illegal. It is software, it runs on every message, and no person is involved in it. Mail you send is checked the same way before it goes, for what makes mail look like spam, by software on our own servers.
When we hold an account's sending for spam or phishing, we keep information from the mail it sent, in a scrambled form that no person can read, for forensic analysis. It is deleted after 90 days, or at once if the hold is lifted.
No human at Clova.Email reads the contents of your email or opens your attachments as a matter of course. There is one exception, and it is worth stating exactly: when something has been flagged as abusive, as spam, or as illegal and a complaint is filed about it, a person here may read the message in question in order to decide what to do — which may include closing an account or reporting it to the authorities.
That is the whole of it. We do not read mail to improve a product, to train a model, to build a profile of you, or out of curiosity.
What we never do
We do not sell your personal information, and we do not share it for money or for anything else of value. That includes aggregated and anonymised forms of it, which are the usual way this promise is quietly broken.
We show no advertising. There are no third-party trackers, no pixels and no cookies beyond the one that keeps you signed in. Even the typefaces on this site are served from our own servers rather than from Google's, because loading them from somewhere else would hand that company the address of everybody who reads the page.
Your browser also keeps a few things of its own, in its local storage: your sign-in token, which domain you last signed in under, the language you chose for the app, and which tips you have dismissed. They never leave your browser, and clearing your browser data clears them.
Analytics
We count how many people visit our public pages — the home page, signing up and signing in, contact, this policy and the terms — and how far people get through signing up: which step they reached, and which plan they picked, monthly or yearly. On the help pages, we count the answers to “Did this help?”: which page, in which language, and the answer. That is all we count. Nothing is counted inside your mailbox, ever.
Each count records the page's address without anything after a "?", the site that sent you here as its domain alone, any campaign name in the link, and what your browser says about itself: its type and version, the kind of device, your operating system, your language and your screen size. A visit's counts share a random identifier, made up fresh each time the page loads, so its steps can be followed in order. It never records anything you type, your name, your addresses, your mail, your time zone or where you are.
Nothing is stored on your device to do this — no cookie, nothing in your browser's storage — so we cannot tell a returning visitor from a new one, and we do not try.
The counts are kept by PostHog, in the EU. Your browser never talks to them: it sends the counts to us, and our server passes them on without your IP address or anything else that could identify you.
Who else ever sees anything
Twelve, and no others.
Google, if you sign in with them. They know you have an account here. They do not receive your mail or anything in your mailbox. Sign in with a username and password instead and Google is not involved in signing you in at all.
If you use the Android app with notifications on, Google's push service, Firebase Cloud Messaging, carries each one to your phone, and all it carries is "new mail" and the message's number: the phone itself then asks us who wrote and what about. When you make an account in the app, Google Play Integrity checks that it is our app asking, as Google Play has it, on a genuine Android device: the app asks Google to vouch for a random challenge from us, which says nothing about you, and Google tells us whether the app and the device pass. Nothing of that is kept with your account or your phone; our logs note the app's version and whether Google Play installed it, or why the check failed. And a plan bought in the app is sold by Google Play, which takes the payment (see What you pay).
Apple, if you sign in with them, the same way: they know you have an account here, and never receive your mail or anything in your mailbox. If you use the iPhone app with notifications on, Apple's push service carries each one to your phone, and all it carries is "new mail" and the message's number: the phone itself then asks us who wrote and what about. And a plan bought in the app is sold by Apple, which takes the payment (see What you pay).
Have I Been Pwned, when you choose or change a password. We will not store a password that is known to have leaked, and checking that means asking somebody who keeps the list. What is sent is the first five characters of a hash of the password — never the password, never your address, never anything naming you. They answer with every leaked hash starting with those five characters, and the comparison happens here. It is a well-known design precisely because it lets the question be asked without revealing the answer.
Spamhaus, whose blocklists we check to keep spam and abuse out. For each incoming connection we ask them about the sending server's IP address and the domain it claims — never about your address or anything in the message. When you send a message, we also ask them about the domains its links point to: the domains alone, never the rest of a link or anything else in the message. A message linking to a domain on their list of spam and phishing sites, or to one registered within the last day, isn't sent, and you're told which. When someone signs up, we ask them about the IP address they're signing up from, and also look it up in the Tor Project's public list of Tor exits and in the lists of addresses cloud providers publish, copies of which we keep. We keep only which of those lists it was on, never the address.
Gravatar, run by Automattic, for the pictures beside names in your list. When your list shows somebody who is not on Clova.Email, and whose mail proved it came from them, our server may ask Gravatar for the picture they keep there. What is sent is a hash of the sender's address — the form Gravatar files pictures under — never the address itself, never yours, and nothing from the message. Gravatar can tell which of its own users' pictures it was asked for, since that is how it finds them; it cannot tell who received their mail. The asking is done by our server, and the picture is kept there, which is where your browser gets it: so Gravatar never sees your IP address, and never learns who reads mail from whom, or when. We ask again only now and then — a month later for a picture, a week later when there is none — to keep up with changes.
Libravatar, a free and open-source service like Gravatar, for the same pictures, and asked only about a sender Gravatar has none for. It is sent the same hash of the sender's address, and nothing else: never the address itself, never yours, and nothing from the message. It is asked to answer for itself rather than pass the question on to Gravatar. As with Gravatar, our server does the asking and keeps the picture, so Libravatar never sees your IP address and never learns who reads mail from whom, or when; and it is asked again on the same schedule.
The networking infrastructure of companies that write to you, for their logos. When your list shows mail from a company that publishes a logo with BIMI, and whose mail proved it came from them, our server looks up the company's DNS records, fetches the certificate that vouches for its logo from wherever the company says it is, and fetches the list of revoked certificates from the authority that issued it. A logo is shown only when that certificate checks out. Those servers see this activity coming from our server's IP address, but cannot tie it back to any single user: not who received the mail, not your IP address, and nothing from the message.
Stripe, if you pay for a plan. Card details are entered into their own form and go straight to them — the card number never reaches our servers, and we could not store it if we wanted to. They are told your account name, so a payment can be traced to the mailbox it is for. They are not given your mail, your addresses, or anything in your mailbox. Stay on the free plan and Stripe is not involved at all.
The people you write to. Sending an email means handing it to whoever's server receives it, and what they do with it is governed by their rules, not ours.
The mailbox you forward to, if you forward mail. Each message forwarded is handed to the server of the address you chose, as it arrived here, with a few lines saying it came through us. From then on it is governed by that mailbox's rules, not ours. It does not work for us, and it is given nothing else.
PostHog, in the EU, keeps the anonymous counts described under Analytics. They come from our server rather than your browser, so PostHog never learns your IP address, and nothing it is sent names you or touches your mailbox.
We also use ordinary infrastructure to run the service — a hosting provider whose machines the data sits on, and a certificate authority that issues our TLS certificates. Neither is given access to mailboxes.
Backblaze stores our nightly backups, and every attachment — the files on mail you receive and the ones you attach yourself. All of it is encrypted before Backblaze gets it: backups on our own server, with a key that never leaves our hands, and each attachment under a key of its own that is kept with your mail, on our servers, and never given to them. What Backblaze holds it cannot read, and it is never told whose it is.
Attachments travel between your browser and Backblaze directly rather than through us, which is what keeps a large file quick. Your browser encrypts a file before it sends it there and decrypts one after fetching it, so Backblaze only ever sees the encrypted form. It does see your browser's IP address when you upload or download one, as any server your browser talks to does.
The same goes for an export of your account, when you ask for one: it is encrypted on our servers under a key of its own before Backblaze stores it, and your browser downloads it from Backblaze and decrypts it as it saves it.
Deleting things
You can delete a message, a whole conversation, a draft, or an entire inbox at any time, and deleting an inbox takes the mail in it with it. A temporary inbox can be set to wipe what it holds when its time is up. You can remove your profile picture whenever you like. Deleted mail is cleared from our storage by a background pass rather than instantly, so allow a little time for the space to actually come back. An attachment you delete is erased from Backblaze a week later, and stays encrypted until it is.
What you forward is out of our hands. Deleting a message here, an inbox expiring and closing your account all remove our copy, not the one forwarded to another mailbox. Nothing is forwarded from a closed account.
You can take a copy of everything with you. From Settings, under Account, you can ask for an export: the mail of every address, with its attachments, your drafts, your spam folder, your contacts and your addresses, in one file. We keep it, encrypted, for 7 days for you to download, and then delete it. You can ask for one a day, and asking for a new one deletes the last.
You can close the account yourself, from the Danger Zone in Settings, under Account. Nothing is erased for 30 days: you are signed out immediately but can sign back in, and the Recovery Zone on that same page undoes it completely. Mail carries on arriving during that month, so that people writing to you are not bounced while you are still deciding.
Once the 30 days are up, a weekly pass erases the mail and its attachments, your profile — name, birthday, phone number, photograph — and whatever links you to the account: the entry naming your Google or Apple sign-in, or your username, the hashed password or the passkeys' public keys, the hashed recovery code and any recovery address, and the record of your latest sign-in. Your forwarding addresses, and the record of who changed them, go with them. Because that pass runs weekly rather than continuously, allow up to a week beyond the 30 days for the data itself to go; the account is shut and unreachable that whole time.
What is left afterwards is a small record that the account was closed — enough to keep it closed, and not enough to say who you were.
Backups outlast deletion, but not by long. Every night we make an encrypted copy of each account and keep one for each of the last seven days, and a copy that has been replaced is kept for one more week. So anything deleted — a message, or a closed account's mail when it is erased — is gone from our backups as well within about two weeks. Ordinary logs may hold traces of deleted material for a short while too.
Law enforcement and legal process
We comply with the laws that apply to us, in the United States and elsewhere where they apply.
We give user data to federal or local authorities when they ask for it properly: with documentation, and with the authorisation of a judge where the law requires one. We do not hand over mailboxes on an informal request, and we push back on demands that are overbroad or improperly served.
Keeping it safe
Mail arrives over an encrypted connection wherever the sending server supports it, and everything between your browser and us is encrypted. Mailboxes are stored separately from one another, and the parts of the service that touch the internet run with as few privileges as they can. Attachments and backups are encrypted before they leave our servers. No system is perfect and anyone who tells you otherwise is selling something.
Changes
If this policy changes in a way that matters, we will say so here and move the date at the top. Continuing to use the service after that means the new version applies.
Getting in touch
Questions about any of this, or about what we hold on you, and requests to see or delete it, go to privacy at clova.email. Clova.Email is run by Despoina Labs LLC, a California limited liability company.