Legal & Compliance
Privacy Policy
How MumuWorks collects, uses, shares, retains, and protects personal data across its AI, automation, and WhatsApp workflows.
Our privacy commitment
Your business data is yours.
Your customer conversations, documents and business knowledge deserve protection. Privacy is a core commitment behind how we build MumuWorks.
A private workspace
Your business has its own workspace. Access controls separate your customer records and documents from other businesses and help protect them from public access.
No AI training use
Your data is for running your AI Employee. Our policy prohibits using it, or sharing it with AI providers, to train general-purpose AI models.
You control team access
Choose who can work in your workspace and what they can access. Permissions help keep customer conversations and business information in the right hands.
Clear about AI processing
AI features send relevant content to service providers to carry out your requests. That processing is subject to provider security and retention terms. Our no-training commitment does not mean zero data retention.
Google Calendar data
Google Calendar is an optional integration. MumuWorks accesses Google Calendar data only after an authorized workspace user chooses to connect an account and grants permission through Google.
- Data accessed: calendar names, identifiers, and access roles so the user can choose calendars; and limited event information such as event identifiers, status, availability times, transparency, and synchronization metadata. MumuWorks does not request or display the titles or descriptions of external events.
- How data is used: to check availability, prevent double-booking, detect scheduling conflicts, and create, update, or remove MumuWorks appointment and travel events in the writable calendar selected by the user.
- Storage and protection: access and refresh tokens and notification tokens are encrypted at rest. MumuWorks stores selected calendar identifiers and labels, MumuWorks-generated event identifiers, and synchronization metadata only as needed to operate and secure the integration. Access is isolated to the authorizing workspace.
- Sharing and training: Google Calendar data is not sold, used for advertising, or used to train general-purpose AI models. It is disclosed only to service providers acting on our behalf when necessary to operate, secure, and support the integration, or when disclosure is legally required.
- Retention and user control: integration records are retained while needed to provide the connected service, protect its integrity, meet legal obligations, or resolve disputes. Users can stop future access by disconnecting calendars in Booking settings or revoke MumuWorks access from their Google Account. They may request deletion of retained account or integration data through Contact & Data Requests, subject to the retention terms in this policy.
MumuWorks’ 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.
Trial expiry and workspace data
Free trials are for first-time customers. Creating another account does not renew trial eligibility. Verify your account email before using AI or sending messages. We may review repeated use of a confirmed business number; contact support for a separate business or an ownership change. A review does not reset trial dates or allowances.
Creating an account and starting the trial require no credit card or payment. The trial lasts for the number of days shown at signup and does not automatically become a paid subscription. Standard features are subject to trial usage allowances, channel availability and any separately disclosed third-party charges.
When a trial or paid subscription expires, live and paid operations stop. Your login and basic company details remain so you can return to your account. Expiry alone does not close your account.
For a workspace that has never paid, operational workspace content is retained for 30 days after trial expiry. For a previously paid workspace, it is retained for 90 days after paid access expires. After the applicable period, that content and its associated files may be permanently deleted. These expiry rules take precedence over general retention wording elsewhere on this page; active paid workspace content is not deleted merely because it is old.
Expiry cleanup preserves login identities, basic company details, all billing invoices, payments and refunds, and all documents associated with those billing records. It also preserves legal acceptance receipts and the minimum audit records needed for accountability. These records are not subject to the 30-day or 90-day content cleanup; legal obligations and verified data requests are handled separately.
At signup we record your agreement to the Terms of Service and acknowledgement of the Privacy Policy, including their versions and content, your account and workspace, signup method, language and acceptance time. This receipt is retained as evidence of the action you took. It is not consent to marketing.
Trial-expiry reminders are required service notices scheduled for workspace owners by email and in-app three days and one day before expiry, and once at expiry. These notices are not disabled by marketing or optional push notification preferences.
Required retention emails notify workspace owners when cleanup is scheduled, with further notices scheduled seven days and one day before the cleanup date. These are service notices, not marketing. We do not continue unsolicited marketing emails after expiry. Marketing consent is optional and is not required to create an account.
1. Scope and role
This Privacy Policy explains how MumuWorks collects, uses, discloses, stores, and protects personal data when you visit mumuworks.com, create an account, connect a messaging channel, upload business materials, submit customer information, or use any MumuWorks AI, automation, knowledge base, WhatsApp, workflow, or support feature.
In many cases, MumuWorks acts as a service provider or processor on behalf of customers that use the platform to manage their own business contacts, leads, customers, conversations, and documents. Those customers control the business purposes for that data and remain responsible for having a lawful basis to collect and use it.
2. Data we collect
Account and business data
- User account information such as name, email address, login credentials, role, and preferred language.
- Business information such as company name, billing details, subscription metadata, support history, and onboarding records.
- Customer information entered by users, including contact details, notes, lead data, quotations, or workflow inputs.
Operational and content data
- WhatsApp conversation data, message metadata, webhook events, phone-number identifiers, and handover status.
- Uploaded documents, knowledge base files, prompts, generated drafts, workflow instructions, and other content submitted for processing.
- Usage analytics, device information, cookies, browser attributes, IP addresses, and application log data.
3. How we use data
MumuWorks may use personal data to operate and improve the service, provision tenant accounts, authenticate users, process AI and automation requests, support customers, monitor security, calculate billing, prevent abuse, investigate incidents, enforce our terms, and comply with legal obligations.
- Service operation, tenant setup, product delivery, feature configuration, and workflow execution.
- AI processing, retrieval, summarization, drafting, and other customer-requested automation tasks.
- Customer support, rollout guidance, incident response, quality assurance, and product improvements.
- Security monitoring, fraud prevention, logging, backup management, and legal compliance.
4. Data sharing and disclosures
We do not sell personal data. We share data only as needed to deliver the service, process customer instructions, protect the platform, collect payment, or meet legal requirements. Depending on the feature used, this may include OpenAI, Meta Platforms, cloud hosting and storage providers, payment providers such as HitPay, and analytics or monitoring providers that we enable for service operation.
We may also disclose data to professional advisers, auditors, or competent authorities when required by law, regulation, court order, or a good-faith belief that disclosure is necessary to protect rights, safety, property, or the integrity of the service.
5. WhatsApp and Meta Platform Data
MumuWorks accesses WhatsApp and Meta platform data only after a customer authorizes the relevant connection and configures the integration for its tenant. WhatsApp messages are processed solely to provide automation, inbox, handover, analytics, and AI features requested by that customer.
- MumuWorks does not sell WhatsApp data.
- Customers remain the owners of their WhatsApp conversation data and business content.
- Data handling is intended to comply with the Meta Platform Terms and WhatsApp Business Terms.
- Customers are responsible for giving notices, obtaining permissions, and configuring lawful use of their connected channels.
6. AI processing
User content may be sent to AI providers in order to generate responses, summaries, embeddings, suggestions, drafts, or workflow outputs. That content can include prompts, knowledge-base excerpts, uploaded materials, customer messages, and other data necessary to execute the requested feature.
- AI-generated responses may contain inaccuracies, omissions, or outdated information.
- Users must verify important information before acting on it.
- Customers remain responsible for final decisions, actions, notices, approvals, and communications.
- AI output should not be treated as legal, medical, financial, or other professional advice.
7. Data retention
Customer content deleted manually normally stays in Trash for 30 days before permanent removal from the live application and managed object storage. An authorized user may permanently delete it sooner. Trash and pending file cleanup continue to occupy storage until removal succeeds.
Where optional cleanup is offered, the workspace owner may independently enable removal of eligible conversation attachments after 12 calendar months and deletion of eligible closed-conversation history after 24 calendar months. Both settings start off. We do not delete active customer history merely because it is old when these settings are off.
Attachment age starts at the message timestamp. Closed-conversation inactivity starts at the later of its recorded closure and last-message timestamps. Records without reliable closure evidence are excluded. Attachment-only cleanup preserves message text and timestamps and shows Attachment removed after permanent removal.
Before enabling either setting, the owner reviews affected records, estimated reclaimable storage and scheduled dates, including already-old records, and explicitly confirms the choice. Cleanup starts only after an initial 30-day waiting period. Eligible content then enters a separate 30-day recovery period before permanent removal. Disabling a setting cancels pending age-based deletion while recovery remains available. Restored content is protected from immediate repeat cleanup.
Open conversations, unresolved work, pinned or protected content, transaction evidence, legal holds and protected file dependencies are excluded. Contacts, leads, products and quotations keep their manual lifecycle. Older closed conversations and completed appointments may appear in history views after 90 days without being deleted or changing appointment status. Ordinary database records are not included in billable file storage during this release.
We retain account, billing, consent, usage, audit, security, operational and support evidence for as long as necessary to provide and protect the service, resolve disputes, enforce agreements or meet legal obligations. Verified deletion requests may follow a separate process. Backup copies expire through the applicable backup-rotation schedule rather than being synchronously removed from every backup; deletion restrictions must be reapplied if a backup is restored.
Expired workspaces follow a separate notice and retention process: never-paid workspaces normally become eligible 30 days after access ends, and previously paid workspaces 90 days after paid access and any applicable grace period end. Cleanup requires the applicable notices and safety checks. Required financial, legal and account evidence may remain. Optional active-workspace cleanup does not shorten that process.
Account verification and trial protection
We verify account email addresses and use security checks to prevent automated registrations and repeated free-trial claims. When enabled, Cloudflare Turnstile processes browser security signals to confirm that a registration is legitimate.
We retain protected matching codes derived from signup network addresses for 30 days, and confirmed business numbers for 365 days after the latest trial-related verification. The security records do not contain the original addresses or numbers. These matching codes remain personal data and access is restricted.
Minimal account-linked trial eligibility and review decisions remain with your account records after operational workspace cleanup. Expired security fingerprints are removed by scheduled cleanup. Shared networks alone do not disqualify a customer. Contact support if a business number has changed ownership or you are setting up a separate business.
8. Security measures
We implement reasonable administrative, technical, and organizational safeguards designed to protect personal data against unauthorized access, loss, misuse, alteration, or disclosure. These safeguards include encryption in transit, access controls, audit logging, and backup processes appropriate to the service.
- Transport encryption for browser and API traffic.
- Role-based access controls and least-privilege administrative practices.
- Application logging and audit trails for operational visibility and investigation support.
- Backup strategies intended to support business continuity and recovery.
9. International transfers
MumuWorks may process or store data in Malaysia, Singapore, the United States, or other jurisdictions where we or our subprocessors operate. By using the service, customers acknowledge that data may be transferred internationally when necessary to deliver hosting, storage, AI, messaging, or support functions.
Where required, we use contractual, technical, or organizational safeguards that are reasonably designed to protect personal data during cross-border processing.
10. User rights and choices
Subject to applicable law and verification requirements, users may request access to personal data, correction of inaccurate records, export of eligible data, deletion of personal data, or closure of their account. Customers may also manage connected systems, cookies, and certain profile details through account controls.
Requests can be submitted through the Contact & Data Requests page or by emailing [email protected]. We may request additional information to confirm identity and authority before fulfilling a request.
11. Cookies, logs, and minors
We use cookies and similar technologies as described in our Cookie Policy. We also collect log and device information to secure the service, maintain sessions, diagnose errors, and understand feature usage. MumuWorks is intended for business use and is not directed to children.
12. Changes and contact information
We may update this Privacy Policy when our products, laws, or operational practices change. Material updates will be posted on this page with a revised effective date. Continued use of the service after changes take effect constitutes acceptance of the updated policy.
- Privacy Officer: [email protected]
- Support: [email protected]
- General: [email protected]
Website conversations
When a business installs our website chat, visitors may send messages without providing contact details. The business receives their messages, attachments and optional contact details in its workspace. Contact details supplied by visitors remain unverified; matching names, email addresses or phone numbers do not automatically join conversations.
A recovery credential is stored on the business website in the visitor's browser to resume the chat on that same website origin for 30 days after visitor activity. Short-lived access credentials stay in the chat frame's memory. “Forget this browser” revokes browser access; it does not delete the business's conversation records. Conversation records follow the business's workspace retention settings and our data request process.
Website chat uses Cloudflare Turnstile to check requests before visitors write, including uploads. Files are held privately and checked by our malware scanner before download or AI processing. Unattached uploads are scheduled for removal after 24 hours; retained and quarantined files count towards workspace storage. Microphone access is requested only when a visitor chooses to record, and recording can be cancelled before sending.