Fair use policy.

What's OK

• Sending to WhatsApp groups your linked account is already a member of, and where members understand they may receive announcements.
• Sending relevant updates to your own community: events, deadlines, reminders, weekly digests.
• Using link tracking on URLs you control or have permission to track.
• Adding the bot account to internal team chats for coordination.

What's not OK

• Unsolicited bulk messages ("WhatsApp spam") to people who haven't agreed to receive marketing from you.
• Joining groups solely to broadcast, without being a participating member of the community.
• Buying or scraping phone-number / contact lists.
• Sending content that is illegal, harassing, defamatory, fraudulent, or that infringes someone else's rights.
• Sending content that violates WhatsApp's own commerce or messaging policies, e.g. anything in their Business Policy restricted list.
• Distributing malware, phishing links, or pirated content.
• Using the service in ways that get your number banned at a rate that affects other tenants on the same infrastructure.

Built-in rate limits

To protect both you and the WhatsApp account you've linked, we enforce technical limits regardless of plan:

• Send cadence — a typing indicator plus a 1.2–4 second pause before each message, then a 3–8 second gap before the next group, with a 20% chance of an additional 5–20 second "thinking" pause. Designed to mimic human typing patterns and not trip WhatsApp's anti-spam.
• Daily caps — a maximum number of messages any one group may receive per day (ceiling of 10, configurable below that), with an optional weekly cap.
• Per-source cooldown — the same campaign, recurring send, or scheduled message cannot reach the same group twice within 20 hours. Different campaigns are independent, and one-off sends from Compose are not cooldown-limited.
• Per-number rate ceiling — 60 messages per hour and 400 per day for each linked number.

We will not raise the cadence, the daily-cap ceiling or the cooldown org-wide, on any plan or on request — they exist because WhatsApp bans are the #1 reason customers churn.

There are exactly two ways an admin can deliberately go past a limit, and both are recorded:

• The rate ceiling can be exceeded per send: a send that would cross it is held back and shows a warning, and the admin can confirm it anyway. That option exists because an organisation with more groups than the ceiling has a legitimate reason to reach them all at once — but it is an explicit, per-send acknowledgement that you are accepting a higher risk of WhatsApp restricting that number. No plan raises the ceiling; upgrading does not change it.
• An owner/admin can turn off both the daily cap and the cooldown for one individual group they're confident about (e.g. a group their own association owns and controls) from that group's settings. This is per-group and off by default; it never applies org-wide.

Both are entirely at your own risk, and a restriction that follows either one is not automatically refunded — see the refund policy below.

What we do on our side

Because we run on an unofficial WhatsApp integration, we treat ban-avoidance as a first-class feature, not an afterthought:

• Human-like send cadence — a randomised 3–8 second gap between groups, plus a 20% chance of an extra 5–20 second pause, with a typing indicator before each message.
• Per-source cooldown & daily caps — enforced by default regardless of plan, so no single group gets hammered by the same recurring send.
• Send circuit breaker — if a run of sends starts failing with ban-indicative errors, we stop that number's fanout immediately instead of pushing through.
• Automatic ban detection & pause — the moment we detect that WhatsApp has restricted a linked number, we pause every send for your account (scheduled, recurring, and campaigns) so nothing keeps firing into a restricted number and makes it worse. We email the account owner right away.

If your number gets restricted

It can still happen: WhatsApp restricts numbers used with any third-party tool at its own discretion, sometimes with no warning. Here's exactly what happens and what you can do:

• We pause your sends automatically and email the account owner. Nothing is deleted: your groups, message history, and campaigns stay intact.
• Connect a different number. Link a new WhatsApp number (ideally a dedicated business number) from Numbers → Connect, then unpause sends. Your groups and campaigns carry over.
• Request a data export. Email us and we'll send your message history, group list, and campaign configs as JSON/CSV so you always keep your own data.
• Request a refund, see below.

Refund policy for restricted numbers

Billing runs through Creem.io (our Merchant of Record).

If WhatsApp restricts or bans your linked number, we refund your most recent month on request. Email [email protected] and tell us which number. You don't have to prove anything — a restriction is the outcome we're insuring you against, and it's the whole reason the limits above exist.

What is not covered: being removed from a WhatsApp group, or having members leave, mute you, or block you. That's an audience reaction, not a platform restriction — your number still works and you can still send. If a group kicks you out, the message wasn't wanted; the fix is fewer and better-targeted sends, not a refund. We're happy to look at your analytics with you and help you tune it.

Three things are handled case by case rather than automatically: repeated restrictions on the same account; restrictions that follow sends where an admin deliberately overrode the rate ceiling (see above); and restrictions involving a group whose cap and cooldown were turned off in its settings. We'd still rather talk it through than say no by default — but that's the point at which "at your own risk" starts to mean something.

A refund never deletes your data; you can still request an export.

Recommended practices

• Use a dedicated business number, not your personal WhatsApp: a restriction then never touches your personal account.
• Warm up new numbers. A brand-new number that immediately blasts dozens of groups is the single biggest ban trigger. Start small and ramp up over days.
• Only message groups you're genuinely part of, where members expect announcements.
• Vary your message content: identical text sent to many groups in a short window is a classic spam signal. Our spin-tax feature helps.
• Leave the rate limits alone. They exist to protect your number.

Enforcement

Reports of abuse, repeated bans of your linked numbers, or evidence of the prohibited activity above can lead to immediate account suspension without refund. We'd rather pause one bad actor than have an entire customer cohort get rate-limited by Meta.

Reporting abuse

If you've received unwanted messages from a PromotionBot user, email [email protected] with the sender's number and a screenshot. We respond within 48 hours.

Questions

Edge cases? Honestly unsure if your use case is OK? Email [email protected] before launching. We'd rather give a quick green light than untangle a ban after the fact.