What you agree to when you send from here

1. Acceptable use

An account exists to send messages people are expecting. Everything below follows from that.

• Consent is required, per recipient. A number belongs on your list only if its owner gave you permission to message them on WhatsApp - at signup, at a counter, in a form, in a reply. Permission to e-mail is not permission to message.
• Purchased, scraped and harvested lists are banned. So are lists rented from someone else, numbers lifted out of group chats, and anything generated by enumerating a dialling range.
• Identify yourself in the first message. The recipient should know who is writing within the first line, without having to guess.
• Offer a way out and honour it. Tell people how to stop - one word is enough - and remove anyone who asks, on the same day, before your next campaign.
• No prohibited content. No fraud or impersonation, no phishing, no malware or credential harvesting, no adult content, no gambling or loan pitches to people who did not ask, no medical or financial claims you cannot support, nothing that targets or harasses a person or group, and nothing illegal where you or the recipient are.
• One account, one operator. Do not resell access, share credentials, or run other people's campaigns from your workspace. They can have their own account.
• No probing the service. Do not attempt to reach another tenant's workspace, bypass the pacing floor, script the web console instead of the documented sender, or load-test this server.

2. WhatsApp account safety

Read this part twice. Automating WhatsApp Web is against WhatsApp's terms of service. A number can be rate-limited, restricted or banned outright, and there is no appeal we can file on your behalf. Every rule below exists because breaking it is how numbers die.

• Warm the number up. A brand-new number that sends two hundred first-contact messages on day one is the single most reliable way to get banned. Start in the low tens, spread over days, and let real replies accumulate.
• Never disable the delays. The floor of five seconds between messages, the randomised gaps, the batch pauses and the nightly cap are the safety system. The floor is enforced server side; the rest you should leave alone.
• Watch the reply rate, not the send rate. Messages that get answered protect a number. Messages that get ignored, blocked or reported destroy it. If replies dry up, stop the campaign and fix the list or the message.
• Stop at the first sign of trouble. Delivery failures climbing, WhatsApp Web logging itself out, a "your account is temporarily restricted" notice - stop the run and wait at least twenty-four hours before sending anything else.
• Vary the text. Identical wording to hundreds of recipients reads as bulk to any filter. Use the template variables, and keep more than one template in rotation.
• Do not send at 3 a.m. Send during waking hours in the recipient's own time zone. A message that wakes someone up gets reported, not read.
• Use a number you can afford to lose. Not your personal number, and not the only number your business can be reached on.
• One session at a time. Do not run the sender on two machines against the same WhatsApp account, and do not use the linked phone for other bulk tooling in parallel.
• No unlinking mid-run. Leave the phone online and the browser profile untouched while a campaign is going, or the run will fail partway and the log will show it.

3. Operating practice

Not rules we enforce - habits that separate an account that keeps working from one that does not.

• Dry run first, always. A dry run walks the whole list, renders every message and writes the log without opening a single chat. It costs two minutes and catches the mistakes that cost a number.
• Read the preview, all of it. Including the rejected rows and the reason each was rejected. An unresolved {name} in the preview is an unresolved {name} in someone's chat.
• Clean the list before you upload it. Remove duplicates, remove anyone who has already replied "stop", and check that the phone column really is the phone column.
• Send in batches you can supervise. Be at the machine while a campaign runs. Stop is instant, but only if somebody presses it.
• Keep the delivery log. Download the CSV after each campaign. It is your record of what was sent, to whom, when, and with what outcome - the only thing that settles a dispute later.
• Re-consent stale lists. Permission from eighteen months ago is not permission today. Ask again before you message an old list.
• Test on yourself. Put your own number as the first row. You will catch formatting problems no preview can show you.

4. Your data

• Isolated per account. Your lists, template, settings and delivery log live in your own workspace. No query in this application can return another tenant's rows, and nothing is pooled or aggregated across accounts.
• Deleted means deleted. Remove a list and the file is removed from disk. Ask us to close your account and the workspace goes with it.
• Never sold, never shared. We do not sell, rent or hand your data to anyone, and we do not use your recipients for anything.
• Your WhatsApp session stays with you. In cloud mode the browser runs on your machine, not ours. We never hold your WhatsApp credentials or session - only the queued job and the outcome the sender reports back.
• You are the controller. The people on your list are your contacts, gathered under your consent and your local law. Answering their access, correction and deletion requests is your obligation, not ours.

5. Keys and access

• Your sender key is a password. It authorises the sender program to claim work as you. Keep it out of screenshots, chat messages, shared documents and anything you commit to version control.
• Rotate on suspicion, not on proof. Issue a new key on the account page revokes the old one immediately. There is no downside beyond restarting the sender.
• You own what happens under your credentials. Activity authenticated with your password or your sender key is treated as yours. Tell us if either is compromised.
• Sign out everywhere else if you have signed in on a machine you no longer control. Changing your password does the same thing and ends every other session.

6. What we do not promise

• No guarantee of delivery. WhatsApp decides what arrives. The log records what we observed, which is the honest limit of what any tool in this position can tell you.
• No protection from a ban. Following every rule on this page reduces the risk. It does not remove it, and we cannot restore a restricted number.
• No uptime guarantee. This service is provided as-is. Maintenance, hosting failures and WhatsApp's own changes can interrupt it.
• No legal advice. Consent, marketing and privacy law differ by country. Whether your campaign is lawful where your recipients live is your call, and your liability.

7. Suspension

We suspend accounts that message people who did not consent, that send any of the prohibited content above, that attempt to reach another tenant's data, or that try to defeat the pacing controls. Clear abuse - fraud, phishing, harassment - is removed immediately and without notice. Anything else gets a warning and a chance to fix it first. You can close your own account at any time; ask, and the workspace and its files go with it.

8. Changes

These terms change when WhatsApp's rules change or when we learn something new about what keeps a number alive. The date at the top of this page is the version in force. Continuing to send after a change means you accept it - so when the date moves, read the page again.