oowl.in

Terms and Conditions

Last updated: June 13, 2026

1. Agreement to Terms

By accessing or using the oowl.inBot Console (the "Service"), you agree to be bound by these Terms and Conditions. If you do not agree to these terms, you are prohibited from utilizing the Service. These terms apply to all administrators, corporate organizations, and team members who access this console.

2. Service Account Registration & Verification

To activate your organization routing profile, you must:

  • Register an administrative account using a valid WhatsApp Business Admin phone number.
  • Complete the OTP (One-Time Password) number verification step.
  • Provide accurate, complete, and updated information regarding your business entity.
  • Maintain the confidentiality of your admin login passwords and restrict unauthorized console access.

3. Mandatory Employee Consent

Crucial requirement for directory uploads:

You certify and guarantee that all employees and agents registered in your console directory have given explicit, active consent to have their WhatsApp numbers configured for routing and to receive automated messaging assignments. oowl.in disclaims all responsibility for directory uploads made without proper employee consent.

4. WhatsApp Policy and Acceptable Use

You must comply with Meta's WhatsApp Business Policy, developer standards, and regional telecommunications spam laws. You agree not to use oowl.in to:

  • Transmit unsolicited promotional or spam messages to consumers.
  • Configure numbers of users who have requested opt-outs.
  • Bypass or attempt to exploit message routing constraints.

5. Termination & Data Deletion

We reserve the right to suspend or terminate your account if any Terms are breached. You may terminate your association with us at any time by requesting deletion of your organization records.

For complete details on request processing, please refer to Section 4 of our Privacy Policy.

6. Limitation of Liability

The Service is provided "as is" and "as available". oowl.in shall not be liable for any indirect, incidental, special, or consequential damages resulting from the use or inability to use the message router simulation, API timeouts, or Meta-side system suspensions.