Türkçe
ProductSolutionsIntegrationsPricingReferencesAboutFAQRequest a demo
Request a demo
Legal
Language:EnglishTürkçe

Otai WhatsApp Integration, Permissions and User Choice

This page explains how Otai uses permissions granted by an authorised business administrator for the WhatsApp Business Platform. Otai accesses only a Customer Business’s own WhatsApp/Meta assets, or assets that the business is expressly authorised to manage. Completing Meta’s Embedded Signup or another official authorisation flow does not transfer ownership of those assets to Otai.

Last updated: 15 October 2026

1. Permissions Otai may request

Otai is operated by Çallıoğlu İnşaat Turizm Sanayi ve Ticaret A.Ş. ("Otai"), a company incorporated in Türkiye.

Otai will request a permission only where the connected business has enabled a feature that needs it.

1.1 whatsapp_business_management

This permission allows Otai to read or manage WhatsApp business assets that the Customer Business owns or has granted Otai access to, including as applicable:

  • WhatsApp Business Account (WABA) identifiers and status;
  • business phone numbers and Phone Number IDs;
  • business profile information;
  • message templates and their status;
  • QR-code/message assets if the Customer uses that feature;
  • webhook subscriptions;
  • permitted account-level analytics displayed to the authorised Customer Business.

Otai uses this permission to complete onboarding, connect the correct business and number, maintain the message integration, manage only the assets/functions selected by the Customer Business, and show relevant operational status.

1.2 whatsapp_business_messaging

This permission allows Otai, for a connected and authorised business number, to:

  • receive and send WhatsApp business messages;
  • upload or retrieve message media where needed for the conversation;
  • obtain/manage permitted business profile or phone-registration information;
  • receive message delivery/status events;
  • support customer- or business-initiated messaging experiences in accordance with WhatsApp rules.

Otai uses it only to deliver the Customer Business’s requested communication and related operational workflow. It is not used to send messages on behalf of an unrelated business.

1.3 business_management

This is a broader Business Manager permission. Otai will request/use it only where Meta’s applicable Embedded Signup, system-user or business-asset connection flow technically requires it. Otai will not use this permission to access or manage unrelated ad accounts, Pages, pixels or other business assets unless a separate Otai feature, explanation and authorisation expressly covers that use.

2. Data received through the integration

2.1 Depending on the enabled function, Otai may receive:

  • Customer Business and WABA identifiers;
  • business phone number, Phone Number ID, profile and template/webhook status;
  • the end user’s telephone number and WhatsApp display/profile name made available by the platform;
  • message content, media, timestamps, conversation identifiers and delivery/read status;
  • integration authorisation status and technical error/audit data.

2.2 Details are provided in the Otai Privacy Policy at https://otai.app/privacy.

3. How Otai limits use of WhatsApp data

3.1 Otai will not:

  1. sell, rent or license WhatsApp Business Solution Data;
  2. access a Customer Business’s assets without its authorisation;
  3. use the data for unrelated advertising audiences or individual profiling;
  4. share it except with the Customer Business, Meta/WhatsApp, authorised service providers acting under contract, or where law requires;
  5. use message content, metadata, or anonymous/aggregate/derived forms of WhatsApp Business Solution Data to create, develop, train or improve shared or general-purpose AI/ML models;
  6. keep access credentials after they are no longer needed for the connected Service.

3.2 An AI subprocessor may process limited message content only to generate the contracted response, classification, translation, summary or workflow for the relevant Customer Business, with provider-model training contractually disabled.

4. Customer Business messaging duties

4.1 Each connected Customer Business is responsible for:

  1. obtaining the person’s telephone number lawfully;
  2. obtaining and keeping evidence of a WhatsApp opt-in that clearly covers the intended message category/call, where required;
  3. identifying itself and not misleading or surprising the recipient;
  4. using approved templates when required and observing the applicable customer-service window;
  5. honouring every opt-out or block request promptly, including requests received outside WhatsApp;
  6. maintaining an up-to-date support contact and a clear route to a human;
  7. complying with WhatsApp/Meta terms, messaging policies and applicable law.

4.2 Otai tools must not be used with purchased, scraped or otherwise unauthorised contact lists.

5. End-user opt-in and opt-out

5.1 Receiving a message through a Customer Business’s WhatsApp number does not mean that a person has opted in to every future message category.

5.2 An end user may:

  1. tell the Customer Business in the chat that they want messages to stop (for example, “STOP”, “DUR” or an equivalent clear statement);
  2. use WhatsApp’s block/report controls;
  3. contact the Customer Business through the contact details in its business profile or privacy notice;
  4. contact Otai support at info@otai.app if the issue concerns Otai’s technical processing.

5.3 Opting out of marketing does not necessarily prevent a Customer Business from sending a strictly necessary service response where law and WhatsApp policy allow it. The Customer Business must maintain appropriate suppression records and honour the user’s choice.

6. Human assistance

6.1 Automation used within the permitted WhatsApp customer-service window must have a prompt, clear and direct escalation path. Depending on the Customer Business’s configuration, this may include transfer to authorised personnel, a telephone number, email, web support form or physical service point.

6.2 For immediate safety, health or emergency assistance, contact the relevant local emergency service or the Customer Business directly. Otai is not an emergency channel.

7. Disconnecting and revoking access

7.1 An authorised Customer Business administrator may revoke Otai’s access by:

  1. using Disconnect WhatsApp in the Otai integration settings, if available;
  2. removing Otai/the app from the relevant Meta Business Integration or business settings;
  3. removing assigned system-user/app access to the relevant WABA and phone number where applicable; and
  4. contacting info@otai.app with the Customer Business name and WABA/Phone Number ID if assistance is needed.

7.2 After a verified disconnect, Otai will stop new processing through the integration and revoke/delete access credentials promptly. Existing Customer Data is returned or deleted according to the Customer agreement, DPA and the procedure in the Privacy Policy. Revoking Otai does not delete data independently retained by Meta/WhatsApp or by the Customer Business; those parties’ procedures apply to their own records.

8. Questions

8.1 Email: info@otai.app Support: https://otai.app/support Data deletion and disconnection: https://otai.app/privacy#data-deletion

8.2 Official WhatsApp rules also apply, including the WhatsApp Business Messaging Policy (https://whatsappbusiness.com/policy/) and the Customer Business’s accepted WhatsApp/Meta terms.