EFFECTIVE 22 AUGUST 2026
Privacy policy
Muenzi helps independent hospitality teams manage enquiries, bookings, guest requests, and daily operations. This policy explains the data the product uses and the controls around it.
Information Muenzi processes
Account details identify the signed-in owner or team member. Property data includes rooms, prices, policies, tasks, operating settings, AI usage totals, and configured provider details. Guest data may include names, phone or WhatsApp identifiers, contact details, stay dates, message content, requests, delivery status, and booking records supplied by the property or an approved guest channel.
Why the data is used
Data is used to operate the workspace, calculate availability and booking totals, manage AI allowances, route guest conversations, deliver requested notifications, provide support, protect the service, and measure whether core product workflows are useful. Product analytics are property-scoped and do not include advertising identifiers or guest message content.
AI and human control
Muenzi may send relevant property knowledge, operational context, and guest enquiries to its configured AI provider to prepare helpful responses or operational suggestions. When a property connects its own AI provider, the relevant prompt content is sent under the property’s provider agreement. Pricing, cancellations, refunds, booking confirmations, and operational completion retain explicit human or policy controls. Customers should not add sensitive information that is unnecessary for a guest’s stay.
Service providers
Hosting, authentication, AI, subscription billing, messaging, and payment providers process only the data needed for their service. Meta may process WhatsApp account identifiers, message content, and delivery events for connected properties. Paynow, DPO or Paystack may process transaction references, amounts, currency and payer details required to complete an authorised payment in supported markets. Muenzi does not store card numbers or mobile-money PINs. Live AI, payment or messaging integrations are activated only when configured by the property operator.
Retention and security
Operational and channel audit records are retained for service delivery, accounting, dispute handling, and security, then deleted or anonymised according to the operator’s retention requirements. Property AI keys and channel access tokens are encrypted at rest and are not returned to the browser after saving. Muenzi also uses tenant-scoped access checks, signed webhooks, restricted secrets, idempotent processing, and encrypted transport. No system can promise absolute security.
Your choices
Property operators can remove a connected AI key or disconnect WhatsApp while retaining the operational audit history needed for service records. They are responsible for responding to guest requests to access, correct, export, or delete personal information. Workspace users can request account or property data support through their organisation’s Muenzi administrator.
Contact and changes
For privacy questions, contact the Muenzi operator identified in your service agreement. Material policy changes will be communicated in the product or through the account contact before they take effect.
This product policy must be reviewed with the operating entity’s legal name, contact details, retention schedule, subprocessors, AI data-handling terms, and applicable jurisdiction before public production release.