Acceptable Use Policy

Customer must use SendInbox only for lawful, expected, and relevant business communication through a Customer-owned official WhatsApp Business Account. Customer is responsible for every contact source, audience rule, template, message, agent reply, product offer, and instruction submitted through its workspace.

This Policy supplements Meta’s current WhatsApp Business Messaging Policy, Messaging Guidelines, Commerce Policy where applicable, and other provider rules. The stricter applicable requirement controls.

• Collect and retain evidence of any consent or other lawful permission required for the recipient, purpose, channel, and jurisdiction.
• Identify the business clearly and send content consistent with what the person reasonably expects.
• Use only approved templates when Meta requires them and keep frequency proportionate.
• Provide and honour a clear opt-out. Stop campaigns promptly when consent is withdrawn or a STOP-like reply is received.
• Keep suppression and consent records accurate. Do not re-import or retag a person to defeat an opt-out.

SendInbox stores consent status and evidence, checks eligibility before a campaign is materialized, and checks it again before sending. Those controls assist but do not replace Customer’s legal and policy assessment.

Customer must not:

• use purchased, rented, scraped, harvested, guessed, leaked, or unlawfully shared contact lists;
• send unsolicited bulk messages, deceptive re-engagement, or repeated messages after non-response or opt-out;
• misrepresent the origin, age, scope, or wording of consent evidence;
• combine data to build or augment unauthorized profiles of WhatsApp users; or
• sell, license, or disclose WhatsApp-derived contact or messaging data except to an authorized processor needed for the Customer’s lawful service.

The service must not be used for:

• fraud, impersonation, phishing, malware, credential theft, fake support, pyramid schemes, or deceptive financial offers;
• illegal goods or services, exploitation, trafficking, child sexual abuse material, or content that facilitates serious physical harm;
• harassment, threats, hate, discrimination, doxxing, stalking, or non-consensual intimate content;
• unlawful political manipulation, voter suppression, or targeting prohibited by provider policy or law;
• regulated products, healthcare, gambling, alcohol, weapons, drugs, financial services, or age-restricted goods unless the exact use is lawful and allowed by Meta;
• infringement of privacy, publicity, copyright, trademark, database, or other rights; or
• content intended to evade review, quality systems, template rules, limits, or enforcement.

Customer must not probe, scan, attack, overload, reverse engineer where prohibited, bypass authentication, share credentials, exploit another tenant, automate outside the documented product, or interfere with queues, rate limits, audit logs, billing, or provider controls. Do not connect assets you do not own or administer.

Unofficial QR sessions, WhatsApp Web automation, device farms, SIM farms, rotating sender schemes, account leasing, and attempts to conceal message origin are prohibited. Security research must follow the coordinated process on our Security page.

We do not pre-approve Customer content, but may use limits, consent state, error patterns, provider status, complaints, and security signals to protect the service. We may pause a campaign, restrict a sender, preserve evidence, request proof of permission, suspend a workspace, or terminate access where reasonably necessary.

Urgent or serious violations may be acted on without prior notice. We may report unlawful activity or respond to valid provider and authority requests. Customer remains responsible for Meta enforcement, end-user claims, and remediation. To appeal a SendInbox action, contact support@sendinbox.cowith the workspace, campaign, and relevant consent evidence.

Review the current WhatsApp Business Messaging Policy before each new use case.