Acceptable use policy

How this page relates to the Terms

This policy summarizes and explains section 5 of the Terms of Use, the acceptable use section. If the two texts ever differ, the Terms of Use prevail.

What we are and what we are not

ZapZap API is an unofficial solution: we are not Meta and we do not carry the official WhatsApp API badge. WhatsApp may restrict or block numbers that send unsolicited messages or break its policies, and no tool, ours included, guarantees that a number will never be blocked.

We use warm-up, a human pace and other protection features to lower that risk. Lowering is not eliminating, so our advice is to connect a number whose risk you are willing to take.

What is your responsibility

Whoever uses the platform answers for what is sent and to whom. In practice, that means:

• having a lawful basis to contact each person, usually consent (opt-in), under the applicable data protection law and WhatsApp rules;
• keeping proof of that consent, so you can show it when asked;
• honoring any request to stop receiving messages, through whichever channel it arrives;
• answering for the content of your messages: what is said, whether it is true and whether it is lawful;
• following the WhatsApp and Meta policies, including the Commerce, Business Messaging and Spam policies.

What is prohibited

You may not use ZapZap API to:

• send unsolicited bulk messages (spam) to contacts without valid opt-in. A list that was bought, rented or scraped from the internet is not opt-in;
• send content that is illegal, fraudulent, defamatory, discriminatory, pornographic involving minors, or that infringes third-party rights, which includes scams and phishing;
• engage in activities that violate the WhatsApp and Meta usage policies;
• compromise the security of the platform: reverse engineering, deliberate overload or exploiting vulnerabilities without authorization;
• resell the service as your own product without a signed white-label agreement.

Opt-out requests

Every marketing or prospecting message must give the recipient a simple way to ask to stop receiving messages, and that request must always be honored, through whichever channel it arrives.

Recording the contacts who asked to leave and checking that list before every send is the customer's responsibility. No product feature replaces that care.

What happens when the rule is broken

A breach of this policy allows us to suspend the account, and in a breach considered serious the remaining balance may not be refunded. We may also suspend or close accounts for non-payment after the grace period, by court order or on well-founded suspicion of fraud, as described in section 6 of the Terms.

If you think a measure was applied by mistake, talk to support and explain what happened. Support reviews the case.

How to report abuse

Did you receive an unwanted message sent by someone using ZapZap API, or see a use that breaks this policy? Write to support with as much of this as you can:

• the number that sent the message and the number that received it;
• the approximate date and time;
• a screenshot of the conversation;
• the reason for the report, in a sentence or two.

Good practices that protect your number

There is no guarantee, but these habits lower the chance of trouble:

• warm up the number before sending in volume;
• raise the volume gradually, with no spikes on day one;
• send messages the person expects and understands why they received;
• offer a way to opt out and respect it;
• watch replies and blocks: if many people complain, the problem is the approach, not the tool.