Privacy Policy
Last updated: 22 October 2026
In one sentence: keepasa is built so that nobody outside a conversation can read it, including us. Messages, photos, voice notes, files, names and avatars are encrypted on your phone before they leave it, and only the participants' phones hold the keys. No ads, no third-party analytics, and we never sell or share data. The exceptions are chats with businesses, which the business's team reads and which are encrypted on our servers (section 4); Ulises, the assistant you choose to start (section 5); and the mail sent to your receipts address, which our server receives like any mail server before encrypting it for your phones (section 6).
1. Who is responsible
keepasa is a private, invitation-only messaging app. The data controller is Keemetrix Systems, S.L. (Spanish tax ID B01957380), Miguel de Unamuno 30, 03202 Elche (Alicante), Spain. For any privacy question write to privacidad@keepasa.com.
2. What we can never see
All content is end-to-end encrypted with standard algorithms (AES-GCM, X25519 and Ed25519). The server stores and relays encrypted packets it cannot open:
- Text messages, replies, reactions and private notes.
- Photos, albums, videos, files and voice notes, including their thumbnails.
- Your name, your avatar and the details on your introduction card.
- Room names and icons, meetups, polls, lists, shared locations and reminders.
- Call audio and video, which are also end-to-end encrypted.
- Your recovery keys, which are stored encrypted so that only you can open them.
Encryption keys are generated on your phone and never leave it unencrypted. If you lose your phone without having set up recovery, not even we can restore your history.
Chats with businesses are not end-to-end encrypted: see section 4.
3. What the server does store
To make the app work, the server needs some technical data. This is all of it:
- Your identity: a random identifier, your public keys and your alias (the short name people in your circle find you by). We do not ask for a phone number, an e-mail address or access to your contacts.
- Your devices: the name you give them, when they last connected and a hash of the session (never the raw token), so you can see where you are signed in and kick a device out.
- Conversation structure: which identities take part in each chat or room, when each encrypted packet was sent and its size. This is the minimum needed to deliver messages to the right people.
- Invitations, introductions and blocks: who invited whom, pending introductions and whom you have blocked. A refusal is never communicated to the other person; it simply expires.
- Notifications: the identifier Apple or Google assigns to your phone so we can alert you. The notification does not contain the message content.
- Calls: who calls whom and when, so the other phone can ring. Nothing is ever recorded.
- Scheduled and disappearing messages: the encrypted packet with its send or expiry date.
- Chats with businesses: what section 4 describes.
- Ulises: if you use it, what section 5 describes.
- Receipts by email: if you use it, what section 6 describes.
4. Chats with businesses
Some businesses (a school, a clinic, a shop) talk to their customers through keepasa. You always start those conversations yourself, from their poster, their website or their link: in the browser, without an account and without installing anything, or in the keepasa app, under Places. They don't work like your private chats:
- They are not end-to-end encrypted. The business's team reads what you write from its dashboard. We store it encrypted on our servers (AES-256-GCM, with a separate key for each business that is not kept in the database) and it is only decrypted to show it to that business and to you. We tell you so when the conversation opens.
- Who is responsible for your data. The business is the data controller: it uses your data to help you. Keemetrix Systems, S.L. stores and delivers it on the business's behalf, as data processor under the contract the business signs with us, and does not use it for anything else. In every chat, "Privacy" shows the business's legal name and tax ID and whom to write to.
- What is kept. What you write and when, the name you give, if you give one, and whether you have closed the conversation. We don't ask for your phone number or e-mail. Each business sees you under its own identifier: two businesses cannot tell that you are the same person.
- Where you came from. The business sees which poster, website or link you started the conversation from. We also count the visits, the conversations, the ones that continue in the app and the new sign-ups of each poster or link, added up per day and with nothing that identifies you, so it knows which ones work. If you create your keepasa account to talk to a business, we note it on your account, without saying which one, to know (always added up) how many people stay; it is deleted with your account.
- How long it can write to you. Up to three days after your last message, and never if you close the conversation. The business cannot start one; you can write again whenever you like.
- In the browser. So you can come back to the conversation, your browser keeps a random key; we only store its hash. It expires after 30 days unused and you remove it with "Remove from this browser". Your IP address is only used by the server, in memory and for a short time, to stop abuse; it is not stored with the conversation.
- In the app. Places holds your conversations with businesses; "Continue in keepasa" moves the one you started in the browser to the app, with a link that works only once. When they reply we notify you without the text or the business's name, and silently at night: for that we store your time zone. The business doesn't see your account or your alias, only the name you give it.
- How long. The conversation is deleted after 12 months without activity, or earlier if the business deletes it.
- Your rights. To see, correct or delete what you wrote, write to the business (its e-mail is under "Privacy") or to privacidad@keepasa.com and we will pass it on.
5. Ulises, the assistant
Ulises is an assistant you talk to in a keepasa chat. You only use it if you start it yourself, from Profile, and before you start we tell you what it does. Its chat is not like the others: keepasa processes what you write to it in order to answer you.
- What it reads. What you write in its chat and, if you connect them, your Google mail and calendar, when needed for what you ask (telling you what you have today, summarising your mail, drafting a reply, adding an event). Ulises runs as a separate service: the messaging server still cannot read your chats, and Ulises sees none of them except its own.
- Who processes it. Keemetrix Systems, S.L., with Claude, by Anthropic PBC (United States), which receives what is needed for each answer. Anthropic does not use it to train its models and deletes it within 30 days at most, unless it must keep it by law or to investigate misuse. This data leaves the European Union under the European Commission's standard contractual clauses.
- Nothing goes out without you. Ulises does not send emails, invite anyone, answer invitations or delete anything on your behalf unless you approve it with Face ID, using your passkey. What only affects you, such as saving a draft or adding your own event, you confirm with a tap.
- What it stores. Encrypted in the Ulises service: the permission for your Google accounts; the recent conversation (what you wrote and what it answered, to keep the thread), which is cut after a few hours without talking and deleted within 30 days at most; and anything waiting for your approval. It does not store the content of your mail or calendar: it reads it at that moment, and only what Ulises answered you remains, plus the identifier, date and account of that email or event, to get back to it. Unencrypted, only what it needs to work: your language, your time zone, the time of your morning summary if you ask for one and the identifiers of your latest messages, so it never answers you twice. While it is free it has a usage limit, so we record what each answer costs, without its content, and those figures are deleted after 60 days.
- Your Google accounts. They are connected through Google's permission screen, and you can withdraw the permission at any time: from the chat, from Profile or from your Google account.
- Forgetting and leaving. "Forget everything" deletes the conversation, disconnects your Google accounts and deletes anything pending and the time of your summary. "Stop using Ulises", or deleting its chat, deletes everything it has. Only the figures of what each answer cost stay, for the usage limit, until they are deleted after 60 days.
- Limited use of Google data. keepasa'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. It is only used for what you ask Ulises to do: it is not used for advertising, it is not sold, no person reads it unless you ask or security or the law require it, and it is not used to train AI models.
6. Receipts by email
If you turn it on, keepasa gives you an e-mail address just for receipts and bills (for example, ana.k7x9@in.keepasa.com), and whatever arrives there shows up in your "Receipts" chat. This is how it works:
- When it arrives. The mail is received by Amazon SES, the e-mail service of Amazon Web Services, in Paris. It checks whether it comes from who it says, whether it is spam and whether it carries a virus, and leaves it in a private store. Our server picks it up straight away, encrypts it with a new key that only your phones can open and deletes the original from the store. While encrypting it, it holds it in memory, like any mail server, but it never stores it unencrypted. Mail with a virus is thrown away unopened.
- On your phone. Your phone decrypts it, reads it and decides what it is: a receipt from a sender you have approved, a message waiting for you to decide, a suspicious one, or the code to confirm a Gmail forwarding. From then on, the mail and its files stay in your "Receipts" chat, end-to-end encrypted like the rest of your chats, and so does the list of senders you have approved or blocked.
- What the server does see. Your address (the part you choose, which may be your name, and four random letters); when each message arrives, its size and the result of the checks, to decide whether to notify you; and, for senders you block, a hash of their address (not the address), to throw their mail away on arrival. If a message is larger than 15 MB it is not kept: you only get its sender and subject.
- The notification. It is a generic "New in Receipts", without the shop or the subject, and it goes through Expo, Apple and Google like the other notifications (section 9). Mail that arrives unsigned or as spam does not make a sound.
- Reporting. If you report a fake message, we receive the address that sent it, its domain, why it looked fake and its identifier, never its text, and we keep it like other reports (section 12). "Also report to INCIBE" opens your own mail app so that you send it yourself: keepasa sends nothing on your behalf.
- Changing or leaving. If you change your address or delete the "Receipts" chat, the old address stops receiving mail and is never given to anyone else.
7. What we use that data for
Only to provide the service: deliver your messages, notify you about them, connect calls, maintain your circle and protect your account from unauthorised access. The legal basis is the performance of the service you request by using the app (Article 6(1)(b) GDPR). With Ulises, also for what you ask it to do (section 5), and with receipts by email, to receive what is sent to you, set aside what looks suspicious and handle your reports (section 6). We do not build profiles, use third-party analytics, show ads, or sell, rent or share data with anyone.
8. How long we keep it
- Encrypted packets are kept for as long as they exist in the conversation. If you delete a message for everyone, it is removed from the server and from the other phones without a trace. Disappearing messages are deleted automatically as soon as they expire.
- Invitations and introductions expire on their own (24 hours or 7 days depending on the type) and are then deleted.
- If you delete your account from the app, you have 24 hours to change your mind: until then nobody notices anything and you can cancel it from your phone (or from another one, with your recovery key and your PIN). After that, your identity, devices, direct chats, messages and files are removed. Rooms you took part in continue to exist for the others, without your messages. If you tell us why you are leaving, we keep the reason with nothing that identifies you.
- Receipt mail that none of your phones has picked up yet is deleted after 30 days. The original left by Amazon SES is deleted as soon as we pick it up, and after 3 days at most.
- We keep encrypted server backups for 14 days and then destroy them. Deleted data disappears from backups within that period at most.
9. Where the data lives and who helps us
The keepasa server runs on Amazon Web Services in its Paris region (France), and the website and the call server run in a Hetzner Online GmbH data centre in Germany: all within the European Union. Receipt mail is received by Amazon SES, also in Paris (section 6). For notifications we use Expo's push service (650 Industries, United States), which delivers them through Apple (APNs) and Google (Firebase Cloud Messaging); they only receive the device identifier and a generic alert. For calls we use our own media server; audio and video pass through it encrypted and are not stored. For the assistant that helps businesses set up their panel in keepasa business we use Claude, by Anthropic PBC (United States). It receives what the business writes to it, the files it sends and what it reads on its website; never the business's conversations with its customers or the customer data it keeps in the panel. If you use Ulises, Claude also receives what section 5 describes, and Google receives the requests to your mail and calendar that Ulises makes for you. Anthropic does not use it to train its models and deletes it within 30 days at most, unless it must keep it by law or to investigate misuse. This data leaves the European Union under the European Commission's standard contractual clauses. There are no other third parties.
10. Phone permissions
The app asks for each permission only when you need it, and you can revoke it in the system settings: camera and photo library (to send photos), microphone (voice notes and calls), location (only when you choose to share it), notifications, and Face ID, Touch ID or fingerprint (to lock the app; the check is done by your phone and never leaves it). We do not ask for access to your contacts.
11. Your rights
You can access, rectify, delete and export your data, and object to or restrict its processing. Most of this you do in the app itself: change your name or alias, see and remove devices, delete messages and delete the whole account. For anything else, write to privacidad@keepasa.com. If you feel we have not handled your request properly, you can complain to the Spanish Data Protection Agency (aepd.es) or your local supervisory authority.
12. Reports
You can report a person or a message from the app. Since we cannot read anything, you decide what to show us: if you tick "attach the latest messages", the app decrypts on your phone up to ten messages from that person in that chat and sends us only those, together with the reason and your comment. The other person is not notified. We keep the report while we review it and for up to 12 months afterwards in case further action is needed; then we delete it.
13. Children
keepasa is not intended for children under 14. If you believe a child under that age has created an identity without permission, let us know and we will remove it.
14. Changes to this policy
If we change anything relevant, we will announce it in the app before it takes effect and update the date above. The current version is always at keepasa.com/privacy.html.
keepasa · private messaging by invitation · keepasa.com