Puxh: privacy policy
Last updated: 22 November 2026
1. Who is responsible for your data
EMIRIS CONSULTING GROUP SARLU, with its registered office at Abidjan Cocody Riviera Allabra, après le Grand Portail de la Cité Allabra ; 11 BP 153 Abidjan 11, a company registered in Côte d’Ivoire with the RCCM under number CI-ABJ-03-2022-B13-09382 ("we"), is the controller of the data described here.
This policy applies to the Puxh application (phone and computer), the Puxh website, the sender space and the API used by senders.
2. What we cannot read
Messages are encrypted end to end with a key specific to each of your devices, created on the device and never leaving it. Once stored, neither we nor our providers can read them.
Our server sees the content of a message only when the sender sends it, to check and encrypt it. This content is processed in memory, without being stored in clear or logged. Only the text of a free-form message, which a sender writes without a template, is passed before sending to an automated review service (see section 5), without your identity.
3. Data we process
Users
| Data | Why |
|---|---|
| Sign-in identifier (email address or WhatsApp phone number) | Create and secure your account |
| Name you enter when signing up | Present you in the application and form your Puxh ID |
| Puxh ID, made of the beginning of your name and randomly drawn characters | Identify you to senders without revealing your contact details |
| Devices: public key, device name and type, date added | Encrypt messages for each of your devices, let you manage them |
| Sign-in sessions: IP address, device or browser type, date | Secure your account, limit abusive attempts |
| Notification tokens (Firebase Cloud Messaging, Apple) | Send you notifications |
| Integrity attestation of the application and the device (Google Play Integrity, Apple App Attest) | Check that requests come from the Puxh application, fight fraud and abuse |
| Approvals given to senders, refusals, reports | Respect your choices, fight spam |
| Replies you write with the "reply" button of a message | Pass them on to the sender concerned |
| PIN code, as a fingerprint (HMAC) only | Protect the addition of devices |
| Sign-in email address, if you have linked one, and date your identifiers were linked | Alert you and reset your PIN (with your WhatsApp number if linked) |
| Messages, encrypted | Deliver them to you; we cannot read them |
| Message metadata: sender, date, size, number of devices, delivery receipt | Route messages, tell the sender they were delivered, apply limits and sanctions |
| Reason for deleting the account, if you write one, kept without your identifier or Puxh ID, with the month of deletion | Internal statistics, improve the service |
| Application crash reports (Firebase Crashlytics): device model and system, application version, place of the crash in the code, installation identifier; never your messages, the text of an error or your account identifier | Fix crashes; you can turn them off in the application settings |
Senders
| Data | Why |
|---|---|
| Identity of the manager and associated user account | Manage the sender account |
| Manager's name, company name and country entered at sign-up, declared purpose of use | Greet the manager, prefill the first sender, show the price equivalent in their currency, support them, internal statistics |
| Domain name, business email address, holder type and name on the document, company documents (trade register extract or articles of association) or, for a sole trader, an identity document (national ID card or passport), DNS (TXT) record of the domain | Verify the sender and award badges |
| Message templates submitted for review | Check their compliance before any sending |
| API keys, as a fingerprint only, and allowed IP addresses | Authenticate sends |
| Webhook addresses and the log of their calls | Pass on replies and delivery tracking |
| Sending history (deliveries, statistics, without content) | Sender dashboard, fight abuse |
| Support requests and their exchanges | Answer managers |
| Balance, top-ups and invoicing | Bill the service |
4. Legal bases
We process this data in accordance with Ivorian law no. 2013-450 of 19 June 2013 on the protection of personal data and, for people located in the European Union, with the General Data Protection Regulation (GDPR).
These processings rely on the performance of the contract (providing the service), our legitimate interest (security, fighting spam and fraud, fixing crashes), our legal obligations (accounting, answers to authorities) and your consent where the law requires it.
5. Who receives data
| Provider | Role | Data |
|---|---|---|
| OVHcloud, servers located in the European Union | Servers, database, file storage (logos, supporting documents) | All the data above; messages only encrypted |
| Google (Firebase Cloud Messaging, Firebase App Check, Play Integrity, Firebase Crashlytics) | Notifications, verification of the integrity of the application, crash reports | Notification token; encrypted notification or public text of the notification; application attestation; crash reports |
| Apple | iOS notifications, verification of the integrity of the application (App Attest) | Notification token; encrypted notification or public text of the notification; application attestation |
| Anthropic | Help reviewing senders' verification requests and message templates | Senders' files and templates only, never the messages sent or your data |
| Vercel (AI Gateway) and TypeSafe AI | Review of the free-form message a sender sends you (marketing, one-time code, phishing) | Text of that message only, without your identity or your reply |
| Paystack | Payment of top-ups | Senders' billing data |
| Wassoya | Sending sign-in codes and security alerts by email, and emails to sender managers | Email address, sign-in code, content of the alert; manager's name for the emails addressed to them |
| Meta (WhatsApp Business) and Wassoya | Sending sign-in codes by WhatsApp | Phone number, sign-in code |
Senders receive the replies you write to them with the "reply" button of a message and know whether you accepted or refused their requests. They also learn that one of their messages was placed on your devices, then that a first one of your devices retrieved it, without knowing how many devices you have or whether you read it. They are never told which links you open. Senders you have authorised also receive, with each send, the date your latest device was added and a risk level (none, low or high) drawn from the integrity check of your devices, so they can ask for an extra verification, for example before a banking operation.
Finally, we may disclose data to the authorities when the law requires us to; messages can then only be handed over encrypted.
We do not sell your data and do not use it for advertising.
6. Notifications
Notifications go through Google's and Apple's services. By default, they only say "New message", or "You received an authentication code" for a code. Some announcements show a short public text, with no personal data, readable by these services. Other messages may be shown as a preview: they are decrypted on your phone, and Google and Apple only receive encrypted data. The "Hide previews" setting brings all notifications back to "New message". Protected messages never show a preview, and sign-in codes received in Puxh are never shown in a Puxh notification.
7. Storage location and transfers
Our servers and our backups are hosted by OVHcloud, in the European Union. For users in Côte d'Ivoire, this hosting is a transfer of data outside the country, subject to declaration or authorisation by the ARTCI.
Some providers in section 5 also process data outside the European Union, in particular in the United States, within the limits of the data listed for each of them.
8. Retention periods
| Data | Period |
|---|---|
| Messages | Until you delete them, or until your account is closed |
| Account, devices, approvals | Until the account is closed |
| Sign-in sessions | Until they expire, you sign out or the device is revoked |
| Notification tokens | Until the device signs out; deleted after 270 days without use |
| Delivery receipts | 30 days |
| Senders' sending history | 30 days for unverified senders; 90 days for verified ones |
| Billing data | 10 years, as required by accounting law (OHADA) |
| Crash reports | 90 days at Google (Firebase Crashlytics) |
| Reason for deleting the account | No limit: it is no longer linked to you |
When an account is closed, the data is deleted, except what the law requires us to keep and the reason for deletion, which you write if you wish and which is kept with nothing that identifies you. Do not put personal data in it.
9. Storage on your device
The application keeps on your device the key that decrypts your messages, in its secure storage: Keychain on iOS, Keystore on Android, secure chip (Secure Enclave) on Mac. This storage is essential to the service.
The website and the sender space only use cookies needed for them to work (sign-in session, language, display), with no advertising or audience measurement cookie.
10. Security
End-to-end encryption, one key per device, messages signed by our server, optional PIN code for adding devices, alerts for every new device, encrypted connections, server secrets encrypted with restricted access, encrypted backups.
11. Your rights
You can ask to access your data, to correct it, to delete it and, where the law provides for it, to receive it in a portable format, as well as object to a processing or ask for it to be restricted. You can delete your messages, revoke a device and close your account directly in the application.
To exercise these rights or for any question about your data, write to us at the postal address given in section 1. Sender managers can also use the support of the sender space. We may ask you to prove that the account is yours before answering.
You can also lodge a complaint with the ARTCI (Côte d'Ivoire) or the CNIL (France).
12. Changes
We will let you know in the application before any significant change to this policy. The date of the latest update is shown at the top of the text.
Puxh