Puxh: sender terms of use
Last updated: 22 November 2026
1. Purpose
These terms govern the use of Puxh by the businesses and individuals who send messages (the "senders") to users of the Puxh application (the "recipients").
Puxh is published by 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").
Puxh is an application-to-person messaging service. It is not designed for marketing or for conversations between people.
2. Sender account
- To become a sender, one must first have a Puxh user account, then request the sender role.
- One account may manage several senders, within the limit set in article 8. Each sender has a single manager, who is the account holder.
- Each sender receives its own identifier ("Puxh ID"), distinct from that of its manager's personal account.
- The manager is responsible for all messages sent on behalf of their senders, including through their API keys.
- A manager may create senders for their own clients, and have them verified, through their account's programming interface. They must then be authorised by each client to act on their behalf and provide accurate information and documents for them, and they remain solely responsible to us for those senders, their messages and their balance. A sanction taken against their account applies to every sender they manage.
3. Verification and badges
- Without verification, the sender is displayed under its Puxh ID, together with an alert badge "Unverified sender". It cannot choose a display name.
- Blue badge: the sender has provided its website and confirmed a professional email address on that website's domain name, and the display name matches that domain. Free email services do not qualify for this badge.
- Green badge: the sender has provided its website, proven the identity of the legal or natural person operating it with an official document (trade register extract or articles of association; national ID card or passport), and proven that it controls the domain of that website with a DNS (TXT) record. The display name is the sender name, checked by our team; the name on the document is not shown to recipients.
- Review: requests are examined and decided by our team, which may rely on an analysis by an artificial intelligence (Claude, provided by Anthropic); the artificial intelligence makes no decision. The more the requested name resembles a well-known or sensitive entity (bank, payment institution, operator, public administration, healthcare), the more thorough the review; for such entities, our team may contact the business through its official channels.
- Refusal: we may refuse a name that resembles a brand or an entity that the sender has not shown it represents.
- Re-verification: documents are re-verified upon their expiry. An expired or resold domain, or an expired document, results in the loss of the badge.
- The sender undertakes to provide accurate information and documents. Any forged document results in the account being blocked.
4. Recipient consent
- A sender may only write to recipients who have accepted it:
- by scanning its QR code in the application;
- by giving their Puxh ID on the sender's website or in the sender's application, then approving the request in Puxh;
- by approving an approval request received with the first message.
- The approval request has a fixed format defined by Puxh; the sender cannot add any text to it.
- Until the recipient has approved, the first message is held, then deleted if the request is refused.
- Every
utilityandinfomessage includes a "Stop receiving" button. Withdrawal of consent takes effect immediately. - The sender must not obtain Puxh IDs by improper means (purchase of lists, collection without informing the persons concerned, guessing from names).
5. Permitted and prohibited content
- Message types:
otp: authentication codes, in a fixed format (a text set by Puxh in the template language, a numeric code and its validity period, without a link);utility: transactional and personal messages (payment, order, appointment, account alert);info: general announcements, identical for all recipients.
- Prohibited in all types: marketing, advertising, promotions, as well as any unlawful or misleading content or content intended to impersonate a third party.
- Validated templates: every message is sent from a template validated by Puxh before use. When sending, the sender provides only the values of the variables. Variables are checked (type, length, links); they must not be used to circumvent the template. Only the free-form message described in point 7 is sent without a template.
- Links: in the text of messages, only to the sender's verified domains; an unverified sender may not include any link there. A button link may point to the site of the sender's choice, over HTTPS, and remains subject to review.
- Notifications: by default, notifications do not display the content of the message. Where the sender chooses to display a text ("public text"), that text can be read by the notification services of Google and Apple; it must not contain any personal data. It may cite the template variables, whose values then display in clear: the sender ensures that they do not contain any either.
otpcodes are never displayed in notifications. - Buttons: a
utilityorinfotemplate may carry up to three buttons, validated with it: open an HTTPS link in the browser of the recipient's phone, shown within the app, copy a code, or reply with free text. Puxh sends no automatic reply to the recipient; every message from the sender goes through a validated template, except the free-form message described in point 7. - Free-form message: a reply from the recipient allows the sender to send them a single free-text message, with up to three buttons, within 24 hours, without a template. A sender with the green badge may send such messages to any recipient who has accepted it, without waiting for a reply. Before it is sent, each free-form message is checked by an artificial intelligence (Jev, provided by TypeSafe AI through Vercel AI Gateway), which refuses any advertising, promotion or marketing, any verification or one-time code, and any phishing or scam attempt; the links in its text remain limited to the sender's verified domains.
6. Processing of content by Puxh
- Puxh receives the content of messages at the time of sending, in order to check it against the template and encrypt it end to end for the recipient.
- This content is processed in memory only: it is not stored in plain text, logged or transmitted to any third party, except the text of a free-form message, transmitted solely for its check to the artificial intelligence mentioned in article 5.
- The replies that recipients type are forwarded to the sender by webhook, with the button's identifier, over HTTPS and signed; the sender may request that their content additionally be encrypted for a key it provides. The same webhook tells that a message was dropped on the recipient's devices, that a first one of their devices fetched it, or that an accepted send did not go through; it never tells whether the message was read.
7. Balance and payment
- Puxh operates on a prepaid balance, without a subscription. Each message sent consumes one credit; recipients' replies forwarded by webhook are free of charge.
- Each account receives, once only, upon opening, a free credit of 3,000 messages.
- The balance is topped up by purchasing packs, at prices that decrease with their size, at the rates published on the Pricing page of the Puxh website. Paid top-ups are reserved for verified senders (blue or green badge).
- The balance does not expire.
- The balance is never refunded, whether the account is closed at the sender's initiative, suspended or blocked. A suspension freezes the balance, which becomes usable again if the suspension is lifted.
- Prices are displayed and paid in CFA francs (XOF). Top-ups are paid via Paystack, our payment provider; an equivalent in the currency of the account's country may be shown for information only. If you pay from another currency, your bank converts the amount and may add its own fees.
8. Usage limits
| Unverified | Verified (blue or green badge) | |
|---|---|---|
| Paid top-ups | No: free credit only | Yes |
| Messages per day | 100 messages | No daily limit |
| Senders per account | 3 until all existing senders are verified | Up to 100, in steps of 3 |
| Webhooks | 1 | 5 |
| Sending history in the dashboard | 30 days | 90 days |
| Support | By ticket | By ticket |
9. Account security
- API keys are personal and confidential. The sender keeps them secure, renews them regularly and may restrict their use to IP addresses.
- If a key is lost or stolen, the sender revokes it immediately and notifies us.
- We recommend enabling the Puxh PIN code on the manager's account, in particular if they sign in with a phone number.
10. Sanctions
- Repeated refusals: a sender is blocked when at least 30% of its approval requests are refused, calculated over at least 20 requests.
- Reports: a sender is suspended when at least 0.5% of its recipients report it, calculated over at least 200 recipients.
- Contagion: when two senders of the same account are blocked, the account loses the sender role; all its senders are blocked and it can no longer create any. This block may extend to accounts linked by the same identifiers (number, device, domain, documents). The account retains the ability to receive messages.
- Emergency: in the event of manifest abuse or compromise, we may suspend a sender, revoke its API keys and remove abusive messages from inboxes, without notice.
- For a verified sender representing a well-known or sensitive entity, a member of our team examines the situation before any permanent block.
- Challenge: the sender may challenge a verification refusal, a suspension or a block from the sender space, within 30 days of the decision.
11. Availability and liability
- We use our best efforts to ensure the availability of the service, without any guarantee of delivery within a given time.
- Puxh transmits messages; the sender is solely responsible for their content.
12. Subprocessors
The service relies in particular on OVHcloud (hosting of the servers, database and files in the European Union), Google (notifications, verification of the integrity of the application, crash reports), Apple (iOS notifications, verification of the integrity of the application), Anthropic (review of sender applications and templates; never the messages sent), Vercel and TypeSafe AI (check of free-form messages), Paystack (payment of top-ups), Meta (sign-in codes through WhatsApp) and Wassoya (sign-in codes by email and WhatsApp, emails to managers).
13. Amendment, termination, governing law
- We may amend these terms; senders are notified before significant changes take effect.
- The sender may close its account at any time; article 7.5 applies to the balance.
- Governing law: Ivorian law.
- Contact: support ticket from the sender space.
Puxh