Acceptable Use Policy
What RASSEL must not be used for, to protect you and your customers.
1. Purpose
This policy sets out what must not be done when using RASSEL, a product of SOWLF, to protect your customers, the reputation of your numbers with channel providers, and the platform itself. It forms part of the Terms of Service and applies to every user of a workspace.
2. General principle
You are responsible for everything sent or executed through your workspace, whether by you, your team, automation, AI or the API.
3. You must not use the Service for
- Spam: sending bulk or repeated unsolicited or misleading messages.
- Unsolicited marketing: messaging people who have not given appropriate consent to receive your messages, buying or compiling number lists without a lawful basis, or ignoring opt-out requests.
- Fraud: scams, impersonating an entity, person or brand, or implying a relationship that does not exist.
- Phishing: messages that lure recipients into revealing credentials, cards or sensitive data.
- Malware: distributing or linking to harmful files or software.
- Illegal activity: any content or activity that violates the laws of the Kingdom of Saudi Arabia or of the recipient's country, including prohibited goods and services.
- Harassment: stalking, threats, repeated abuse or privacy violations.
- Hate and abuse: content that incites hatred, violence or discrimination.
- Credential theft: collecting passwords, verification codes or keys by deceptive means.
- Unauthorised access: attempting to access accounts, workspaces or systems you are not authorised for, or exploiting a vulnerability.
- Security bypass: disabling or circumventing security controls, permissions or technical limits.
- API abuse: usage that disrupts the Service or exceeds what is allowed, or sharing API keys outside your organisation.
- Rate-limit or plan circumvention: multiple accounts, numbers or tools used to exceed limits or evade monitoring.
- Provider-policy violations: policies of Meta / WhatsApp (including the business and commerce policies and template quality) and of any channel, AI or payment provider.
- Messaging without appropriate permission: sending to recipients the customer has no lawful basis to contact.
- Security testing without permission: penetration testing or automated scanning of the platform without prior written permission.
- Reselling the Service or sharing accounts between different entities without an agreement.
4. Sending and campaign controls
- Obtain clear consent before messaging and keep evidence of it.
- Provide an easy way to stop messages and honour it immediately.
- Use clear templates and honest content; avoid misleading or falsely urgent content.
- Send at a reasonable pace; if you see a drop in number quality or a rise in blocks, stop the campaign and review the list and content.
5. AI and automation
You are responsible for the replies of automated agents and for automation rules. Do not use them to make material decisions without human review, to impersonate humans in order to deceive recipients, or to process sensitive data without a lawful basis.
6. Consequences of a breach
Where we reasonably suspect a breach we may, depending on severity: warn you, stop a campaign, channel or API key, temporarily suspend the workspace, or terminate the Service. We tell you why where possible and restore service once the breach is remedied where appropriate. We may report unlawful activity to competent authorities. A channel provider (such as Meta) may also restrict your number directly and independently of us.
7. Reporting
To report abuse originating from a workspace on RASSEL: [email protected]. For legal matters: [email protected].