Skip to content
ProductsAboutContactSign in
ProductsAboutContactSign in
← Back to home

Privacy Policy

Last updated: 6 November 2026

Who we are

The Happie Co OÜ (“The Happie Co”, “we”, “us”) is a private limited company registered in Estonia under registry code 17226889, with its registered office at Ahtri tn 12, 15551 Tallinn, Estonia. You can reach us at hello@thehappie.co.

What this policy covers

This policy explains how we handle personal data in connection with our websites — thehappie.co, wappie.thehappie.co and mailie.thehappie.co — with your account at the happie co. (sign-in at id.thehappie.co, and your settings, your personal workspace and your team workspaces at console.thehappie.co), and with Mailie, our email service (the app at app.mailie.thehappie.co and the API at api.mailie.thehappie.co). Most of our products are not yet available, and our websites are informational. Wappie is available as an invitation-only pilot, which you use with your account at the happie co.; this policy describes what Wappie and we exchange (under “The apps and the workspaces”, “API keys” and “The apps’ settings in the console”) and what happens when a number is deleted (under “Deleted numbers and email accounts”), but not yet the rest of what the Wappie console and messaging client process; until it does, participants in the pilot can ask us about it at hello@thehappie.co. Mailie is available as a private beta, which you use with your account at the happie co.; the sections whose titles start with “Mailie” describe the personal data it processes. For now, an account at the happie co. can be created only with an address we have added to a list.

What we collect on our websites

Our websites do not use advertising or analytics, and they do not ask you to fill in any forms; your account at the happie co. is created and managed at id.thehappie.co and console.thehappie.co, as described below. We do not track your activity. Your language and your theme are kept in two cookies that every site and app of the happie co. sets on the whole thehappie.co domain (thehappie.co, id.thehappie.co, console.thehappie.co, our apps and our product sites), so that one choice is the same everywhere: thehappie_locale holds the language (pt-BR, en or es), and thehappie_theme the theme (system, light or dark). They are kept for one year, hold no identifier and are not used to recognise you. Because they belong to the whole domain, your browser also sends them to other sites hosted under thehappie.co, which learn only your language and theme. While you are signed in to the console, a change of language or theme made on any of our sites or apps changes your account’s too, and every page shows your account’s (see “Your account at the happie co.”). Our server keeps standard technical logs (such as IP address, requested page and time) for security and troubleshooting, and keeps them only for a short time. Beyond that, the only personal data we receive is what you choose to send us — for example, if you email us, we receive your email address and the contents of your message.

Why we use it and our legal basis

We use the information you send us solely to read and reply to you. Under the EU General Data Protection Regulation (GDPR), our legal basis is our legitimate interest in responding to your enquiry (Art. 6(1)(f)).

Sharing

We do not sell your personal data. We may rely on service providers (such as our email, hosting or payment provider) who process data on our behalf and only on our instructions, apart from what our payment provider does as a controller in its own right, described under “Billing”. Some of your data is also shown to other people, in the cases this policy describes: for example, the other members of a team workspace you belong to see your name, email address and role there; once one of our apps has reported on a workspace, its owners and admins also see what you can do with each of its WhatsApp numbers and email accounts in that app and whether you have opened that app; once an app also sends us its settings, they also see some of what you did in that app, such as pausing a number’s sync or connecting an assistant, and, in Mailie, your status there, and the people who can read one of the workspace’s numbers or email accounts may see that you, as one of the workspace’s owners or admins, paused or turned off the sync of that number or email account, or, for a number, that an API key you created paused its sync; the other owners and admins of a workspace see the API keys you created in it, with your name or, if you have none, your email address, while you are in it; whoever opens the link of a workspace invitation sees the invited address; and, if you buy a workspace’s plan or pay for it, its owners and admins see your name and, if you pay for it, its other owners also see your billing details at Stripe; and, in Mailie, the people who read a team mailbox see what you send from it, with your name, and your name and email address while you wait for its key (see “Your account at the happie co.”, “Workspace invitations”, “The apps and the workspaces”, “API keys”, “The apps’ settings in the console”, “Billing” and “Mailie — what we process”).

Keeping your data

We keep correspondence for as long as needed to handle your request and to keep a reasonable record, but no longer than 3 years after our last exchange, and then delete it.

Your rights

Under the GDPR you may request access to your data, correction, erasure, restriction, or portability. You may also object at any time, on grounds relating to your particular situation, to processing based on legitimate interests (Art. 21). To exercise any of these, email hello@thehappie.co. You also have the right to lodge a complaint with the Estonian Data Protection Inspectorate (Andmekaitse Inspektsioon, aki.ee).

Your account at the happie co.

When you create an account, we keep your email address; your name, if you give one; and your language, one for the whole account, which id.thehappie.co, console.thehappie.co and the emails about your account use; a sign-up or recovery code, though, is written in the language shown on the page where you asked for it. We also keep, on our server, your theme (system, light or dark): one per account, which id.thehappie.co and console.thehappie.co share, and which either can change; and your personal workspace at console.thehappie.co, with when it was created, which is when you signed up, and your role in it, which is owner. If you create or join team workspaces there, we also keep each team workspace you belong to, with its name, your role in it (owner, admin or member) and when you joined it. The other members of a team workspace see your account’s identifier, name, email address and role, and when you joined it; its owners and admins also see you in its pending invitations, when you invite someone, and in its activity log, with your account’s current name and email address, for as long as its entries about you are kept, even after you leave the workspace or if you decline an invitation to it, as described under “Workspace invitations”. Once one of our apps has reported on a team workspace, as described under “The apps and the workspaces”, its owners and admins also see there what you can do with each of its WhatsApp numbers or email accounts in that app, and whether you have opened that app; in a team workspace, its other owners and admins also see the API keys you created there, with your name or, if you have none, your email address, while you are in it (see “API keys”). Once that app also sends us its settings, the workspace’s owners and admins also see there some of what you did in it and, in Mailie, your status there, as described under “The apps’ settings in the console”. You stay in a team workspace until you leave it, an owner or admin removes you or your account closes; a team workspace that an owner closes disappears for its members but is kept, with its members and their roles, so that we can reopen it for one of its owners. For the account itself, we keep, while it exists, whether it is active or disabled by us, when it was created and last changed, and when your password and recovery code last changed. We also keep a dated record, without an IP address or browser label, of the account’s creation, of each change to its name, language or theme, of each time all its sessions were ended (and whether a recovery ended them) and of each time we disabled or enabled it; the console uses this record to set up your personal workspace, to end its own sessions, to revoke the API keys you created before a recovery of your account or before we disabled it (see “API keys”) and to tell our apps when your sessions were last ended, when your account was last recovered and when we last disabled it, as described under “The apps and the workspaces”. Your password stays in your browser: the page at id.thehappie.co derives keys from it there with Argon2id, a deliberately slow calculation that makes guessing passwords costly, and sends us only a sign-in key that proves it is you and, when you set a password, your main key, described below, encrypted under another of those keys. We store a hash — a one-way fingerprint — of that sign-in key, with the salt, a value we derive from your email address with a secret key of ours and that your browser mixes into the calculation, and the settings your browser needs to repeat it, but never your password itself. Your account also has a main key, which your browser makes when you sign up and which we never see: we store it only encrypted, in separate copies, one that only your password opens, one that only your recovery code opens and one for each passkey (a way to sign in with your device’s fingerprint, face or screen lock instead of your password) that can unlock your account. The page at id.thehappie.co is, however, loaded from our servers, and a modified version of it could read your password as you type it, or your main key, and send them elsewhere. For your recovery code, we store only a hash of a key derived from it, never the code itself, so we cannot show it to you again. With your recovery code and a code we email you, you can set a new password if you forget yours; this keeps your main key, gives you a new recovery code, removes all your passkeys, ends every session of your account at id.thehappie.co and in the console and revokes the API keys you created before the recovery, in every app they name (see “API keys”). In each of our apps that follows your workspaces, as described under “The apps and the workspaces”, a recovery also ends your sessions and stops every integration you created before it; in an app that does not follow them yet, a session already open is not ended. For each passkey, we store its identifier and public key; the name you give it (the page suggests one such as “Passkey (macOS)” when your browser reports your device’s operating system); whether it can unlock your account or only sign you in; whether it can be synced across your devices, and whether it is; when it was added and last used; and the technical record your browser gives us when you add it, which we update each time you use it and which includes, when your browser reports them, an identifier of the kind of authenticator or password manager that holds the passkey, how it connects to your device and a signature counter. A passkey you remove, or that a recovery removes, loses its copy of your main key at once, if it had one, and its record is deleted 30 days later. For each of our products, currently Wappie and Mailie, your browser derives from your main key, when you sign up, a key pair of that product: we store only its public half, which the product uses to check that the key it receives is your account’s, and which stays the same when you change your password or recover your account. When one of our apps asks for its key, the page at id.thehappie.co asks you to unlock your account with your password or with a passkey that can unlock it, derives the private half of that app’s key in your browser and seals it — encrypts it so that only the page of the app that asked can open it. We cannot open that sealed copy: it waits on our server only until that page, in your browser, collects it, and is erased once collected or, if it is never collected, within about two minutes. When you sign in to one of our apps, such as Mailie or Vaultie (app.vaultie.thehappie.co), id.thehappie.co gives that app the identifier of your account, your email address, your name, your language, when and how you signed in and, for Wappie and Mailie, the public half of that app’s key; what Mailie keeps of it is described in the sections whose titles start with “Mailie”, what Wappie keeps of it is not yet described in this policy (see “What this policy covers”), and what each of our other apps keeps of it is described in the notice of that app. We also keep your sign-in sessions at id.thehappie.co, each as a hash of its token, with when and how you signed in, when it was last used, a truncated IP address (the first three parts of an IPv4 address, the first 48 bits of an IPv6 address) and a coarse browser label such as “Chrome on macOS”, and your console sessions likewise, but without an IP address or browser label. A session at id.thehappie.co ends after at most 14 days, or 72 hours without use, and a console session after at most 12 hours, or 2 hours without use; either also ends when you or we end it. An ended session is deleted within about a minute, except a console session ended from id.thehappie.co (for example when you sign out everywhere, when you recover your account or when we disable it), which stops working at once and is deleted within about 2 hours. Our security log records sign-ups, sign-ins and failed or refused sign-ins, unlocks and failed unlocks, recoveries and attempts at one, changes and failed attempts to change your password, changes to your recovery code, passkeys, name, language and theme, warnings that a passkey may have been copied, downloads of your key bundle (a file with encrypted copies of your main key), sign-outs, attempts to sign up again with your address, sign-ins to the console and to our apps, including those you cancel and attempts to reuse the one-time code that completes such a sign-in, and your account being disabled or enabled, or its sessions ended, by us; each entry has the truncated IP address and browser label of the device or server that made the request (none for actions we take), and is kept for 13 months. Each code we email you is valid for 15 minutes. Our outgoing queue holds it in clear only until it sends the email, drops it or gives up on it; apart from that, our database keeps it only as a keyed hash (a fingerprint made with a secret key of ours), with the address and the browser it was sent for, and deletes it within about a minute after it is used or expires. While a sign-up, a recovery, a passkey step or a sign-in (at id.thehappie.co, to the console or to one of our apps) is under way, we keep, for at most 30 minutes, the records that tie its steps together — one-time values or their hashes, the address you typed or an app suggested, and the console page to return you to — and delete them within a few minutes after it finishes or expires. We also keep the addresses we add to the list of those who may sign up, each with when it was added and any note we add, until we remove it from the list or close the account with that address. At id.thehappie.co, you can yourself change your name, your language, your theme and your password, replace your recovery code, add, rename or remove passkeys, and sign out of the browser you are using or everywhere; signing out everywhere also ends your console sessions and your sessions in each of our apps that follows your workspaces, but not those in an app that does not follow them yet. In the console, and on any of our sites or apps while you are signed in to the console, you can change your language and theme; signed in, every page shows your account’s. Unless a different period is given above, we keep this data while your account exists; data we delete or replace, such as an earlier encrypted copy of your main key, can remain for up to 90 days in the encrypted backups described under “Logs and backups of id.thehappie.co and console.thehappie.co”. To close your account, write to hello@thehappie.co from its email address (we keep that correspondence as described under “Keeping your data”); we then delete this data without undue delay and within one month of your request, with eight exceptions: the entries of the security log, with a record of the closing, which we keep under your account’s identifier alone, without the truncated address and browser label, until each is 13 months old; the entries about you in the activity logs of workspaces, team or personal, which keep your account’s identifier and, for an invitation to your address, that address, until each is 13 months old; the records of the team workspace invitations you sent or that were sent to your address, each deleted 30 days after it ends or expires (for both, see “Workspace invitations”); the record that lets our apps learn of the closing: its date and time, under your account’s identifier alone, until it is 13 months old, and which of our apps you had signed in to, with what we last sent each about your account, until that app confirms it has forgotten you and for at most 30 days (for both, see “The apps and the workspaces”); the records of API keys that name you, by your account’s identifier, as the person who created the key, added an app to it, gave one of its permissions, registered its reading key or revoked it, each until 13 months after that key ends, and the permissions you gave that an app holds back, until it tells us otherwise, and those it refused, for 30 days from their receipt (see “API keys”); the billing records described under “Billing”, such as your purchases and withdrawals, with the emails and statements kept with them, each for its period there; the records of our apps’ settings that hold your account’s identifier, that is, what an app last reported of them and the changes made to them in the console by you or about you, or whose answer names you (for example as someone who still has access to a number), each for its period described under “The apps’ settings in the console”; and the keyed hashes our outgoing queue keeps for 30 days after each email (see “Emails about your account”). An email to you already waiting to be sent when you close your account is still sent, except an email about a WhatsApp number or an email account, of a team or of your personal workspace, described under “Emails about your account”, which is then not sent. Your personal workspace is then closed but kept, with only its identifier and the dates it was created and closed, and nothing that links it to your account apart from the activity log entries, the API key records, the billing records and the records of our apps’ settings above, for their periods; our products use that identifier for what you keep in them, for as long as they keep it. You also leave every team workspace you belong to: one whose last owner you were passes to its longest-standing admin or, if it has none, its longest-standing member, as owner, and one left with nobody is closed. The invitations you sent that are still open end, and those whose email has not yet gone out are never emailed. Each of these steps is recorded in the team workspace’s activity log. The API keys you created that are still valid are also revoked, in all your workspaces and in every app they name (see “API keys”). If you have a Mailie account, we close it on the same request, as described under “Mailie — how long we keep it”. In each of our apps that follows your workspaces, closing your account also makes the app forget you (apart from your account’s identifier as the creator of an API key, in a record of the key that the app keeps until 365 days after the key was created and uses only to keep the key revoked and for its own security log; as the giver of permissions on an API key, while that key is valid and up to 30 days after it ends, as described under “API keys”; and, once the app accepts changes to its settings from the console, as the person who asked for a change, someone it concerned, someone whose account it relied on or someone the app’s answer named as still having access to a number, in the record the app keeps of those changes, for 30 days after it received each one, as described under “The apps’ settings in the console”) and delete your personal workspace there and its data within 30 days, disconnecting its WhatsApp numbers and email accounts, while the team workspaces you were in keep theirs (see “The apps and the workspaces”). In an app that does not follow them yet, closing your account does not, by itself, close your account there or delete what you keep in it. We use this data to sign you in, protect your account, let you work with others in team workspaces and provide our products. Legal basis: performance of our contract with you (Art. 6(1)(b)); for sessions and the security log, our legitimate interest in keeping accounts secure (Art. 6(1)(f)); and, for the list of addresses that may sign up, our legitimate interest in opening sign-up gradually during the beta (Art. 6(1)(f)).

Cookies on id.thehappie.co and console.thehappie.co

These two addresses use only strictly necessary cookies, each valid only on the address that sets it: __Host-id_session, your sign-in session, for up to 14 days, ending after 72 hours without use; __Host-id_bind, a random value that holds nothing about you, set at your first visit to id.thehappie.co for up to 30 days, which ties each step of a sign-up, a recovery, a sign-in (at id.thehappie.co, to the console or to one of our apps), an unlock with a passkey or adding a passkey to the browser that started it; and __Host-console_session, your console session, for up to 12 hours, ending after 2 hours without use; before you sign in, the same cookie holds, for up to 10 minutes, a random value that ties the sign-in to the browser that started it and identifies nobody. Your browser also sends __Host-console_session to the console when the pages of one of our apps (such as app.wappie.thehappie.co or app.mailie.thehappie.co) ask it for the menu they show, or for your account’s name, language and theme; the console then answers with your account’s identifier, name, workspaces (with the name of each team workspace) and your role in each, language and theme. The pages of each of our apps can read this for anyone signed in to the console, whether or not that person uses that app; they get no email address, key or token this way, and keep none of it in your browser, apart from the language and theme they show, which an app may remember as it remembers its own appearance preferences, and the last menu its console screens showed you, as described below. Your browser also sends the cookies of id.thehappie.co to it from the page of one of our apps, such as app.mailie.thehappie.co, when that page completes a sign-in and, if it asked for the app’s key, collects the sealed key, as described under “Your account at the happie co.”; that request reads only __Host-id_bind and ignores your session cookie. The console sets no other cookie, apart from the two preference cookies described under “What we collect on our websites”. The id.thehappie.co and console.thehappie.co pages each keep in your browser’s local storage the language and the theme (light, dark or your system’s) they last showed you: the one you chose there or, once you sign in, your account’s. Both stay there after you sign out, so signing out does not change the page. Both pages now also keep the same in the two cookies described under “What we collect on our websites”, which win when the two differ. The id.thehappie.co page keeps nothing else there. The console.thehappie.co page, and the console screens that our apps show on their own addresses (such as app.wappie.thehappie.co), may also keep there the last menu they showed you, so that the next page can draw it at once: your account’s identifier and name, and your open workspaces, each with its identifier, its name and your role in it, never your email address, a key or a token. A page erases its copy when you sign out on it, and when it finds that your session has ended or belongs to another account; a copy that one of our apps keeps after you signed out elsewhere, on the console or in another app, is erased the next time you open that app, before anything is shown, unless you are still signed in to that app with the same account. The console.thehappie.co page keeps, for the open tab only (session storage), the time it last sent your browser to sign in, so that it can tell a browser that refuses cookies, and nothing else. Apart from those two preference cookies, the website thehappie.co uses no cookies.

Workspace invitations

When an owner or admin of a team workspace invites someone to it, we keep the invited address, who invited them, the workspace and its name, the role offered, when the invitation was sent and when it expires, and a hash of the secret in its link; once it ends, we also keep when and how it ended (accepted, declined, cancelled, replaced by a newer one, expired, or ended because the workspace was closed) and, if someone ended it, who. An invitation is valid for 7 days and works only once, and only an account with the invited address can accept it; it also ends when whoever sent it leaves the workspace, is removed, closes their account or loses the role that could send it. Its record is deleted 30 days after it ends or expires. We email the invitation to the invited address, which may not have an account yet, as described under “Emails about your account”: the email gives the inviter’s name, the workspace’s name, the role, when the invitation expires and its link, and is written in the language of the account with that address or, if there is none, in the inviter’s. If the invitation ends before its email goes out, the email is not sent. While the invitation is open, whoever opens its link sees, without signing in, the workspace’s name, the inviter’s name, the role, the invited address and when it expires; after that, the link shows only whether it was accepted, expired or otherwise ended. Someone signed in to an account with the invited address also sees the open invitation in the console, with the workspace’s name, the inviter’s name, the role and when it expires, and can accept or decline it there. Each team workspace has an activity log, without IP addresses, that records when the workspace was created (or brought into the console by us), renamed, closed or reopened; each invitation sent, cancelled, accepted or declined, with the invited address and the role offered; and the changes of its members: who joined, left, was removed or changed role (with the old and new roles), whether someone left, or an owner removed them, despite the warning described under “The apps and the workspaces”, who became owner when the last owner’s account closed, and whose account closed. In every workspace for which a plan has been bought, whether a team workspace or your personal workspace, the activity log also records, as described under “Billing”, each purchase and each increase; each reduction scheduled, each pending change undone or dropped, and each reduction; each cancellation, resumption and ending; each withdrawal; each change of payer and each payer’s departure; and each purchase we void because it should not have happened. Each of these entries holds what was done and when; the identifier of the account that did it, or none if we or our systems did it; the quantity of each of the plan’s items, and whether it is monthly or annual, as they are afterwards; the identifier of the payer’s account, but only on a change of payer and on a payer’s departure; and, for a pending change undone or dropped, the reason: an owner undid it, or a withdrawal, the payer leaving or the plan ending dropped it. None of them holds an amount, a card, an email address or an identifier at Stripe. Each entry says when and, unless we or our systems made the change, who made it; entries are never changed, and each is kept for 13 months, even after the accounts it names have closed, and then deleted. A team workspace’s owners and admins see its activity log, with the current name and email address of each account in it (an account that has closed shows as a closed account, but the invited addresses remain), and its pending invitations, each with the invited address, the role, the name and email address of who sent it, and when it was sent and expires; an admin’s list of pending invitations leaves out those that offer the owner role, though the activity log still shows them. The console shows activity logs only for team workspaces: the activity log of your personal workspace, which holds only these entries, is kept for the same 13 months but, for now, is not shown. Data we delete here can remain for up to 90 days in the encrypted backups described under “Logs and backups of id.thehappie.co and console.thehappie.co”. Legal basis: for the invited address, until the invitation is accepted, the legitimate interest of the owner or admin who invites, and of the team workspace’s other members, in inviting people to it (Art. 6(1)(f)); after it is accepted, performance of our contract (Art. 6(1)(b)); for the activity log, our legitimate interest in keeping accounts secure (Art. 6(1)(f)) and, for its entries about plans, also the legitimate interest of the workspace’s owners and admins, and ours, in knowing who bought, changed or cancelled its plan or withdrew from a purchase, and when (Art. 6(1)(f)); its entries that say how someone left a team workspace, was removed from it or had their account closed are also used to tell the workspace’s owners, other than one who removed that person, why nobody can read one of its numbers or email accounts any more, as described under “Emails about your account”, on the basis of the legitimate interest of those owners in knowing why (Art. 6(1)(f)).

Deleted numbers and email accounts

In Wappie and in Mailie, in every workspace, personal or team, only an owner can delete one of the workspace’s WhatsApp numbers (in Wappie) or email accounts (in Mailie, where this is called removing a mailbox); no other member can, except that, in Mailie, an admin can also remove a mailbox they connected whose connection was never completed. In your personal workspace, you are its only member and its owner. A number or email account that an owner deletes is kept, with its data, for 30 days, so that it can be recovered; then the app permanently deletes it. An owner can recover it within the 30 days, on the app’s screens in the account console, with its data and the people still in the workspace who could read it (in Mailie, a team’s email account that nobody could read once recovered cannot be recovered); its sync stays paused until someone resumes it or, in Mailie, if its sync was off, turns it on (in Mailie, for a team’s email account, an owner or admin), and AI assistants, and API keys limited to chosen numbers or email accounts, must be given access again. In Wappie, deleting a number also asks WhatsApp to log it out, which cannot be undone: when WhatsApp confirms the logout (the normal case), a recovered number comes back read-only, and syncing the phone again means linking it as a new number. The mapping between contacts’ phone numbers and their WhatsApp identifiers, which Wappie’s server keeps in one cache shared by every number, is not deleted with a number. In Mailie, an owner recovers a removed email account, and can also delete it for good sooner, in Mailie’s settings in the account console (see “Mailie — who is responsible”); one whose connection was never completed is deleted for good as soon as it is removed. Copies can remain in the app’s encrypted backups for up to 90 days after that; for Mailie, the period is 30 days, as described under “Mailie — how long we keep it”. Once the app is connected, we will send the workspace’s owners one email when someone deletes a number or an email account, and each person who can read the number (in Wappie) or the email account (in Mailie) one email when someone pauses or turns off its sync; we never send one to the person who did it. Each of these emails goes only to the workspace’s members at console.thehappie.co (the one about a deletion, to its owners there), even while the app still keeps its own members; it goes to the address of the recipient’s account at the happie co., in that account’s language, and at most once for each deletion or each time sync is paused or turned off, as described under “Emails about your account”; the app may also show these notices in its own pages. To let us send them, the app tells us which number or email account was deleted or had its sync paused or turned off, by its identifier in the app, the name it was given there, if it has one, and a masked hint (the last 4 digits of a number, or the first character and the domain of an email address), never by its full phone number or email address, and who did it and who can read it, by the identifiers of their accounts at the happie co. The app tells us the same when one is recovered or permanently deleted. An app tells us this, and we send these emails, only once it is connected, as described under “The apps and the workspaces”, which also says what we keep of it and for how long; until then, the app tells the people who can read a number or an email account, in its own pages, when its sync is turned off and, in Mailie, also when an email account is removed, and the workspace’s owners receive no email when one is deleted. In Mailie, which is connected, these notices in its own pages, of a removal, of a sync paused and of a sync turned off, go on beside our emails: a notice never goes to the person who did it, and it stays until its reader dismisses it, for 90 days at most; a recovery withdraws the notice of a removal, and the end of a pause withdraws the notice of that pause. Once an app also sends us its notices, as described under “The apps’ settings in the console”, the console shows each person the notices that app keeps for them and, where the app allows it, lets them dismiss them there. Legal basis: performance of our contract with you (Art. 6(1)(b)).

The apps and the workspaces

We connect our apps, Wappie and Mailie, to console.thehappie.co one at a time, over a private connection on the same server, so that each can follow the workspaces, members and roles of your account at the happie co., tell us who can do what with each of its WhatsApp numbers and email accounts and, once it takes the API keys of your workspaces, check those keys (see “API keys”). Until an app is connected, none of what follows is exchanged with it; a test that only checks the connection exchanges no personal data and does not count as connecting it; once an app is connected, the exchange about you starts when it first follows your account, at your sign-in to it, or reports on a workspace you belong to. A connected app follows your workspaces once it takes its members from them. Before that, Wappie goes through a stage in which it only compares the members and roles we send with its own and changes none of them; Mailie has no such stage. From the moment an app is connected, though, everything described below already applies, except what an app that follows your workspaces does, which starts only once it follows them. An app that follows your workspaces keeps, from what we send it, your workspaces, your role in each and what we last sent it about your account, for as long as it keeps you; what else Mailie keeps is described in the sections whose titles start with “Mailie”, what else Wappie keeps is not yet described in this policy (see “What this policy covers”), and what each app keeps of API keys is described under “API keys”. What each app keeps of the changes made to its settings in the console, and how long Wappie keeps its notices, are described under “The apps’ settings in the console”. For each person who has signed in to a connected app with an account at the happie co., we send that app, when they sign in and whenever it changes: the account’s identifier; whether it is active, disabled by us or closed; when we last disabled it, when all its sessions were last ended (by signing out everywhere, by a password change that signs out the other sessions, by a recovery or by us) and when it was last recovered; and each of its workspaces, with the workspace’s identifier, whether it is personal or a team and whether it is open or closed, the person’s role in it and, for a team, its name and how many owners it has. What we send an app about you never includes your email address or your name; nor does it include any key, apart from the reading key (a public key) of an API key that names that app, of which we also send the prefix and a one-way hash of the rest, never the API key itself; nor who the other members of your workspaces are, apart from who created such an API key and who gave it its permissions, by the identifiers of their accounts (see “API keys”); a change described under “The apps’ settings in the console” names another member only by the identifier of an account that app already knows. For each workspace we have told it of, a connected app sends us, soon after each change and at least every hour, a report of its WhatsApp numbers (in Wappie) or email accounts (in Mailie) there. For each one, the report gives an identifier of the app’s own; the name a person gave it in the app, if any, but never its phone number or email address (a name that contains an @ is left out, and any run of 7 or more digits is shortened to its last 4, by the app and again by us); a masked hint: the last 4 digits of a number, or the first character and the domain of an email address; a sequence number from 1 to 9999, which Wappie, once it takes the API keys of your workspaces, sends for every WhatsApp number that has one, named or not (Mailie sends none yet), and which the console shows when the name is missing; whether it is active, paused (and why) or deleted (and when it goes for good); and, by the identifiers of their accounts at the happie co., who can read it, send from it, act on its messages or manage it, who is waiting for its key, who has set up their own key in the app, who holds a key to it and whose loss would leave nobody able to read it, and only how many other key holders it has without an account at the happie co., never who they are; and, from an app that takes the API keys of your workspaces, which of those keys can use it, with what each can do there, whether it reads it and whether it still waits for access in the app (see “API keys”). In these reports, we keep only the people who are still members of the workspace. A connected app also tells us when one of these numbers or email accounts is deleted, recovered or deleted for good, when a person pauses or turns off its sync, when an API key pauses a number’s sync, when a number moves out of a team workspace into the personal workspace of the person who moves it, and when one is left with nobody who can read it, with the person whose loss caused it and, if the app knows, why (if it does not, we take from the team workspace’s activity log whether that person left, was removed or closed their account, and who removed them); each time, with its identifier, name and hint as above, the workspace, when it happened and, for a deletion, when it goes for good, who did it (for an API key, the person who created it) and who could read it just before, by the identifiers of their accounts, never a phone number or an email address. In the console, a team workspace’s owners and admins see, for each connected app, its numbers or email accounts in the workspace, who can do what with each, API keys included, which members have opened that app, and whether that app’s latest report is missing or more than 90 minutes old; other members see, of these reports, only the numbers and email accounts they are on, and only what they themselves can do. In your personal workspace, you see your own. What else an app sends us once it also sends its settings, who sees it in the console and what we pass to the app when someone changes them are described under “The apps’ settings in the console”. We use what we send so that each connected app can follow your workspaces, and what the apps send us to show it in the console; to refuse to remove someone from a team workspace when they are the only one who can read one of its numbers or email accounts, or when we cannot tell because an app’s latest report is missing or out of date, unless an owner removes them anyway after a warning (they can still leave, after the same warning); and to send the emails described under “Deleted numbers and email accounts” and “Emails about your account”. An app that follows your workspaces applies what we send: when you leave a team workspace or are removed from it, it ends your access to that workspace; when all your sessions are ended, it ends your sessions in the app; after a recovery, it also stops every integration you created before it, in every workspace (API keys, assistants and AI connections, and service accounts); and when we disable your account, it suspends you, ending your sessions, API keys and connections, and keeps your keys to its numbers and email accounts, unusable, until we enable your account again or it closes. When your account closes, such an app confirms the closing with us, forgets you (apart from your account’s identifier as the creator of an API key, in a record of the key that the app keeps until 365 days after the key was created and uses only to keep the key revoked and for its own security log; as the giver of permissions on an API key, while that key is valid and up to 30 days after it ends, as described under “API keys”; and, once the app accepts changes to its settings from the console, as the person who asked for a change, someone it concerned, someone whose account it relied on or someone the app’s answer named as still having access to a number, in the record the app keeps of those changes, for 30 days after it received each one, as described under “The apps’ settings in the console”) and deletes your personal workspace and its data without undue delay and within 30 days, disconnecting its WhatsApp numbers and email accounts; the team workspaces you were in keep their data, and the app’s own backups follow its own periods. We keep each app’s latest report on a workspace until its next report replaces it; a number or email account deleted for good leaves it, and so do your lines when you leave a team workspace or are removed from it; the reports on a closed team workspace, including which API keys can use each of its numbers or email accounts, are deleted 30 days after it closes, unless it reopens first, and a report that arrives after that, while it is still closed, is not kept. We keep which of our apps you have signed in to until that app tells us it no longer keeps you, and what we last sent each app about you for as long as it does. Of each event, we keep only its type, the identifier and kind of the number or email account, the workspace and when it happened and arrived, for 30 days; the names an email needs go only to our outgoing queue, which erases them as it erases the address (see “Emails about your account”). When your account closes, we delete at once what the apps reported about your personal workspace, including which API keys could use each of its numbers or email accounts, but keep what they sent us about those keys themselves (when they applied a change, the last day each was used, and what they refused, held back or suspended), as described under “API keys”, and the apps’ answers to the changes described under “The apps’ settings in the console”, kept with those changes; we keep which apps you had signed in to, and what we last sent each about you, until that app confirms it has forgotten you and for at most 30 days, and the date and time of the closing, under your account’s identifier alone, for 13 months, so that an app restored from a backup can still confirm it. Data we delete here can remain for up to 90 days in the encrypted backups described under “Logs and backups of id.thehappie.co and console.thehappie.co”. Legal basis: performance of our contract with you (Art. 6(1)(b)); for refusing to remove someone, or to let them leave without a warning, when that would leave one of a team workspace’s numbers or email accounts with nobody who can read it, the legitimate interest of that team workspace’s owners and other members in keeping it readable (Art. 6(1)(f)); and, for what we keep after your account closes so that each app learns of the closing and, once it follows your workspaces, deletes your data, our legitimate interest in making sure that it does (Art. 6(1)(f)).

API keys

On the API keys page of console.thehappie.co, a team workspace’s owners and admins, and you in your personal workspace, can create API keys for those of our apps that take them: an API key gives a program, such as an AI assistant, access to the workspace’s WhatsApp numbers or email accounts in those apps, within what the key allows, and whoever holds the key can do what it allows until it expires or is revoked. Each app starts taking these keys at a time of its own, and the page offers an app only once it takes them and we have told it of the workspace; until then, Mailie’s own API keys are described in the sections whose titles start with “Mailie”. Wappie’s own API keys are not yet described in this policy (see “What this policy covers”), apart from what Wappie sends us of its older local MCP tokens once it also sends its settings (see “The apps’ settings in the console”) and what it tells us when one of its own API keys pauses a number’s sync (see “The apps and the workspaces”). An app may take the API keys of your workspaces before it follows them, as described under “The apps and the workspaces”; until it follows them, it also checks whoever created a key, and whoever gave each of its permissions, against its own members and roles. A key may name several apps, and works in each of them only on the numbers or email accounts given to it there and only with the permissions given on each: in Wappie, reading, sending and managing (which includes pausing and resuming a number’s sync), each on its own, on each number; in Mailie, reading each email account of your personal workspace that it is given and, together with reading, acting on that account’s messages, but not sending. Nothing is given by default: a number or email account connected later gets nothing until someone gives it access, and no key can connect a new number or email account, delete, recover or move one, or change the workspace’s members or keys. Only an owner or admin who reads a number or email account in that app, according to the app’s latest report on the workspace, if that report is no more than 90 minutes old, may give a key permission to read it, and the app checks this again itself; in Wappie, a key reads a number only once an owner or admin who reads that number has also given it access in Wappie itself, through the key’s reading key, described below. Creating a key, or giving one more access, requires a sign-in to the console in the last 10 minutes. A key is valid for 30, 90 or 365 days, chosen when it is created, and its validity can later be shortened, never extended; a workspace can hold at most 100 active keys, and an account can create at most 10 keys a day, which we count by the identifier of the account, keeping each day’s count for 2 days. An app may have its own terms for API keys, as Mailie does (see “Mailie — API key terms” in our Terms of Use): the key’s creator must then agree to the revision of those terms that the console names, which we publish there, before that app is added to the key, and only the creator can add it. The key itself is shown only once, when it is created; we never store it, and it never appears in our logs: we keep only its prefix, the part that identifies the key and is not secret, and a SHA-256 hash of the rest, a one-way fingerprint from which the key cannot be rebuilt (the rest is random and long enough that no slower calculation is needed). For each key, we also keep its name (a name with an @ is refused, and any run of 7 or more digits in it is shortened to its last 4); the workspace; who created it, by the identifier of their account, and when; when it expires; each app it names, with who added that app and when and, for an app with terms for API keys, the revision the key’s creator agreed to and when; each permission, with the number or email account it is on, who gave it, by the identifier of their account, and when; its reading key, if one was registered, with its fingerprint, who registered it and when; and, once it is revoked, in every app or in one, when and why and, if an owner or admin revoked it in every app from the console, who did. Each app that takes these keys sends us, for each key that names it: when it applied the latest change to the key; the last day on which it accepted the key, of which we keep only the latest; the permissions it holds back until it can check who gave them, and those it refused, with the reason, which then leave the key; whether it has suspended the key on its own, and why; after we restore our database from one of our backups, any part of the key it still holds more narrowly than we do, which we then narrow in the same way; and, for each day, how many uses of the key it refused, with the number or email account, the permission and the reason. None of this includes an IP address, the time of a use or what the program asked for or received. In its report on a workspace, described under “The apps and the workspaces”, such an app also lists, for each number or email account, the keys that can use it, with what each can do there, whether it reads it and whether it still waits for access in the app. For each workspace we have told it of, over the connection described under “The apps and the workspaces”, we send each app every key that names it, and again whenever the key changes: its identifier, the same in every app it names; the version of what we send about it; its name, prefix and hash; the workspace; who created it, by the identifier of their account, and when; when it expires (or the earlier expiry the app holds); whether, when and why it was revoked, in that app or in all; the revision of that app’s terms for API keys the key’s creator agreed to, and when; its reading key, if any, with its fingerprint and when it was registered; and, while it is not revoked, each number or email account of that app given to it, with each permission, who gave it, by the identifier of their account, and when. We never send an app the key itself, who added an app to it, registered its reading key or revoked it, its last use, or its terms or permissions in another app. Each app checks keys itself, from what we send it, so that, once it has caught up with what we have sent it, they keep working while console.thehappie.co cannot be reached, except for sending and managing, which an app refuses once it has had no news of the keys from us for an hour; it keeps what we send it about a key for at most 30 days after the key expires, is revoked or is dropped from the keys we send that app. After that, until 365 days after the key was created, it keeps only a record of the key, which it uses only to keep the key revoked and for its own security log and which holds at most the key’s identifier, prefix, hash and reading key; who created it; its workspace; when it was created and expires; when and how it ended and, if it was revoked, why; the app’s own record of each suspension of it; the versions of what we sent about it and when the app applied them; and the identifier of any internal account the app made for the key; an app may keep less, but never less than the key’s revocation, so that a revoked key never works there again. Each time an app suspends a key, it may also keep, outside its database, a copy of the key’s prefix and of when the suspension was made and lifted, so that it can reinstate the suspension if it restores its database, for 365 days after writing each entry of that copy; the app’s own backups follow its own periods. Once Wappie takes these keys, a cleanup that it runs every hour deletes a key’s name, its permissions and who gave each, and the full copy of what we sent about it, once 30 days have passed since the key expired, was revoked or was dropped from the keys we send Wappie or, if sooner, once 365 days have passed since it was created. Once 365 days have passed since the key was created, the same cleanup also deletes, within the hour, for every key Wappie held, however it ended (revoked, expired or dropped from the keys we send Wappie) and whether or not Wappie suspended it: its identifier and workspace; when it was created and expires; when and how it ended and, if it was revoked, why; its prefix, hash and reading key; the identifier of its creator’s account; the versions of what we sent about it and when Wappie applied them; the identifier of the internal account Wappie made for the key (the account itself is deleted when the key ends); and Wappie’s own record of each suspension of it, made by Wappie’s operator or by Wappie itself: when it was made and lifted, the server account that made it and any note the operator wrote. Wappie keeps the revocation of a key it never held, with the key’s identifier, until 365 days after that key was created. For each suspension made by Wappie’s operator, Wappie also keeps on its server, outside its database, a copy of the key’s prefix and of when the suspension was made and lifted, so that it can reinstate the suspension if it restores its database, and deletes each entry of that copy 365 days after writing it. What Mailie keeps of these keys is described under “Mailie — how long we keep it”. An app that takes these keys may also let us suspend a key in that app alone, for example if it leaked; the console then shows the key as suspended there. An API key may have a reading key: a public key made by the program that uses the API key, whose private half stays with that program: we never receive it; an owner or admin registers it when creating the API key or once later, and it never changes. In Wappie, once it takes these keys, an owner or admin who reads a number gives an API key access to that number by sealing, in their browser and on Wappie’s own pages, the number’s key to the API key’s reading key, so that the program opens the number’s content itself; the console never receives a number’s key, and Wappie deletes these sealed copies when it applies the API key’s revocation, when the key is dropped from the keys we send Wappie, or within about an hour after the key expires; the copy for a single number also goes when the key can no longer read that number, or when the number is taken off the key, deleted or moved out of its team workspace. Mailie does not use reading keys yet: in Mailie, an API key’s permission to read is only a permission, as described under “Mailie — your messages”. An owner or admin can revoke a key at any time in the console, in every app at once: within seconds, we send the revocation to every app the key names, and each app applies it as soon as it receives it. We also revoke a key, in every app, when whoever created it leaves the workspace or is removed from it or their account closes and, if they created it before, when they recover their account or we disable it; a revoked key stays revoked, even if we enable that account again. Changing someone’s role, or signing out everywhere, revokes no key. Taking an app off a key revokes the key in that app for good, and a number or email account that is deleted, or moves out of the workspace, leaves every key, which a recovery does not undo. Only a workspace’s owners and admins (in your personal workspace, you) see its keys in the console: for each, its name and prefix, who created it (by their name or, if they have none, their email address, while they are still in the workspace) and when, when it expires or was revoked and why, the fingerprint of its reading key and, for each app it names, its permissions, whether and when the app has applied it, whether the app has suspended it, which permissions the app holds back or refused and why, the last day the key was used there and how many uses the app refused in the last 30 days. Other members do not see the workspace’s keys, although our email saying that a key paused a number’s sync names the person who created the key, by their name, if they have one and are still an owner or admin of the team workspace (see “Emails about your account”), and so may the notices that the console shows once an app sends them (see “The apps’ settings in the console”). We keep a key, with its apps, permissions, reading key and the last day each app used it, while it is valid and for 13 months after it expires or is revoked in every app (taking an app off it starts no period), even after the accounts of whoever created it or gave its permissions have closed; what we send the apps about it and when each app applied the latest change to it, until 365 days after it was created, so that an app restored from one of its own backups still learns of every revocation; the permissions the apps refused, for 30 days from their receipt, and how many uses of it they refused each day, for 30 days from the day of the use; and what an app holds back or has suspended, until it tells us otherwise and no longer than we keep the key. Data we delete here can remain for up to 90 days in the encrypted backups described under “Logs and backups of id.thehappie.co and console.thehappie.co”. We use this data to issue, show, change and revoke keys, so that each app can check them, and to show a workspace’s owners and admins how its keys are used and what the apps refused. Legal basis: performance of our contract with you (Art. 6(1)(b)); for keeping a key for 13 months after it ends, with who created it, gave its permissions and revoked it, the legitimate interest of the workspace’s owners and admins, and ours, in knowing afterwards which keys could reach its numbers and email accounts, and who gave them that access (Art. 6(1)(f)); and, for what an app keeps of a key after the key ends and for its copy of its suspensions of a key, our legitimate interest in keeping the app secure, so that a revoked key never works there again and a suspended key stays suspended after the app restores its database (Art. 6(1)(f)).

The apps’ settings in the console

Once one of our connected apps, Wappie or Mailie, also sends us its settings, the console shows that app’s settings on pages of console.thehappie.co, based on what the app reports, and passes to the app the changes people make there; until then, none of what this section describes is exchanged with that app, and the console takes you to the app’s own screens for its settings. Only the editions of Wappie and Mailie that we run send us their settings: a self-hosted edition sends us none of this itself, and what we hold about a self-hosted Wappie installation comes from what Wappie, which we run, reports of it and from the changes people make in the console, as described below. Such an app sends us, over the private connection described under “The apps and the workspaces”, soon after each change and at least every hour, a report of each part of its settings in each workspace we have told it of (in Wappie, its numbers, its AI integrations, its assistants connected over MCP, the protocol through which assistants such as Claude or ChatGPT reach Wappie, and its self-hosted installations; in Mailie, its email accounts and its members), and a report of each person’s own settings in it, for each person who has signed in to it with an account at the happie co.; each report also says when it was made and which of the changes described below the app accepts from the console at that moment. These reports may hold names: those that people gave to AI integrations, AI provider keys, Wappie’s older local MCP tokens, self-hosted installations and the numbers that hold one of their licences; the name of each assistant’s connection; and the name an assistant gives itself. Each follows the rule for names described under “The apps and the workspaces” (a name that contains an @ is left out, and any run of 7 or more digits is shortened to its last 4, by the app and again by us) and has at most 80 characters. They may also hold, for an assistant connected over MCP, the domain Wappie verified for it and its main domain; and, for a self-hosted installation, the address that one of the workspace’s owners or admins gave for that Wappie server: https:// followed by a domain name or a public IPv4 address, sometimes with a port; we check only that it has this form, never whose address it is, and our servers, Wappie’s included, never connect to it; the console shows these addresses as text, never as links. They also hold the state of each number or email account: for a number, the state of its link to WhatsApp (being linked, connected, disconnected, logged out or banned) and when it was last connected, whether its sync is paused and can be resumed, whether it is read-only and whether a deleted one can still be recovered; for an email account, its provider (Google, Microsoft, iCloud or another IMAP server) and whether Mailie signs in to it through the provider or with a password, whether it is connected or needs attention, with a reason from a fixed list, never the provider’s error, when it was connected, whether Mailie itself saves a copy of what is sent from it in its Sent folder, at the provider (Gmail and Microsoft save their own), whether anyone can read it, whether its sync is on, paused or off, how much of it is indexed and when it last synced, and, for a removed one, when it goes for good and whether its index is kept; for both, the version number of its current key, never the key itself; and, for the workspace, whether a number can be linked now, how many free places its plan has, whether it is paused for storage and which numbers are being registered (in Wappie), or whether Mailie can be used there, who may connect an email account and which revision of the text on a team’s sync it accepts (in Mailie). In Wappie, they also hold whether AI is on in the workspace and which AI functions and providers Wappie’s server has turned off; each AI provider key, with its provider (Anthropic, OpenAI or Google) and when it was added, never the key itself; and each AI integration, with its state and dates, and why it ended, its functions (audio, video, images and documents), each with its provider, its monthly cap and how much of it is used, its numbers and its alerts, such as a key the provider refused. For assistants connected over MCP, they hold the workspace’s four switches (message text, attachments, drafts and sending, and AI), each as chosen and as in effect, with what Wappie’s server allows and when they last changed; each connection, with what it reads (metadata or content), its state and dates, and why it ended, whether Wappie has tested that assistant, the choices made when consenting to it (such as text, attachments and sending) and how many days of history it may read, its numbers, the limits it reached and whether its sending is paused; how many renewals are waiting; Wappie’s older local MCP tokens; and, for each connection and each of the last 30 days on which it did something, how many drafts it prepared and how many messages it sent, never to whom or what. For self-hosted installations, they hold how many licences the workspace has, if there is a limit, and how many of them are in use, and how many of its numbers we host; each installation, with when it was added; and each number at an installation that holds one of those licences, with whether its licence is reserved or in use, when it was assigned and when it expires. In Mailie, they hold, for each member of the workspace whom Mailie knows, whether they are active, suspended, held or disabled in Mailie, and whether they have set up their own key there. They name people only by the identifiers of their accounts at the happie co., to say who did what and whom it concerns: in Wappie, who paused a number’s sync (for an API key, the person who created it), who added each AI provider key, who created each AI integration and each older local MCP token, who consented to each assistant’s connection and who marked it as seen, for whom renewals are waiting, who last changed the switches and, for each number of a team workspace with only one owner, who else has access to it, which keeps that owner from moving it to their personal workspace (people by those identifiers; assistants, AI integrations, service accounts and older local MCP tokens by the app’s own; and API keys by ours); and, in Mailie, who connected each email account, who gave the team’s agreement to its sync, when and to which revision, and whether that agreement still rests only on the consent of whoever connected it, and who paused its sync. Unlike the reports described under “The apps and the workspaces”, these keep the identifiers of people who have since left the workspace, for as long as the app still names them; the console never names such a person, and shows them as a former member. A person’s own report holds when they last signed out of every session in that app and up to 300 of the newest notices that app keeps for them; in Mailie, it also holds their choices on sync, actions on messages and sending, each with whether it is on or off (actions and sending are also paused when they were allowed under a text Mailie no longer accepts), the revision of the text agreed to when it was made, and when it was made and, for actions and sending, when it was withdrawn; the revisions of these texts and of its terms for API keys that Mailie accepts now; and whether they have set up their own key in Mailie. A notice says what happened (that a number or email account was deleted, and until when it can be recovered, that its sync was paused or turned off, that a number was moved out of a team workspace, or that a deleted number lost the last person who held its key), in which workspace, to which number or email account, by the app’s identifier, and when; it keeps the name and the masked hint the app took for that number or email account (the last 4 digits of a number, or the first character and the domain of an email address), so that it can still name one that is gone, though Mailie forgets an email account’s name when it deletes it for good and keeps only its masked hint for as long as a notice needs it; and some notices also say who did it, by the identifier of their account. A notice never goes to the person who did it. In a notice, the console names who did it, by the name of their account at the happie co., which we take from our own records, if that account has a name, only in these cases and only while that person and you are both members of the workspace: to the people who can read one of a team workspace’s numbers or email accounts, which of the team’s owners or admins paused or turned off the sync of that number or email account (for an API key that paused a number’s sync, the person who created the key, if they are one of them); and, to a team workspace’s owners, who deleted one of its numbers, moved one out of the team or, from a deleted number, removed the last person who held its key. Any other notice names nobody. None of these reports, nor any answer to a change, holds a phone number or an email address (only the masked hints above), a postal address, a WhatsApp profile name or picture, an identifier in WhatsApp (LID), the name of a folder or of a chat, a chat’s identifier, a redirect address, anything from the content of a message, a key, a sealed copy of a key, a password or a token, or any part of one, or the text of an error; reasons and states come from fixed lists, and a list of who or what has access is never shortened without saying so. In the console, every member of a workspace sees, of an app’s settings there, the workspace’s own state in that app, such as whether a number can be linked; the numbers they can read, send from or manage, or the email accounts they have any permission on, though not who did what to them, other than in the notices described above; in Wappie, the switches for assistants, the AI provider keys they added, the AI integrations they created and the connections they consented to, with what the app reports of them; and, in Mailie, their own status there. Owners and admins also see the rest, including who did what and the self-hosted installations, apart from other people’s AI provider keys; only owners see deleted numbers, removed email accounts and who else has access to a number of a team with only one owner; and a person’s own settings and notices are shown only to that person. The console shows what an app last reported, says when, and says when a report is incomplete or more than 90 minutes old. When you change one of these settings in the console, we pass the change to the app, which checks again that you may make it and that its own rules allow it, makes it or refuses it with a reason from a fixed list, and tells us the result; the console shows how your request stands and the app’s answer only to you, and no longer once you leave that workspace, while what the change then does shows in the app’s settings, as the app reports them, to those who may see them, as described above; we write nothing about it in the workspace’s activity log. Each change we pass is signed by us and holds: the kind of change, from a fixed list; the workspace (none for your own settings); the identifier of your account and your role there; what it is about, by identifiers only: a number or email account, another person’s account, one of the app’s own records or a switch; one setting’s value before and after, such as a number’s old and new name, what someone may do with a number or email account, or, to add a self-hosted installation, its address and name; your confirmation of what you remove or delete for good; for an agreement, the revision of the text you agreed to and the language it was shown to you in; the versions of what we last sent the app about you and about the person it concerns; and when it was issued, when it was first issued and, unless it only takes something away, when it expires, 5 minutes after it was first issued. We pass a change only when that app already follows your account and the account of every person it concerns, because each of you has signed in to it or was already one of its users when it began to follow you, and we first send the app what we send about each of you, as described under “The apps and the workspaces”: so a change never tells an app about anyone it does not already know, and it never holds the name or email address of your account or anyone else’s, a key or a password. The app’s answer says whether it made the change and, depending on the change, may hold the name as the app would save it after applying the rule for names, how many of your sessions it ended, which switches also went off, that an email account was deleted for good at once, or who else still has access to a number, by the identifiers of their accounts, by the app’s own or, for API keys, by ours. If the app asks us to try again, we pass the change again after the wait the app names, at most an hour, or else after at most 5 minutes; if it refused the change because it does not accept that kind of change at that moment, that refusal is final, unless the change only takes something away, in which case we pass it again once the app accepts that kind of change again; if it refused it because the workspace is closed, we pass it again once the workspace reopens; but a change that does not only take something away still lapses 5 minutes after we first issued it. In a closed workspace, the console offers no change. If an app has not asked us for changes for about 2 minutes, the console shows its settings as the app last reported them, with the time, and passes on only the changes that only take something away, such as withdrawing a consent, taking someone’s or something’s access away or narrowing it, turning off a switch or the sync of a team’s email account, or ending your sessions. Such a change has no 5-minute limit: we keep passing it until the app makes it or refuses it for good, and it lapses once 30 days pass after we last passed it without the app making it; and we pass it again to an app restored from a backup, so that a restore never gives back what someone took away. An app that does not follow your workspaces yet also checks each change against its own members and roles, and refuses it where they differ from ours. What needs a key, a password or the app’s own check that it is you stays in the app, such as linking a number or an email account, letting someone read it, connecting an assistant, adding an AI provider key, deleting or recovering a Wappie number, and reading or sending messages: for these, the console opens a page of the app whose address holds only identifiers, never a name or an address, and that page brings you back; the console never holds a number’s or an email account’s key, its credentials or its messages. In each app that accepts it from the console, you can also sign out of every session of yours in that app alone, which leaves your API keys and your connections to assistants and to AI as they are. We use these reports to show each app’s settings in the console and to offer only the changes that the app accepts and that you may make, and the changes you make to pass them to the app and show you their results. We keep only the latest report of each part of an app’s settings in a workspace, and of each person’s own settings in an app, until the app’s next report replaces it. The reports on a personal workspace are deleted when its account closes, and a report that arrives later is not kept; a team workspace’s are kept while it is closed, so that it can reopen with them, and deleted 30 days after it closes, unless it reopens first (a report that arrives after that, while it is still closed, is deleted within a minute); and a person’s own report in an app is deleted when the app stops following their account, with our record that they have signed in to that app, described under “The apps and the workspaces”: when the app tells us it no longer keeps them or, after their account closes, at the latest 30 days later. We keep each change, with your request and the app’s answers, until 30 days after we last pass it to the app or after the app’s last answer, whichever is later, or, for a change that took something away and that the app made, until 90 days after its answer, so that we can pass it again to an app restored from a backup. These stay for their periods after you leave the workspace or your account closes. Each app keeps its own record of the changes it took, each with the app’s answer, and so with the identifier of your account and those of the people the change concerned or the answer names, for 30 days after it took each change, even after one of those accounts closes, so that a change passed twice is made only once; a change that took something away and that we pass again after an app restores a backup is made again, unless the app’s record still holds it. Wappie deletes its notices, unless they go sooner, in a cleanup that runs every hour: each notice, once 30 days have passed since its person saw it, and one not yet seen, once 30 days have passed since the paused sync resumed or the deleted number was deleted for good, or once that person no longer reads the paused number, while one that a number moved out of a team or lost the last person who held its key may stay until it is seen; Mailie keeps its notices as described under “Deleted numbers and email accounts”. Our service’s logs name a change only by its app and its identifier, never by a name, a person or what it changed. Data we delete here can remain for up to 90 days in the encrypted backups described under “Logs and backups of id.thehappie.co and console.thehappie.co”. Legal basis: performance of our contract with you (Art. 6(1)(b)); for showing a team workspace’s owners and admins who did what in its apps, and the people who read its numbers and email accounts who paused or turned off their sync, the legitimate interest of those people in running the workspace and in knowing what happened to what they read (Art. 6(1)(f)); and, for keeping for 90 days the changes that took something away, our legitimate interest in making sure that an app restored from a backup does not give back access that someone took away (Art. 6(1)(f)).

Billing

An owner of a workspace, personal or team, can buy a plan for it at console.thehappie.co. For now, billing runs in the test mode of Stripe, our payment provider: nothing is really charged, the console says so on every billing page, and so does the email that confirms each purchase. When billing moves to live mode, the plans bought in test mode end and are not carried over, and their records stay, marked as test. Payments are processed for us by Stripe Payments Europe, Limited, in Ireland, as our processor; it also computes VAT, and Stripe may transfer the data it receives, described in this section, to the United States and other countries under the EU–US Data Privacy Framework and the European Commission’s standard contractual clauses. For some purposes of its own, such as preventing fraud and meeting its legal duties as a payment provider, Stripe uses that data as a controller in its own right, as its privacy policy describes. You enter your card and your billing details on Stripe’s own pages (its checkout, its billing portal and its invoice pages), never on ours, and they reach Stripe even in test mode. Stripe’s pages ask for a card and a billing address, which we need to take payment and to apply the right VAT: without them, you cannot buy a plan or become its payer; adding a tax ID is up to you. Each workspace in which an owner has started a purchase has one customer record at Stripe. It holds our identifier of the workspace, never its name; the preferred language; any tax ID, such as a VAT number, that a business adds; the payer’s card; and, only while someone is the payer or has a checkout open for a first purchase, that person’s contact details: the email address of their account at the happie co. and the name and billing address they give at checkout. The record is created with the email address of the owner who starts the workspace’s first checkout. If that checkout ends without a purchase, because it expires or is abandoned, and the workspace has no plan, the record’s email address, name and address are cleared. A later checkout, by any owner, sets that owner’s email address, and that owner becomes the payer when it completes. The payer is the one owner whose card pays the plan: at first, whoever bought it. Another owner can become the payer by entering their own card at Stripe; the customer record’s email address, name and address then become theirs, its tax IDs are cleared, and the previous payer’s card is removed from it. When the payer leaves the workspace, is removed from it, stops being an owner or closes their account, and whenever a plan ends, for whatever cause, the payer’s card is removed from the customer record, and the record’s name, address, email address and tax IDs are cleared; after a plan ends, a new checkout sets them again. An invoice that Stripe has issued cannot be deleted: it keeps its own copy of the details it was issued with, and Stripe keeps it for as long as our account at Stripe exists; we keep our own records of purchases and withdrawals for the 7 years given below. We record who the payer is, by their account’s identifier, since when, and Stripe’s identifier of their card (never the card’s number), until they leave the workspace, are removed from it, stop being an owner or close their account, or another owner becomes the payer. In the console, every member of a workspace sees the state of its plan (until when its free trial runs, whether it has a plan, and whether a payment is pending or the plan is ending); its owners and admins also see the plan’s details, the payer’s name and the list of its purchases, each with its date, items, amount and buyer and, if it was withdrawn, when. The owners of a team workspace share its billing portal at Stripe: each of them sees there the invoices and their receipts, with the details they were issued with, and the payer’s name, billing address and tax IDs, and can change those details but not the card. The portal, the invoices and the receipts may also show the card’s brand and last four digits, and the billing email address, which cannot be changed there. You also see, in the console, your own purchases in every workspace, even after you leave one, and can withdraw from a purchase there while that is still possible. For each purchase, we keep the account that bought it and when; the workspace’s kind (personal or team) and, for a team workspace, its name at that time; what was bought (the items, monthly or annual, the prices, the amount paid with VAT and its currency); the dates shown for when charging starts and when the plan renews; your request to start at once, with its time, its language, the version of the text you were shown and the version of the terms in force; Stripe’s identifiers of the checkout, the subscription and the invoice; until when it can be withdrawn and, if it was, when and whether by its buyer; if we voided it because it should not have happened (for example, because it completed after its workspace closed or its buyer left it), when and why; and the email that confirmed the contract, as we sent it. For each withdrawal, we keep how it was made (in the console or by email) and, in the console, the account that made it; the statement, which is the name and the email address given for our acknowledgement, with its date and time (in the console, that address is the one of the account that withdraws, and cannot be changed; by email, it is the address you give us, and we also keep your email itself, with anything you put in it, such as the postal address the model form asks for, as described under “Keeping your data”); the acknowledgement, as we sent it; and the refund, with its amount, Stripe’s identifiers of the credit notes and refunds, its status and when it completed. After each purchase, we email the buyer a confirmation with our details as given in our terms, the plan, the price, the dates, the request to start at once and its time, the information on withdrawal and the model withdrawal form; we email the acknowledgement of each withdrawal to the statement’s address and, when someone other than the buyer withdrew, a copy, with the statement’s name and email address, to the buyer, if their account still exists; and, when a first purchase is withdrawn and its plan ends, we tell the workspace’s other owners, without the statement’s email address. These emails are sent as described under “Emails about your account”. Each purchase, change, cancellation, resumption and ending of a plan, each withdrawal and each change or departure of its payer is also recorded in the workspace’s activity log, as described under “Workspace invitations”. To run billing, we also keep a copy of each plan’s state at Stripe (its identifier, its status, monthly or annual, its items, its period, when it is cancelled or ends and why, the identifiers and states of its invoices, a scheduled change, whether VAT is being computed on it, and the identifiers of the card it is charged to); a record of each billing operation, such as a cancellation, a resumption, a change of payer, a withdrawal or an ending, which names the account that asked for it, unless we or our systems did it, with what it changes (such as the items, the facts of a request to start at once, when it takes effect or a departing payer’s card identifier), its steps, Stripe’s identifiers and an error code of our own; each checkout an owner starts, which expires 35 minutes after it starts, with who started it, what it buys, its total and language, the request to start at once, the dates it shows, its identifier at Stripe and its state; and the notices Stripe sends us about changes there, of which we keep the notice’s identifier and type, the type and identifier of what it is about, where we route it, the customer’s identifier at Stripe and when we received and processed it, but never the notice’s content, and fetch the rest from Stripe. We keep each purchase, with the request to start at once, the confirmation of the contract, and the workspace’s kind and, for a team workspace, its name, for 7 years from the end of the calendar year in which it was made, and each withdrawal, with the statement and the acknowledgement, for 7 years from the end of the calendar year in which it was submitted, the period the Estonian Accounting Act (§ 12) sets for accounting records; the copy of a plan’s state, while the plan is live and then until the last purchase made under that plan is deleted; the record of each billing operation, for 13 months after it ends; each checkout, for 30 days after it is completed, expires, is abandoned or is replaced by a newer one; each notice from Stripe, for 30 days after we process it or give up on it; and the workspace’s customer record, with its identifier at Stripe, the payer and our index of its identifiers at Stripe, for as long as the workspace has a live plan or a billing record, except the payer, whom we clear at once when they go. These records name people only by their account’s identifier, apart from the statements and the emails we keep, and they stay for their periods after an account or a workspace closes. Data we delete here can remain for up to 90 days in the encrypted backups described under “Logs and backups of id.thehappie.co and console.thehappie.co”. Legal basis: performance of our contract with you (Art. 6(1)(b)); for the confirmation of each purchase and the acknowledgement of each withdrawal, which consumer law requires us to send, and for the records of purchases and withdrawals made in live mode, which we keep for 7 years, also our obligations under consumer, accounting and tax law (Art. 6(1)(c)); for the requests to start at once and the withdrawal statements, and for the records of purchases and withdrawals made in test mode, for which nothing is charged, also our legitimate interest in being able to show that we respected your right of withdrawal and what happened to each purchase (Art. 6(1)(f)); for the record of billing operations, which names who asked for each, also our legitimate interest in keeping accounts and billing secure (Art. 6(1)(f)); and, for showing the payer’s name and each purchase’s buyer to the workspace’s owners and admins, the payer’s billing details to its other owners and a copy of an acknowledgement to the buyer when someone else withdrew, the legitimate interest of those people in managing the workspace’s plan and its purchases (Art. 6(1)(f)).

Emails about your account

We email you the codes for signing up and for recovering your account, and notices that your account was recovered, that your password or your recovery code changed, or that a passkey was added or removed. We also email invitations to team workspaces to the invited address, which may not have an account yet, as described under “Workspace invitations”. In a team workspace, we also email you when one of our apps tells us, as described under “Deleted numbers and email accounts” and “The apps and the workspaces”, that one of the workspace’s WhatsApp numbers or email accounts was deleted, if you are an owner; that its sync was paused or turned off, if you can read it; or, if you are an owner, that nobody can read it any more, or that someone has moved one of the workspace’s numbers into their own personal workspace. We never email you about something you did yourself (an API key’s act counts as its creator’s). Each of these emails names the app, the team workspace, and the number or email account by the name it was given in the app, if it has one, or, for a number without one, by its last 4 digits. The email about a number or email account that nobody can read any more says why, if known; the others name who acted, and that one may too, by their name, if they have one and are still a member and, for an email about a sync paused or turned off, an owner or admin of the team workspace, and the email about a deletion also gives the date until which an owner can still recover it on the app’s screens in the account console. All but the email about a moved number link to the app, and each is written in your account’s language. We also send the emails about purchases and withdrawals described under “Billing”. These emails are sent from an @thehappie.co mailbox hosted by our email provider, GoDaddy.com, LLC, through its outgoing (SMTP) server in the United States; as our processor, it receives the recipient’s address and the content of each email. The transfer relies on the EU–US Data Privacy Framework, under which GoDaddy.com, LLC is certified as part of the certification of GoDaddy Operating Company, LLC, with the European Commission’s standard contractual clauses in GoDaddy’s data processing addendum as a fallback; GoDaddy may use sub-processors of its own. Replies to these emails, and the delivery-failure reports that receiving servers send back, are moved unread to the mailbox’s trash as they arrive, and GoDaddy deletes them after 30 days. Our outgoing queue erases the address and the content as soon as it sends a message, drops it or gives up on it. For 30 days after that, it keeps a keyed hash of the address (and, for codes, one of the address together with the browser that asked), the kind and language of the message, when it was queued and when it was sent or dropped, the number of attempts and, if it could not be delivered, a short failure reason of our own (never the receiving server’s text). It uses these only to avoid sending the same notice twice in a day, to limit how many codes an address receives, to send only the newest code a browser asked for and to stay within our daily sending limit. We send invitations and the notices about numbers and email accounts only while less than half of that limit is used, so that they never hold back a code or a security notice; past our daily limits on those notices, for each app and for each workspace, they wait for a later day, and none is dropped, except one whose recipient, while it waits, stops being a member of the workspace or, for an email to its owners, stops being an owner, and an email about a pause if, while it waits, the app tells us that its number or email account has had its sync turned off, been deleted or deleted for good, or moved out of the team workspace: those are not sent. If someone asks to sign up with an address that already has an account or, while sign-up is limited, with an address that is not on the list, we send that address a short notice, at most once a day. Legal basis: performance of our contract with you (Art. 6(1)(b)), including for the notices about numbers and email accounts described above; for security notices and notices sent to addresses without an account, our legitimate interest in keeping accounts and sign-up secure (Art. 6(1)(f)); and, for invitations, the legitimate interest described under “Workspace invitations” (Art. 6(1)(f)).

Logs and backups of id.thehappie.co and console.thehappie.co

Apart from the security log described under “Your account at the happie co.”, the activity logs of workspaces described under “Workspace invitations”, the billing records described under “Billing”, the records of API keys described under “API keys” and the records of our apps’ settings described under “The apps’ settings in the console”, the servers behind id.thehappie.co and console.thehappie.co keep the logs of our service and of the requests made to these two addresses for at most 15 days (14 days, plus up to a day until each daily file is deleted); an entry for a request your browser makes includes its full IP address, the time, the page it asked for (never what follows “?”), the answer’s status and your browser’s identification string (user agent). To limit repeated attempts, these servers also hold in memory, never on disk, the IP address of each request, which they take into account for a few minutes, and a fingerprint of each email address someone uses to sign up, sign in or recover an account, which they take into account for up to about an hour. A browser that has signed in to an account with its password in the last 30 days is exempt from the hourly limit on wrong passwords for that account’s address, so that someone guessing the password elsewhere cannot lock you out of a browser you already use; for this, our server keeps, in memory only, a fingerprint of that browser’s __Host-id_bind value combined with the address, which is lost whenever the server restarts. These servers, and the encrypted backups of their database, which we keep for up to 90 days, are on Amazon Web Services in the eu-west-1 region (Ireland). Legal basis: our legitimate interest in keeping the service secure and recoverable (Art. 6(1)(f)).

Mailie — who is responsible

The Happie Co OÜ, identified under “Who we are”, is the controller of the personal data processed by Mailie: the website mailie.thehappie.co, the app at app.mailie.thehappie.co, Mailie’s settings in the account console (the console screens that Mailie shows on that address, inside the menu of console.thehappie.co, and, once Mailie sends us its settings, the pages of console.thehappie.co that show them, your account’s page included, described under “The apps’ settings in the console”) and the API at api.mailie.thehappie.co. That includes the data of team mailboxes: we decide how Mailie processes it, and a team’s owners and admins choose, within what Mailie offers, which mailboxes the team connects, whether they sync and who reads them. This policy covers only that hosted service: the open-source, self-hosted edition of Mailie (github.com/thehappieco/mailie) is not operated by The Happie Co, we see none of the data of a self-hosted installation, and whoever runs one is responsible for it. For anything about Mailie and your data, write to hello@thehappie.co.

Mailie — what we process

Your Mailie account: you sign in to Mailie with your account at the happie co., described under “Your account at the happie co.”, and Mailie creates your Mailie account the first time you do. Mailie takes your email address from your account at the happie co. only then: if it changes there later, the change does not reach Mailie. Your name, though, Mailie takes again each time you sign in to it, so a change to your name there reaches Mailie at your next sign-in; if your account has no name when you sign in, because you never gave one or you cleared it, Mailie keeps none, not even the last one it had, and the messages you send go out under the mailbox’s address alone. In a team workspace, Mailie shows your name and the email address of your Mailie account to the team’s owners and admins, in its lists of members and of who has which access, and, while you wait for someone to hand you a team mailbox’s key, to the people who read that mailbox, as it shows you theirs; and the copy of what you send from a team mailbox, where one is saved, carries your name for everyone who reads that mailbox. Your name cannot be edited in Mailie: you change it in your account at the happie co., at id.thehappie.co. For your Mailie account, we store your name, your email address, the link to your account at the happie co. (the address of id.thehappie.co, the identifier of your account there and when the link was made), the public half of your product key, described below, as id.thehappie.co sends it (Mailie records each version of it the first time it sees it, notes when, and never replaces it), your sign-in sessions (a hash of the session token, your browser’s user agent, when the session was created, last used and expires, when you last signed in at id.thehappie.co, as id.thehappie.co reports it when you sign in to Mailie or confirm there that it is you, when the app started such a confirmation, if it has not been completed, and, if the session was ended, when) and, if you turn on sync, allow actions on your messages or allow sending, when you made each of those choices and the version of this policy you agreed to when you made it; your choice on sync covers the mailboxes of your personal workspace only, while your choices on actions and sending cover what you ask in every workspace. When you sign in, Mailie also receives your language and how you signed in to id.thehappie.co, but does not store them; it never stores or logs the single-use access token with which it fetches these details. Your Mailie account has no password or recovery code of its own, and Mailie sends no invitations or reset links: your password, your recovery code and your passkeys are those of your account at the happie co. Your account key is a pair of keys your browser makes for you at your first sign-in, so that data can be encrypted for you: what its public half locks, only its private half unlocks. We store its public half, and its private half only encrypted, in a single copy, under a key that your browser derives from your product key: the key pair that your browser derives for Mailie from the main key of your account at the happie co., as described under “Your account at the happie co.”. Only your browser ever holds the private half of your product key unsealed, so we cannot open that copy; we store it with the version of your product key and when it was stored, tied to a random identifier we keep for your account, not derived from your email address, to the identifier of your account at the happie co. and to the public half of your account key. Your browser sends us that public half and that copy with a single-use ticket, valid for ten minutes, which the app gets at your first sign-in, or at a later one if the first did not get that far; we store that public half and that copy only once and never replace them. For each ticket, we store its hash, your account, the identifier of your account at the happie co., the version of your product key, when you last signed in at id.thehappie.co and how long your session will last. Your account key therefore depends on your account at the happie co.: if you lose your password there, have no passkey that can unlock that account and cannot recover it, the copy we store can no longer be opened, and neither we nor id.thehappie.co can restore it. Mailie has no reset of its own: we can close that Mailie account when you ask, and the way back is a new account at the happie co. and a new Mailie account, as described under “Mailie — how long we keep it”, with the mailboxes of your personal workspace connected again; a team mailbox stays with its team, and the new account must be invited to the team again, given Read again by an owner or admin who reads the mailbox and handed the mailbox’s key by someone who reads it. The mailboxes you connect: the email address (the one you type or, for a Gmail or Microsoft mailbox you connect without typing its address, the one Google or Microsoft reports, when you connect it, for the account you choose on the provider’s page), the name you give the mailbox, if you give it one, the provider (Google, Microsoft, Apple iCloud or another IMAP server), the server settings and login name, the connection status and the log of its changes, and the credentials that let Mailie sign in for you — for Gmail and Microsoft, the OAuth tokens the provider issues; for iCloud, an app-specific password; for other servers, the password. While you connect a Gmail or Microsoft mailbox without typing its address, Mailie keeps, for about twenty minutes, a record of the connection under way: who started it (the internal identifier of your Mailie account), the team workspace, if you are connecting a team mailbox, the provider and when the connection started; until the connection ends, the name you gave the mailbox, if you gave it one, and, for a team mailbox whose sync you turned on, the team’s agreement to sync it (the version of the text you agreed to); and then when you came back from the provider and how and when the connection ended: the mailbox it connected or, if it failed, the reason and, if the provider reported a usable address, that address, only to tell you why it failed. It keeps none of the tokens the provider issues for a connection that fails, though your Google Account or Microsoft account may still list Mailie among the apps with access to it until you revoke that access with the provider, as described under “Mailie — removing a mailbox and revoking access”. Then it deletes that record; copies of it can remain in backups for up to 30 days, as described under “Mailie — how long we keep it”. On that path, Microsoft’s answer, which names the address, also carries an identifier of the account you chose and an identifier of its organisation (for a personal account, the one Microsoft uses for all personal accounts): Mailie uses the organisation’s identifier only to check that the answer was issued by Microsoft for that organisation and that Mailie accepts accounts from that organisation, does not use the account’s identifier, and stores neither, except as they may appear inside the OAuth tokens Microsoft issues, which Mailie keeps encrypted and does not decode. What Google’s answer carries, and what Mailie does with it, is described under “Mailie — Google user data”. In a team workspace, only an owner or admin connects a mailbox, which then belongs to the team, not to whoever connected it, and whoever connects it gets Read, Act and Send on it; Mailie signs in to it on behalf of the team with the credentials given when it was connected or last re-authorised, and keeps using them after whoever gave them leaves the team or closes their account; and Mailie stores who connected it, which decides nothing, is shown only to the team’s owners and admins and is cleared when that person’s Mailie account is deleted. For each team mailbox, Mailie also stores who has which access to it (Read, Act and Send and, for a member who is not an owner or admin, whether they may see and re-authorise the mailbox), who gave it, and when it was first given and last changed; and the team’s agreement to sync it, described under “Mailie — your messages”: who gave it, when, and to which revision of the text that describes sync. Each mailbox you connect also gets a key pair of its own, its mailbox key, so that the mailbox’s data can later be encrypted for you and, for a team mailbox, for each of its readers; the browser of whoever connects the mailbox makes it then. We store its public half, its version number (each new key you create for a mailbox of your personal workspace gets the next number; a team mailbox never gets a new key), a random identifier that stays the same for every version, who made it (the internal identifier of that person’s Mailie account) and when; and each reader’s own copy of its private half, sealed — encrypted in a browser so that only that reader’s account key can open it — with its version, who made that copy and when. Your copy of the key of a mailbox you connect is sealed in your browser; in a team, the copy of a member given Read is sealed in the browser of the owner or admin who gives it, or of someone who reads the mailbox and hands its key to a member waiting for it, and that person is recorded as having made it. When a mailbox is removed, Mailie also stores when, who removed it (the internal identifier of their Mailie account) and when it will be deleted for good, for as long as it stays removed. Mailie also keeps a record of each time a mailbox is removed, recovered or deleted for good, each time the sync of a team mailbox is paused, resumed or turned off, or we turn off the sync of a mailbox of your personal workspace, and, for a team mailbox, each time it is left with nobody able to read it: what was done and when, who did it (the internal identifier of their Mailie account, or a mark that we did it), the mailbox and its workspace, by internal identifiers, who could read the mailbox at that moment, by the internal identifiers of their Mailie accounts, for a team mailbox left with nobody able to read it, why and whose loss caused it, the name given to the mailbox, if it has one and it has no @ in it, and a masked form of its address, with its first character and its domain (such as a…@example.com), never the address itself; how long it keeps this record is described under “Mailie — how long we keep it”. As described under “The apps and the workspaces”, each time a mailbox is removed, recovered or deleted for good, each time one of a team’s owners or admins pauses or turns off the sync of a team mailbox that others read and each time a team mailbox is left with nobody who can read it, Mailie tells us the name given to the mailbox, if it has one, and the masked form of its address described above, never the address itself, and the identifiers of the accounts at the happie co. of whoever did it, of the people who can read the mailbox and, for one left with nobody who can read it, of the person whose loss caused it and why, if Mailie knows; pausing or turning off the sync of the mailboxes of your personal workspace sends us no event, though the report described under “The apps and the workspaces” still shows such a mailbox as paused. Once Mailie also sends us its settings, as described under “The apps’ settings in the console”, it also tells us, by these identifiers, who connected each mailbox, who paused its sync and, for a team mailbox, who gave the team’s agreement to sync it; whether each member is active, suspended, held or disabled in Mailie and has set up their own key; and, for each person, their choices on sync, actions and sending, with the revision of the text each was made under, and the notices Mailie keeps for them, with only the masked form of an address, never the address itself or anything from the messages. While sync is off, Mailie reads the list of folders of each mailbox (names, roles and message counts) each time you ask for it, for example when you open that mailbox in the app; it shows the list to you and does not store it. With sync on, Mailie stores the list of folders and an index of your messages’ metadata, as described under “Mailie — your messages”. While a mailbox’s sync is paused, Mailie keeps the list of folders and the index it already stored, with where the sync of each folder stopped, and takes nothing new into them from the mailbox, other than the result of what you change through Mailie, until sync is resumed; it also stores that the mailbox is paused and since when, which the mailbox’s card shows, and who paused it (for a recovered mailbox, who recovered it), which Mailie shows only to the workspace’s owners and admins (as does the console outside its notices, once Mailie sends us its settings) and clears when that person’s Mailie account is deleted, though our email about a team mailbox’s pause, and the console’s notice of it, may tell its other readers who paused it, as described under “Emails about your account” and “The apps’ settings in the console”. API keys: until Mailie takes the API keys described under “API keys”, it has its own; for each of its own keys you create, we store the prefix that identifies it (the part of the key that is not secret), its name, the access it gives (read, or read and actions), the workspace it belongs to (your personal workspace in Mailie), who created it (the internal identifier of your Mailie account), when it was created, when it expires, when it was last used and, once it is revoked, when and why (for example, that you revoked it, that we disabled your Mailie account or that your account at the happie co. was recovered or disabled), as well as the version of the authorisation text you agreed to when you created it and the mailboxes it reaches (a list you choose when you create the key and can change later), with, for each of them, the access the key has on it (read, or read and actions), who gave it and when it was first given and last changed; the key’s secret is shown only once, when the key is created, and stored only as an Argon2id hash, never in readable form; once Mailie takes the API keys described under “API keys”, it revokes its own and keeps, for each of those keys that names it, what it needs to check the key, which is not its name or its reading key, for as long as described under “Mailie — how long we keep it”. No key reaches a mailbox you connect later unless you add it to the key, and no key reaches a team mailbox, even one you read. Sending: for each message you send, we store the mailbox it was sent from, who asked for it to be sent (the internal identifier of your Mailie account), when the sending was requested and when it ended, its status (sent, failed or outcome unknown), the number of attempts, the reason for a failure, as a category of our own such as “recipient refused” and never as the text the server returned, the message’s Message-ID, the number of recipients, whether the copy in Sent was saved, and two codes that keep the same message from going out twice: the identifier of the request, which the app generates for each message you write, and a cryptographic digest (hash) of the message; we do not store the recipients, the subject, the text or the attachments. This record is shown to you alone, even for a message you send from a team mailbox, and if your Mailie account is deleted, the record of a send from a team mailbox stays until its 30 days are over, without naming you. Data from the mailboxes you connect or read, including Google user data, is also available through the Mailie REST API, which the app itself uses, which is also offered at api.mailie.thehappie.co and which tools such as AI assistants can use with an API key you create. The API returns that data only to requests authenticated as someone allowed to see it, with their session in the app or with an API key. The data of a mailbox of your personal workspace reaches only you and the tools you give a key to, since each key reaches only the mailboxes and the access you chose for it. The messages, folders and log of changes of a team mailbox reach each member given Read by an owner or admin who reads the mailbox, and who holds their own sealed copy of its key, and no tool; its card (its name, address, provider, connection status, sync counts and what the viewer may do with it, nothing from its messages) also reaches the team’s owners and admins and every member given any access to it. The one exception is the keys we use to operate Mailie: we use them to access data from your mailboxes only in the cases listed under “Mailie — what we never do”. Our web server and Mailie keep technical logs (IP address, time, the request made and your browser’s user agent); for each action on your messages, Mailie also logs the mailbox, the folders and the messages involved, by internal identifiers only, never by subject or email address, and who asked for the action: the internal identifier of your Mailie account or the prefix of the API key used. For each message you send, Mailie logs the mailbox, the identifier of the request, the status of the sending and the category of any failure, never email addresses, the subject or the text of the message. When you create a new key for a mailbox, Mailie logs that, by internal identifiers only: the mailbox, who made the key and its version; it never logs mailbox keys or their sealed copies. When a mailbox gets its first key, when someone hands a team mailbox’s key to a member, when a team mailbox is connected with its team’s agreement to sync it or has its sync turned on or off, and when the sync of any mailbox, personal or team, is paused or resumed, Mailie logs that, by internal identifiers only: the mailbox and, where it applies, its workspace, who did it and, for a key handed on, to whom. When a mailbox is removed, recovered or deleted for good, Mailie logs that, by internal identifiers only: the mailbox, its workspace and who did it. Mailie masks email addresses in its own logs and never logs passwords or tokens. If id.thehappie.co sends Mailie a product key for your account other than the one Mailie recorded for that version, Mailie refuses the sign-in or the confirmation and logs that, with the version and, for a confirmation, the internal identifier of your Mailie account. In your browser, the app keeps your session in memory and in an encrypted copy in the browser’s storage; your language and theme, which are your account’s while you are signed in, in the two language and theme cookies described under “What we collect on our websites”, to show them before the app loads; the copies it kept before, in the browser’s local storage and in its own two cookies, mailie_theme and mailie_locale, are read once to carry your choice over, then deleted; and, while you connect a mailbox, which mailbox you are connecting or, for a Gmail or Microsoft mailbox you connect without typing its address, which provider, which team workspace if it is a team mailbox, the Mailie page you started from and the address the provider sends you back to, in that tab’s session storage, each for up to ten minutes from when it is stored there, or until you close the tab if you do not come back to the app in it. While you sign in at id.thehappie.co, or confirm there that it is you, the app keeps in the browser’s IndexedDB storage one-time values that protect that step (such as a state, a nonce, a PKCE verifier and the page to return to, which, from a settings page, may include the identifier of the workspace shown there) and hold nothing else about you; when it asks for your product key, it also keeps there a one-time key pair that lets only this page receive it, whose private half is stored encrypted under a key the page can use but not read. Each set is used only once, is valid for ten minutes and is deleted when it is used or, if it expires unused, at your next sign-in or confirmation; the app also keeps, in that tab’s session storage, a short record of a sign-in or confirmation under way, which holds nothing about you. The app also keeps your account key, in memory and in the browser’s storage (IndexedDB), where it is encrypted under a key that the browser lets the page use but never read, and it never sends these copies anywhere. The app asks id.thehappie.co for your product key only when this browser does not hold your account key — at your first sign-in, in a new browser or on a new device, after you sign out or after the stored key was deleted — and id.thehappie.co then asks you to unlock your account, as described under “Your account at the happie co.”; the app keeps the private half of your product key only in the page’s memory, only until it has made or opened the encrypted copy of your account key with it, erases it right after and never sends it anywhere. The app deletes the copy of your session when you sign out or when an open page of the app finds that your session has ended; if your session ends while no page of the app is open, that copy stays until you next open the app in that browser. Your account key stays in the browser after your session merely expires, so that your next sign-in there does not need your product key; the app deletes it when you sign out, in every tab, when someone else signs in to Mailie in that browser, and when an open page of the app finds that your session was ended before its expiry, for example because you signed out of every session in Mailie’s settings in the account console or we disabled your Mailie account. Closing the tab or the browser does not delete it: a browser that stays closed, asleep or offline until your session would have expired keeps your account key even if the session was ended earlier, and a stored account key has no expiry of its own, so it can stay until you sign out in that browser after a later sign-in, someone else signs in to Mailie there, or you clear the site’s data. The private half of a mailbox key is held only in the page’s memory, while the app makes it, seals it, opens your sealed copy to check it or, in a team, opens your sealed copy to seal a copy of the key for a member you give Read or hand the key to, and is erased right after; the app never stores it in the browser or sends it anywhere unsealed. The app does not use cookies to keep you signed in.

Mailie — your messages

Mailie stores data from the messages of your personal workspace’s mailboxes only if you turn on sync, in Mailie’s settings in the account console, where Mailie first explains what will be stored and asks for your consent. One consent covers every mailbox of your personal workspace, those you have connected and those you connect later, never a team mailbox, and you can withdraw it at any time by turning sync off. In a team workspace, a mailbox belongs to the team, and Mailie stores data from its messages only with the team’s agreement, which any of the team’s owners or admins gives for that mailbox, when connecting it, when resuming its sync or later, in Mailie’s settings in the account console, to the current text that describes sync; Mailie records who gave it, when and to which revision. The team’s agreement is not the consent of the person who gives it: it stays when that person leaves the team or closes their account, your own choice on sync never touches a team mailbox, and the team’s never touches your personal ones. With it, Mailie stores for a team mailbox the same data as for yours, described below, and only the members given Read by an owner or admin who reads the mailbox can search and read it, each with their own sealed copy of the mailbox’s key; the team’s owners and admins do not read a mailbox by their role, a member given Read waits until someone who reads the mailbox hands its key to them, and a member who has never signed in to Mailie cannot be given Read until they sign in, which makes their account key. A team mailbox syncs only while someone can read it: if nobody can any more, for example because its only reader left the team or closed their account, its sync stops and cannot be turned on again or resumed, the team’s owners are told, as described under “Emails about your account”, and what it stored stays, though no member can read it, so that the team’s owners can see the mailbox and decide what to do with it, until an owner or admin, or we, turn its sync off, or until it is deleted for good after an owner removes it. While a team is closed, none of its mailboxes syncs; their index and the team’s agreement are kept, and sync goes on when the team reopens, except for a mailbox whose sync was paused, which stays paused; while it is closed, nobody can pause or resume a mailbox’s sync, and only we can turn a mailbox’s sync off, which deletes its index, or delete a removed one for good, and we do so when one of the team’s owners asks us. Any owner or admin can turn a team mailbox’s sync off, which deletes its index, its list of folders and its log of changes for every reader; its other readers are told in Mailie and by an email from us, as described under “Deleted numbers and email accounts”, and whoever turned it off is not. In a team, Mailie may refuse to connect a mailbox, re-authorise it, give someone access to it or a sealed copy of its key, turn its sync on or off, pause it or resume it, act on its messages, send from it or delete it for good until we have confirmed, within the last hour, that the person doing it, and anyone they give access to, still has their place in the team; reading, removing and recovering are never refused for this. Everything else these Mailie sections say about a mailbox and its messages applies to a team mailbox too, except where they say otherwise. While a mailbox’s sync is off, Mailie stores nothing from its messages, except the short record of each sending described below, and reads only its list of folders and their message counts, plus what it needs to send the messages you ask it to send. With sync on, Mailie keeps an index of the metadata of the messages in the synced folders: for Gmail, the Inbox, Sent, Drafts, Trash, Spam and your labels, but never All Mail, Starred or Important; for Microsoft, iCloud and other servers, the inbox and the other folders that hold messages, such as Sent, Drafts, Trash, Junk, Archive and the folders you create. When sync is turned on, Mailie indexes the messages of the last 90 days in those folders; from then on, it adds the messages that arrive in them and updates the index when messages are read, flagged, moved or deleted in your mailbox. For each message, the index holds: the sender, the recipients (To, Cc and Bcc) and the reply-to address, with their names; the subject; the date it was sent and the date it arrived in your mailbox; its size; its folder and its marks, such as read, starred or answered; the identifiers that link a reply to the original message (Message-ID, In-Reply-To and References); and its structure: for each part and attachment, its type, character set, encoding, size, file name, whether it is an attachment or shown in the message, and its content ID, but not its contents. Mailie builds a search index from the subjects, senders and recipients, and keeps the list of synced folders, with their names, roles, message counts and sync status. It also keeps a log of changes — for example, that a message arrived, with its subject, sender and folder, or that one was moved, deleted or marked as read — which the app of each person who reads the mailbox, and any tool you give an API key to for a mailbox of your personal workspace, use to follow them as they happen. This version of Mailie does not store the text or the attachments of your messages; before it does, we will update this policy, tell you in the app and by email, and ask for your consent again or, for a team mailbox, the team’s agreement again. With sync on, or paused, you can search your messages and read them, but only while your sealed copy of the mailbox’s key, described under “Mailie — what we process”, is stored and, for a team mailbox, while you have Read on it. Search looks only at the index — subjects, senders and recipients — not at the text of your messages. When you open a message, Mailie fetches it from your email provider’s server to show it to you, without storing its text or its attachments and without marking it as read; it fetches an attachment, or the original message, only when you download it, and does not store it either. To change messages in your mailbox, Mailie needs a separate permission, which you give the first time in the app, when it asks you, or in Mailie’s settings in the account console: with it, and only when you ask, in the app or through the API, it marks messages as read or unread, stars or unstars them, archives them, and moves them to another folder or to the trash. The change is made on your email provider’s server, so it also shows in your other email apps, and the index is updated to reflect it. Mailie never changes your messages on its own — opening a message still does not mark it as read — and it never deletes a message permanently; what goes to the trash or to spam is subject to your provider’s rules, and your provider may empty those folders automatically. In Gmail, archiving removes a message from the Inbox; because Mailie does not sync All Mail, an archived message that has no other label leaves Mailie’s index, but it stays in Gmail. You can withdraw this permission at any time, and give it again later, only in Mailie’s settings in the account console; when you withdraw it, your actions stop at once. The permission is yours and covers what you ask in every workspace: on a team mailbox, Mailie acts for you only where an owner or admin has given you Act, and only on a mailbox you read; the change is made on the mailbox’s server, so everyone who reads it sees it; and the team’s other members act under their own permission, which yours does not change. Actions store nothing beyond what sync already stores and the technical logs described under “Mailie — what we process”. You can also connect a tool, such as an AI assistant, to the mailboxes of your personal workspace through the Mailie API, with an API key you create in the account console, in Mailie’s settings until Mailie takes the API keys described under “API keys” and on the console’s API keys page from then on; Mailie takes keys only in your personal workspace, and no key reaches a team mailbox, even one you read. When you create the key, you choose the mailboxes it reaches, the access it gives and how long it lasts (30, 90 or 365 days), and Mailie’s terms for API keys explain in plain words what a tool with it can do (see “Mailie — API key terms” in our Terms of Use); creating the key is your authorisation for that tool, and Mailie treats the requests made with it as yours, within what the key allows. Later, in the account console, you can add one of your mailboxes to the key, take one out, or change whether the key may act on it; a mailbox you connect later is reached only if you add it, and a key left with no mailbox reaches nothing until you add one. An API key needs no sealed copy of a mailbox key. With the key, the tool can search and read the messages of the chosen mailboxes, with their text and attachments: Mailie fetches them from your email provider’s server when the tool asks, without storing them and without marking the messages as read. With a read-and-actions key, and only while you allow actions, the tool can also make the actions described above, on the mailboxes where the key has actions. What the tool does with what it receives is governed by the terms and privacy policy of whoever provides it, not by this policy: an AI assistant such as Claude, for example, sends what it reads to Anthropic. You can revoke a key at any time in the account console, and the tool loses access from its next request once Mailie has the revocation, which, for a key described under “API keys”, we send to Mailie within seconds. To send messages from your mailboxes, or from a team mailbox where an owner or admin has given you Send, Mailie needs another separate permission, yours in every workspace, which you give the first time in the app, when it asks you, or in Mailie’s settings in the account console. With it, Mailie sends a message only when you click Send in the app, and only after 5 seconds during which you can still cancel; closing the page during that time also cancels the sending. Mailie never sends on its own, and no API key sends from your mailboxes: the keys you create cannot send yet, and the keys we use to operate Mailie send only from mailboxes we connected ourselves. The message goes out through your email provider’s outgoing (SMTP) server, with the address of the chosen mailbox and your name, as your account at the happie co. had it when you last signed in to Mailie, as the sender, or the address alone if your account had no name then. While you write, the message is kept only in the memory of the app page, never in the browser’s storage or on the server: Mailie keeps no drafts. When you send, the text and the attachments pass through Mailie’s server only while the message is being sent and are deleted when the sending ends; Mailie keeps no copy of what you send. The copy stays with your provider, in the Sent folder: Gmail and Microsoft save it themselves, and in other mailboxes set up for it, as they are by default, Mailie saves the message there exactly as it was sent, after checking that it is not there yet; in a mailbox set up for Mailie not to save it, there is a copy only if the mailbox’s own server saves one. When you send from a team mailbox, that copy, where there is one, is in the team mailbox, and everyone who reads it sees it, with your name as the sender. With sync on, the sent message enters the index through the Sent folder, like any other. For each sending, Mailie keeps only the short record described under “Mailie — what we process” (from which mailbox, when, its status, its Message-ID and the number of recipients, never the recipients, the subject or the text) and deletes it 30 days after it last changed; the notice that a sending ended, with its outcome, also goes into the log of changes, but only to you: the record and that notice are shown to no one else, not even the other readers of a team mailbox you send from. When you reply to a message, Mailie marks it as answered with your provider only if you have allowed actions and, for a team mailbox’s message, have Act on that mailbox, and replying to or forwarding a team mailbox’s message needs Read on that mailbox; when you forward a message with its attachments, Mailie fetches them from your provider’s server at the time of sending, without storing them. You can withdraw the sending permission at any time, and give it again later, only in Mailie’s settings in the account console; when you withdraw it, a message that Mailie has not yet started handing to your provider is not sent, and your sending stops everywhere, team mailboxes included, while nobody else’s does. A mailbox’s sync can also be paused, in Mailie’s settings in the account console, and resumed later: for a mailbox of your personal workspace, by you, and for a team mailbox, by any of the team’s owners or admins; no other member, and no API key, can pause or resume a mailbox. While a mailbox is paused, Mailie fetches nothing new from it for the index, so the messages that arrive in it and the changes made to it elsewhere are not stored; what is stored stays, and you can still search it and read it, open its messages, act on them and send from it, under your permissions and, for a team mailbox, your Read, Act and Send, and what you change through Mailie shows in the index at once, except that a message moved where the mail server does not say its new place, and the copy in Sent of a message you send, enter the index there only once sync is resumed. When it is resumed, sync catches up from where it stopped: it adds the messages that arrived meanwhile (a folder created meanwhile starts with its last 90 days) and updates the index for what changed or was deleted, without indexing the last 90 days again; a paused mailbox that kept nothing from an earlier sync, such as one removed before its first sync, indexes its last 90 days when it is resumed. Pausing deletes nothing and is not turning sync off: it withdraws neither your consent nor the team’s agreement, while turning sync off, as described in this section, deletes the index and ends any pause, so that when sync is turned on again, Mailie indexes the last 90 days again. Pausing a team mailbox’s sync tells its other readers, in Mailie and by an email from us, as described under “Deleted numbers and email accounts”, and never whoever paused it; a mailbox that is recovered after being removed comes back paused, unless its sync was off, as described there, and its readers are not told of that pause. Turning your sync off stops it for all the mailboxes of your personal workspace and deletes everything it stored for them: the index, the list of folders and the log of changes, including those of the mailboxes you removed that are still kept; it never touches a team mailbox, whose sync its team’s owners and admins turn off, as described above.

Mailie — Google user data

When you connect a Gmail or Google Workspace account, you choose the account on Google’s page and grant Mailie the https://mail.google.com/ permission, together with Google’s sign-in permissions openid and email (https://www.googleapis.com/auth/userinfo.email), with which Google tells Mailie the primary address of the account you chose; when you re-authorise an account already connected, Mailie asks only for https://mail.google.com/. Google’s answer also carries an identifier of the Google Account you chose, its Google Workspace domain, if it has one, and whether the address is verified: Mailie checks that it is, uses neither the identifier nor the domain, and stores none of these (for a connection refused because the address is not verified, Mailie does not keep the address, only a general reason: that Google reported no usable address, as described under “Mailie — what we process”). Mailie uses the address Google reports as the mailbox’s address, just like one typed, in the ways described under “Mailie — what we process”: for example, it signs in to the mailbox with that address and shows it to you and, for a team mailbox, on its card, to the team’s owners and admins and to every member given any access to the mailbox, and it uses only a masked form of the address in its own logs, in its record of what was done to the mailbox and in what it tells us. Mailie uses the https://mail.google.com/ permission only to connect to that mailbox over IMAP and SMTP on your behalf or, for a team mailbox, on behalf of the team and of its members who have access to it: to show you its folders and, if sync is turned on, to keep an index of the metadata of that mailbox’s messages, which Mailie uses to keep your folders’ message counts up to date and to report changes as they happen, and which lets you list and search your messages; to open the messages you ask to read; and, if you allow actions on your messages, to make the changes you ask for — marking them as read or unread, starring or unstarring them, archiving them, and moving them to another folder or to the trash — but never to delete them permanently. If you allow sending, it also uses it to send, through Gmail’s SMTP server, the messages you ask it to send, and Gmail keeps their copy in Sent. Mailie encrypts the OAuth tokens Google issues and stores them together with the account’s email address: the one Google reports when the mailbox is connected or, for a mailbox whose address was typed when it was connected, that address. For a team mailbox, these are the tokens Google issued when the mailbox was connected or last re-authorised, and Mailie keeps using them for the team after whoever did that leaves it, until the mailbox is re-authorised or deleted for good, or a revocation of Mailie’s access at Google takes full effect. When the mailbox is removed in Mailie, Mailie stops using them and keeps them, with what sync stored for the mailbox, for 30 days, so that the mailbox can be recovered, then deletes them, or sooner if the mailbox is deleted for good earlier, as described under “Mailie — how long we keep it”; after you revoke Mailie’s access at Google, they stop working, though not always at once, as described under “Mailie — removing a mailbox and revoking access”. After the mailbox is deleted for good, Mailie asks Google to revoke Mailie’s access to the mailbox’s Google Account, unless another mailbox in Mailie that was connected through Google under the same address still holds that access, even one removed and not yet deleted for good (for a gmail.com address, dots, a +tag or googlemail.com in place of gmail.com do not make it another address); a revocation ends Mailie’s access to that account for every mailbox connected to it through Google, though not always at once, as described under “Mailie — removing a mailbox and revoking access”, so a mailbox connected under another address of the same account, such as an alias or an earlier address of the account, must then be re-authorised. While sync is off, it reads the list of folders and their message counts from Gmail each time you ask for it, for example when you open the mailbox in the app, and does not store it. With sync on, it reads from Gmail, and stores, the folders and the message metadata described under “Mailie — your messages”, never the text or the attachments of your messages. While a mailbox’s sync is paused, it keeps what it stored and reads nothing new from Gmail for the index, other than the result of an action you ask for, until sync is resumed. When you open a message, it reads that message from Gmail to show it to you, and an attachment or the original message only when you download it, and does not store them. When you ask for an action, it makes only that change in Gmail. When you send a message, it hands that message to Gmail to be sent; when you forward a message with its attachments, it reads those attachments from Gmail at that moment, without storing them; and when you reply to a message and have allowed actions, it marks that message as answered. Apart from the new access tokens it gets with the stored ones, its request to revoke Mailie’s access after the mailbox is deleted for good and what Google tells it when you connect or re-authorise the mailbox, described above, it asks Google for nothing else. What Mailie reads from Gmail is also available through the Mailie REST API to you and to the tools you give an API key to or, for a team mailbox, to each member given Read on it and to no tool, as described under “Mailie — what we process” and “Mailie — your messages”. A third-party tool receives Google user data only at your direction — through a key you created for it, and only from the mailboxes and with the access you chose — and what it does with that data is governed by the terms of whoever provides it. We do not use Google user data for advertising, we do not sell it, we do not use it to develop, improve or train artificial intelligence or machine learning models, generalized or not, and we do not transfer it to anyone except as needed to provide the features you use, such as showing a team mailbox to the members of its team given Read on it, for security purposes such as investigating abuse, or to comply with the law. If we ever want to use Google user data in a way this policy does not describe, we will tell you and ask for your consent or, for a team mailbox, the team’s agreement, first. Mailie’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.

Mailie — why we process it and our legal basis

We process your account and mailbox data to provide Mailie to you: to sign you in, connect your mailboxes and show them to you, to search and read your messages, including through the tools you connect with an API key, to change them when you ask, to send messages on your instruction, to keep a removed mailbox for 30 days so that it can be recovered, to keep the record of what was done to a mailbox, described under “Mailie — what we process”, in a team, to show a team mailbox to the members given access to it, keep the team’s agreement to sync it and who has which access to it, tell its readers when its sync is paused or turned off, or when it is removed, and refuse an act on it until the person’s place in the team has been confirmed, and to tell the other owners of a mailbox’s workspace when someone removes it. The legal basis is the performance of our contract with you (GDPR Art. 6(1)(b)). Even so, as promised under “Changes”, we change messages for you only after you allow actions, we send messages from your mailboxes only after you allow sending, and a tool receives data from your mailboxes only after you create a key for it, agreeing to Mailie’s terms for API keys, which first explain what a tool with that key will be able to do; if you withdraw the permission for actions or for sending, your actions or sending stop, in every workspace, and if you revoke the key, the tool loses access. We keep the index of the messages of your personal workspace’s mailboxes only until you turn sync off or your Mailie account is closed (and that of a removed mailbox only while it is kept), on the basis of the consent you give when you turn it on (Art. 6(1)(a)); turning sync off withdraws that consent and deletes the index, without affecting what was done before. We keep the index of a team mailbox with the team’s agreement, which is no one’s consent under the GDPR: for the personal data of the team’s members, the basis is the performance of our contract with them (Art. 6(1)(b)), and for that of anyone else, the legitimate interest of the team workspace’s owners, admins and members, and ours, in its members reading the team’s email together in Mailie (Art. 6(1)(f)); you may object to this processing, as described under “Mailie — your rights”. That index is kept until an owner or admin, or we, turn the mailbox’s sync off, or until it is deleted for good; closing your Mailie account does not delete it. Your messages also contain personal data of the people you exchange email with, such as their names and addresses; we process it only to provide Mailie to you or, for a team mailbox, to its team’s members, on the basis of the legitimate interest, yours and ours, in Mailie working for you or, for a team mailbox, the legitimate interest described above (Art. 6(1)(f)). We process technical and security logs, and apply rate limits, to keep Mailie and your data secure and to prevent abuse, on the basis of our legitimate interest in doing so (Art. 6(1)(f)). Where the law requires us to keep or disclose data, the basis is that legal obligation (Art. 6(1)(c)). For users in Brazil, the corresponding bases of the LGPD are the performance of a contract (Art. 7, V), consent (Art. 7, I), legitimate interest (Art. 7, IX) and compliance with a legal obligation (Art. 7, II).

Mailie — what we never do

We do not sell your personal data. Mailie shows no advertising and uses no analytics or tracking, and we never use your mailbox data for advertising. We never use data from your mailboxes, including any data received from Google, Microsoft or Apple, to develop, improve or train artificial intelligence or machine learning models, generalized or not. No one at The Happie Co reads your mailbox data except (a) with the explicit permission of someone who can read that mailbox, for example when they ask us for help with a specific problem in it, (b) when it is necessary for security purposes, such as investigating abuse or a security incident, or (c) when the law requires it.

Mailie — where your data is and who helps us

Mailie runs on Amazon Web Services (AWS) in the European Union, in the eu-west-1 region (Ireland); AWS hosts the servers as our processor, under a data processing agreement. The provider of each mailbox you connect (for example Google, Microsoft or Apple) processes your email under its own terms and privacy policy; Mailie connects to it on your behalf or, for a team mailbox, on behalf of the team and its members, and data moves between that provider and Mailie only when Mailie does something you or, for a team mailbox, one of its team’s owners, admins or members asked for, such as keeping the index of your messages up to date while sync is on. The emails about your mailboxes described under “Deleted numbers and email accounts” go through our email provider, GoDaddy, and its outgoing server in the United States, as described under “Emails about your account”. We do not share your data with anyone else unless you ask us to or the law requires it. In a team workspace, Mailie shows the team’s members what these sections describe: a team mailbox’s data, including what you send from it, to its readers; your name, your email address and what you can do with each team mailbox to the team’s owners and admins; and, while you wait for someone to hand you a team mailbox’s key, your name and email address to its readers. A tool you give an API key to, such as an AI assistant, is not our processor: it receives the data of the mailboxes you chose because you connected it, and whoever provides it handles that data under their own terms, including where it is kept. If another service provider ever needs to process data outside the European Economic Area, we will rely on appropriate safeguards, such as the European Commission’s standard contractual clauses. If you are in Brazil, your data is transferred to and stored in the European Union (Ireland); this international transfer is necessary to perform our contract with you (LGPD Art. 33, IX).

Mailie — how long we keep it

We keep your account data for as long as your Mailie account exists, and the data of each mailbox until it is deleted for good: 30 days after it is removed, or sooner, as described below. Only an owner of the mailbox’s workspace can remove it (in your personal workspace, you), except that, in a team, an admin can also remove a mailbox they connected whose connection was never completed. Once a mailbox is removed, Mailie stops using it and keeps its settings, its credentials, the records of its mailbox key and every sealed copy of it, for a team mailbox who has which access to it and the team’s agreement to sync it, its sending records and everything sync stored for it for 30 days, so that the mailbox can be recovered; then it deletes them from our database for good. A mailbox whose connection was never completed, so that Mailie never stored its credentials, is instead deleted for good as soon as it is removed. Within the 30 days, an owner can recover a removed mailbox or delete it for good, in Mailie’s settings in the account console; a recovered team mailbox comes back with the members who can still read it and stays paused until an owner or admin resumes it, or, if its sync was off (turned off, or never agreed to), stays off until an owner or admin turns it on, and a removed team mailbox that nobody could read once recovered cannot be recovered, and is deleted for good at the end of its 30 days, or sooner if an owner deletes it; if you ask us at hello@thehappie.co to erase a mailbox you removed from your personal workspace, we delete it for good as soon as we confirm that the request comes from you, without waiting for the 30 days; a team’s removed mailbox can be deleted for good sooner by one of its owners, in Mailie’s settings in the account console; and turning sync off during those days, by you for a mailbox of your personal workspace or by one of a team’s owners for its mailbox, still deletes, at once, what sync stored for it. While a removed mailbox is kept, its address cannot be connected again in the same workspace: an owner recovers it, or deletes it for good and connects it again. Creating a new key for a mailbox deletes the sealed copies of its earlier versions, but not their records, which stay until the mailbox is deleted for good. In a team, taking a member’s Read on a mailbox, or the end of their membership, deletes at once their sealed copies of that mailbox’s key and their access to it. The index of your messages and the list of your folders are kept only until you turn sync off, which deletes them for all the mailboxes of your personal workspace, removed ones included, or until the mailbox is deleted for good; those of a team mailbox are kept until an owner or admin, or we, turn its sync off, or until it is deleted for good, even while nobody can read it or its team is closed; those of a paused mailbox are kept too; a message deleted from your mailbox leaves the index once Mailie confirms that it is gone, which, while the mailbox is paused, happens only after sync is resumed. Entries in the log of changes are deleted once they are more than seven days old, except that Mailie always keeps the 10,000 most recent entries, counting those of all its users, so that the app and your tools can pick up where they left off. Turning your sync off deletes the entries of all the mailboxes of your personal workspace at once, turning a team mailbox’s sync off deletes its entries for every reader, and a mailbox’s own entries are deleted, at the latest, when it is deleted for good. Sign-in sessions in Mailie, which you open with your account at the happie co., expire 24 hours after you sign in and are never extended; their records are kept with your Mailie account. The single-use tickets described under “Mailie — what we process” last ten minutes; each is deleted when your browser has sent us the public half and the encrypted copy of your account key, with it or with another ticket, or when your account is disabled, and otherwise within about an hour after it expires. The record of a Gmail or Microsoft connection under way, described under “Mailie — what we process”, is deleted, with the address the provider reported if the connection failed, within a few minutes after twenty minutes have passed since the connection started, or sooner, for example when you sign out everywhere or leave the team it was for. Mailie’s own API keys expire at the end of the period chosen when they are created, not when the session in which you created them ends; their records, even after they expire or are revoked, are also kept with your account, so that, until Mailie takes the API keys described under “API keys”, you can see in Mailie’s settings in the account console which mailboxes each key reaches or, once it has expired or been revoked, still holds, and, for each of them, who gave the access and when it last changed. Taking a mailbox out of one of Mailie’s own keys deletes from our database the record that the key reached it; only the technical logs and, for up to 30 days, the backups described below still show it; a removed mailbox is taken out of every key, including expired and revoked ones, as soon as it is removed, and a recovery does not put it back; and a key left with no mailbox is not revoked for that: it stays valid, reaching no mailbox, until it expires or is revoked, for example when you revoke it, your account at the happie co. is recovered or we disable that account, as described under “The apps and the workspaces” and “API keys”. Once Mailie takes the API keys described under “API keys”, it keeps, of each one that names it, what it needs to check the key, including who created it and who gave each of its permissions (by the identifiers of their accounts), the email accounts and permissions it was given and the revision of Mailie’s terms for API keys its creator agreed to, for at most 30 days after the key expires, is revoked or is dropped from the keys we send Mailie, and only until your Mailie account is deleted, even if we send Mailie the key’s record again; then, until 365 days after the key was created, it keeps only the key’s prefix, its revocation or its suspension in Mailie and the key’s end date, without its hash, reading key, creator or workspace, so that the key never works in Mailie again, even after your account at the happie co. closes or your Mailie account is deleted. The record of each message you send is deleted 30 days after it last changed, and if your Mailie account is deleted first, the record of a send from a team mailbox stays until then, without naming you; the text and the attachments of a message you send stay on the server only while it is being sent. When Mailie refuses the first sign-in of an account at the happie co., for example because its address already belongs to a Mailie account, it may still keep the public half of the product key that id.thehappie.co sent it for that account, with the identifier of that account and when it was received; that key is not linked to any Mailie account, even one with the same address, and we delete it within about 70 minutes. Technical and security logs are kept for 14 days. Each entry of the record of what was done to a mailbox, described under “Mailie — what we process”, is kept for 90 days, even after the mailbox is deleted for good, and then deleted; deleting the mailbox for good removes its name from its entries, and its masked address from those that no notice still needs and from the others once their notices go. You cannot yet close your Mailie account yourself: ask us at any time by writing to hello@thehappie.co. As soon as we confirm that the request comes from you, we disable your Mailie account, which signs it out of every session, revokes Mailie’s own API keys that you created, suspends in Mailie, for as long as each of them lasts, those described under “API keys” that you created, stops the sync of the mailboxes of your personal workspace and deletes every sealed copy of a mailbox key made for you, those of team mailboxes included, which ends your reading of them; we then delete your Mailie account, the mailboxes of your personal workspace, including those removed in the last 30 days, with their credentials, the records of their mailbox keys, their sending records, everything sync stored for them and the record of what was done to them, your sessions, any of Mailie’s own API keys, the link to your account at the happie co. with the public halves of your product key that Mailie recorded, and the encrypted copy of your account key, without undue delay and in any case within one month of your request. The team mailboxes you connected or could read stay with their teams, with their credentials, index, keys and the other readers’ sealed copies, and their sync goes on, or stays paused, while someone else can read them; Mailie forgets that you connected them, made their key, gave the team’s agreement to sync them, paused their sync or recovered them, gave anyone access to them or sealed a copy of their key for anyone (apart from, once Mailie accepts changes to its settings from the console, its record of those changes, for 30 days after it received each one, as described under “The apps’ settings in the console”), though the agreement, the access and the copies you gave others stay; and if you were the only one who could read one, nobody can read it any more, its sync stops, and the team’s owners are told, as described under “Emails about your account”. To cut Mailie off from a team mailbox you connected or re-authorised with your own sign-in, revoke its access with the provider, as described under “Mailie — removing a mailbox and revoking access”. If entries of the record of what was done to a team mailbox name you, as the person who did something to it or as the reader whose loss left nobody able to read it, Mailie still keeps, for those entries alone, the link between them and your account at the happie co. until it has sent those events to us and stopped following your account, and in any case for at most 90 days after the deletion, and then removes that link; you are also taken off, at once, the readers listed in any entry, though an event about a team mailbox’s sync being paused or turned off that Mailie holds back for up to about an hour, to send us together with others like it, still names you among its readers if you were one, and for longer only while we do not take Mailie’s events, never past 90 days. While the closing of your account, or the end of Mailie following it, is being carried out, Mailie keeps the identifier of your account at the happie co. in a queue until each step is done, normally for up to about an hour, or longer if we do not answer. When you ask us to close your account at the happie co., we also close your Mailie account, on the same request and as described above. Closing your account at the happie co. also makes Mailie forget you and delete your personal workspace there and its data within 30 days, as described under “The apps and the workspaces”. A new account at the happie co. is a different account for Mailie, even with the same email address. To start again with the same address, write to hello@thehappie.co from it and ask us to close your old account at the happie co. and your old Mailie account: id.thehappie.co does not create an account with an address that already has one, and Mailie refuses the sign-in of a new account whose address is that of your old Mailie account; while sign-up is limited to a list of addresses, we also add your address to the list again, since closing your old account takes it off. A new account at the happie co. with another address signs in to Mailie as a new Mailie account, and your old Mailie account stays until you ask us to close it. Every 6 hours, Mailie makes an automatic backup of its whole database, which holds everything this policy describes as stored by Mailie. Backups are kept in Amazon S3 in the eu-west-1 region (Ireland), and each one is deleted 30 days after it is made, so data deleted in Mailie, such as a removed mailbox once it is deleted for good, the index removed when you turn sync off or a closed account, can remain in backups for up to 30 days after it is deleted. We open a backup only to restore Mailie after a failure or data loss, or to check that restoring works; this happens inside AWS in the eu-west-1 region, and a copy restored for a check is deleted right after the check. If we copy the database by hand, for example before an update, the copy stays in the eu-west-1 region (Ireland), the credentials in it remain encrypted, and we delete it within 30 days.

Mailie — how we protect it

Mailbox credentials (OAuth tokens and passwords) are encrypted at rest with AES-256-GCM, each with its own data key and bound to its own mailbox. Each data key is in turn encrypted by AWS Key Management Service, in the eu-west-1 region (Ireland), under a key that never leaves that service, so neither the database nor its backups hold anything that can open the credentials: the Mailie server opens one only through the AWS role of the machine it runs on, and AWS records each opening. The index of your messages, when sync is on or paused, is kept in the same database, on the same server and with the same access restrictions as the rest of the database, but it is not encrypted that way. Neither Mailie’s database nor its backups hold anything that can open your account key, or the mailbox keys sealed to it, without the private half of your product key, which Mailie’s server never receives; but the Mailie app and the page at id.thehappie.co are both loaded from our servers, and modified versions of them could read your password as you type it, your product key, your account key or your mailbox keys, and send them elsewhere. Mailie uses your account key only for the sealed copies of the mailbox keys made for you, team mailboxes’ included, and does not yet use mailbox keys to encrypt anything: your messages, their index and your mailboxes’ credentials are protected as described in this section. A mailbox key does not stop Mailie’s server from reading the mailbox, which it does for you, for the tools you give an API key to and, for a team mailbox, for each of its readers, as this policy describes. Mailie’s own API keys are stored only as Argon2id hashes, those described under “API keys” only as the hash described there, and session tokens only as hashes. Every connection — between your browser and Mailie, and between Mailie and your email provider — is encrypted with TLS. The access tokens Mailie receives from id.thehappie.co, product keys, the secrets of API keys, OAuth tokens and the ID tokens with which Google and Microsoft report a mailbox’s address never appear in logs or URLs, and the single-use code with which id.thehappie.co sends you back to the app is kept out of our web server’s logs; signing in, sending us the encrypted copy of your account key and confirming that it is you through id.thehappie.co are rate-limited, and access to the production systems is limited to the people who operate them. Connecting a mailbox, creating a mailbox key, the first one or a new one, and, in a team, giving someone Read with a sealed copy of a mailbox’s key or handing the key to a member who waits for it also require that you last signed in at id.thehappie.co, with your password or a passkey, no more than ten minutes earlier, as id.thehappie.co reports it when you sign in to Mailie or confirm there that it is you; otherwise the app sends you to id.thehappie.co, telling it your email address, to sign in there again. Backups are encrypted on the Mailie server before they leave it, with AES-256-GCM and a new data key from AWS Key Management Service for each backup, and the credentials inside them stay encrypted with their own keys; only The Happie Co can decrypt a backup, and the server itself can only create backups, not read, list or delete them. Amazon S3 also encrypts them at rest. No system is perfectly secure; if a breach affects your data, we will tell you and the authorities as the law requires.

Mailie — removing a mailbox and revoking access

If you are an owner of a mailbox’s workspace, as you are of your personal workspace, you can remove the mailbox at any time in Mailie’s settings in the account console. Mailie then stops using it and keeps it, with its stored credentials, the records of its mailbox key and every sealed copy of it, for a team mailbox who has which access to it and the team’s agreement to sync it, its sending records and everything sync stored for it, for 30 days, so that the mailbox can be recovered; then it deletes all of it for good and, for a Gmail mailbox, asks Google to revoke Mailie’s access, unless another mailbox in Mailie under the same address still holds it, even one removed and still kept, as described under “Mailie — Google user data”; copies can remain in backups for up to 30 days more, as described under “Mailie — how long we keep it”. Within those 30 days, you, or any owner of a team mailbox’s workspace, can recover it, unless it is a team mailbox that nobody could read once recovered, or delete it for good, in Mailie’s settings in the account console, and a mailbox whose connection was never completed is deleted for good as soon as it is removed. The API keys that reached it lose it as soon as it is removed, and a recovery does not give it back to them. While a removed mailbox is kept, its address cannot be connected again in the same workspace: recover it, or delete it for good and then connect it again. We email the other owners of a mailbox’s workspace when someone removes it; in your personal workspace, you are the only owner, so nobody is emailed. Mailie also tells everyone who would have read a removed team mailbox, other than whoever removed it, in its own pages, until they dismiss the notice, for 90 days at most, and a recovery withdraws it. You can also revoke Mailie’s access directly with your provider: for Google, at myaccount.google.com/permissions; for a personal Microsoft account, at account.live.com/consent/Manage, and for a work or school account, in My Apps or through your administrator; for iCloud, by revoking the app-specific password you created for Mailie at account.apple.com; for other servers, by changing the password. For a team mailbox, this can be done only by someone who can sign in with the provider to the account whose access Mailie uses (the mailbox’s own or, for Microsoft, the account of whoever connected or last re-authorised the mailbox, which is the mailbox’s own unless they signed in with another account that has access to it, as for a shared mailbox) or, if that account is an organisation’s, such as a Google Workspace account or a Microsoft work or school account, by that organisation’s administrator, and doing so cuts Mailie off from the mailbox for every reader. After access is revoked, Mailie is cut off from that mailbox, though not always at once: it can keep using a connection it already had open, or one it opens with an access token it still holds, until the provider ends it (Gmail usually ends one opened with OAuth about an hour after it was opened) and, for Google or Microsoft, it may still be able to sign in with the access token it already holds until that token expires (for Google, within about an hour; for a Microsoft work or school account, by default within about an hour and a half; Microsoft publishes no figure for personal accounts); Google does not say how soon a revocation takes full effect, and says that an administrator’s block of an app can take up to 24 hours; and Microsoft does not say how long a connection already open lasts after a revocation. The next time Mailie asks the provider for a new token and the provider refuses it, it shows that the mailbox needs to be re-authorised; what it had already indexed stays until its sync is turned off, by you or, for a team mailbox, by an owner or admin, by an owner once it is removed, or by us, or until the mailbox is deleted for good: 30 days after it is removed, or sooner. You can revoke an API key at any time in the account console: the tool that uses it loses access to your mailboxes from its next request once Mailie has the revocation, which, for a key described under “API keys”, we send to Mailie within seconds, but what it has already received stays with it, under the terms of whoever provides it.

Mailie — your rights

Under the GDPR you may ask us for access to your data, its correction or erasure, the restriction of its processing, or a copy in a portable format, and you may object to processing based on legitimate interests, ours or those of a team’s owners, admins and members. If you are in Brazil, the LGPD (Art. 18) gives you equivalent rights: confirmation that we process your data, access, correction, anonymisation, blocking or deletion, portability, information about who we share it with and, where we rely on your consent, its withdrawal. You can do much of this yourself in Mailie’s settings in the account console — turn sync off, remove mailboxes (a mailbox you remove is kept for 30 days, so that you can recover it, and then deleted for good, unless you delete it for good sooner), sign out of every session; in a team, only its owners and admins turn a team mailbox’s sync off, and only its owners remove it, though an admin can also remove a mailbox they connected whose connection was never completed — and change your name and your password, replace your recovery code and manage your passkeys at id.thehappie.co; for everything else, write to hello@thehappie.co. If you ask us to erase a team mailbox’s data, or object to its processing, including as someone whose email is in it, we tell the team’s owners of your request; if they do not act on it within one month of your request, we turn that mailbox’s sync off, which deletes its index, and its readers are told only by Mailie’s own notice (in Mailie and, once Mailie sends us its notices, in the console), not by an email from us; if it is turned on again, Mailie indexes the last 90 days again. Removing the mailbox stays its owners’ decision. You may also lodge a complaint with the Estonian Data Protection Inspectorate (Andmekaitse Inspektsioon, aki.ee) or, in Brazil, with the ANPD (gov.br/anpd).

Changes

We may update this policy as our products launch. We will revise the date above when we do. If a change affects how Mailie uses data from your mailboxes or Google user data, we will tell you in the app and by email before it takes effect, and we will ask for your consent or, for a team mailbox, the team’s agreement, before using that data in the new way.

© 2026 The Happie Co OÜ · Reg. no. 17226889 · Ahtri tn 12, 15551 Tallinn, Estonia

© 2026 The Happie Co OÜ
Registered in Estonia
Reg. no. 17226889
Ahtri tn 12, 15551 Tallinn, Estonia
WappieMailiePrivacyTerms