1. Purpose
WAManager provides a workspace for managing WhatsApp sessions, conversations, contacts, campaigns, queues, calendars, appointments, integrations, statistics, an API and AI-assisted features.
Use of the service constitutes acceptance of these terms.
2. Account and access
Each user must use access authorised by their organisation and keep their credentials confidential. The organisation is responsible for the accounts it creates, the roles assigned to its members and actions performed using its access.
Any suspected or compromised access should result in the relevant credentials being changed and, where necessary, the associated sessions or keys being disabled.
3. Permitted use
WAManager must be used in accordance with applicable laws, third-party rights and the rules of connected services.
Fraudulent, unlawful, deceptive or malicious use, or use intended to bypass a third-party provider's technical limits, is prohibited.
The organisation remains responsible for content sent, data imported and the lawful basis allowing it to contact recipients.
4. WhatsApp, contacts and campaigns
Messaging and campaign features must be used with recipients who may lawfully be contacted. Opt-out requests, objections and exclusions must be respected.
WAManager provides tools for managing exclusions, quotas, queues and sending rules, but the organisation remains responsible for configuring its campaigns and complying with the terms applicable to its activity and to WhatsApp.
5. Third-party services and integrations
Some features depend on external services such as WhatsApp, Google Calendar, Microsoft 365 / Outlook, Calendly, Cal.com, OpenAI, payment services or email delivery services.
The operation, outages, rules and changes of these services are also controlled by their respective providers.
An integration may stop working if permission is revoked, credentials become invalid or the provider changes its service.
6. Subscription and billing
Paid features are billed according to the offering, number of sessions, billing period and options selected when subscribing.
Applicable amounts are those shown in the interface or on pricing pages at the time of purchase.
Deleting a billed resource or stopping a renewal takes effect according to the rules shown in the relevant billing interface.
7. Availability and maintenance
The service is operated with the aim of remaining available and operational, but uninterrupted availability cannot be guaranteed.
Maintenance, technical incidents, updates or third-party provider outages may temporarily affect certain features.
8. Data and backups
The organisation is responsible for the data it adds to the service and for ensuring that data is lawful. WAManager provides the functions required to store and process that data operationally as part of the service.
Available exports should be used when the organisation wants to keep an independent copy of certain business data.
9. Intellectual property
WAManager, its interface, code, visual identity and documentation remain protected by applicable intellectual property rights. Access to the service does not transfer ownership of the software.
Content and data added by an organisation remain under that organisation's responsibility and control, subject to processing required to operate the service.
10. Suspension and termination of access
Access may be suspended or limited in the event of a security risk, fraud, clearly abusive use, non-payment of a paid feature or a serious breach of these terms.
Closing an account or stopping a service may end associated synchronisations, automations and access.
11. Liability
WAManager provides technical and business tools. Commercial decisions, content sent, targeting rules, configured automations and use of produced results remain the responsibility of the organisation using the service.
Artificial intelligence features may produce imperfect answers; human approval modes should be used when the context requires verification before sending.
12. Changes to these terms
These terms may be updated when the service or its usage framework changes. The version published on this page is the version currently in force.