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:

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:

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:

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.

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:

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

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