Terms of Use
The scope of the Suppliping panel, user responsibilities, and third-party service dependencies.
Last updated: August 31, 20261. Scope of the service
Suppliping is a business tool that helps manage the supplier directory, communication consent, WhatsApp message templates, sending schedules, status webhooks, and reporting records in one panel. This version works with the Meta WhatsApp Cloud API; it is not WhatsApp Web automation.
2. Accounts and authorized use
- The panel may be used only by a user authorized by the business.
- Sign-in credentials, Meta access tokens, and other secrets must not be shared, and multi-factor authentication should be enabled wherever available.
- The user is responsible for the accuracy of supplier records, keeping phone numbers current, and selecting an appropriate audience.
- The service must not be used for unlawful, misleading, harassing, unauthorized messages or messages that violate Meta or WhatsApp policies.
3. Communication consent and messages
A phone number appearing in the supplier directory does not by itself constitute consent to receive recurring WhatsApp messages. Before sending, the user must provide any required notice, complete the appropriate consent process, and act on opt-out requests without delay.
Business-initiated messages are sent only with templates approved by Meta. Meta determines the template category and approval, messaging limits, quality status, and final charges.
4. Third-party services
Message delivery depends on the Meta WhatsApp Business Platform, while deployment, domain, backup, or monitoring functions may depend on the relevant infrastructure providers. Outages, policy changes, account restrictions, or price changes in these services may be outside Suppliping’s control.
Keeping the same number active in the WhatsApp Business mobile app is possible only through a supported Coexistence onboarding flow and when the account is eligible; the panel alone does not guarantee eligibility.
5. Service continuity and limitation of liability
The panel includes queueing, retries, webhook verification, backups, and health checks to support reliable operation. Even so, uninterrupted service, delivery or reading of every message, and any particular commercial result are not guaranteed. Before bulk sending, the user should run a pilot test, monitor reports, and stop the automation if a problem occurs.
6. Data, privacy, and deletion
For information about data processing, see the Privacy Policy; for deletion requests, see the Data Deletion Instructions. The user must also meet applicable notice, consent, retention, and deletion obligations toward its own suppliers.
7. Changes and contact
These terms may be updated when the service or third-party requirements change. Material changes are reflected by the date on this page. You may use the contact channel below for questions.