The Service integrates with third-party messaging and communication platforms to enable Customers to manage omnichannel conversations. This section describes how we handle data received from or transmitted to these platforms.
5.1 Meta Platform (Facebook Messenger & Instagram Direct)
When a Customer connects their Facebook Page or Instagram Professional Account to MonkeyMachine, we access data through the Meta Platform APIs (Graph API, Messenger Platform, Instagram Messaging API) in accordance with the Meta Platform Terms and Meta Developer Policies. Specifically:
- We receive and process message content, sender/recipient identifiers (PSIDs, IGSIDs), timestamps, and media attachments solely to deliver the messaging functionality requested by the Customer.
- We do not sell, license, purchase, or sublicense Meta Platform Data to or from any third party, data broker, advertising network, or ad‑related service.
- We do not use Meta Platform Data for advertising, ad targeting, ad ranking, or building advertising profiles.
- We do not use Meta Platform Data to discriminate against or disadvantage any individual or group based on race, ethnicity, color, national origin, religion, age, sex, sexual orientation, gender identity, family status, disability, medical condition, genetic information, or any other characteristic protected by applicable law.
- We do not use Meta Platform Data to determine eligibility for housing, employment, insurance, education, credit, government benefits, or immigration status.
- We do not use Meta Platform Data for surveillance, law enforcement, or national security purposes, or provide tools that facilitate such activities.
- We do not attempt to decode, re‑identify, de‑anonymize, decrypt, reverse‑hash, or reverse‑engineer any Meta Platform Data provided to us in anonymized, aggregated, or hashed form.
- We do not create or supplement user profiles using Meta Platform Data without the valid consent of the applicable End User.
- Meta Platform Data is stored in encrypted databases with logical tenant isolation — one Customer's data is never accessible to another Customer or to MonkeyMachine personnel without a legitimate operational need.
- When a Customer disconnects their Meta integration, or when an End User requests deletion, all associated Meta Platform Data is permanently deleted within 30 days. End Users and Customers may also request immediate deletion via our Data Deletion page.
- We comply with Meta's requirements for annual re‑verification, App Review, and any data deletion callbacks issued by Meta.
5.2 WhatsApp (WhatsApp Business API / Cloud API)
When a Customer connects a WhatsApp Business Account to MonkeyMachine, we access data through the WhatsApp Cloud API hosted by Meta. In addition to the general commitments in Section 5.1 above, the following applies specifically to WhatsApp data:
- We process messages, phone numbers, message templates, delivery receipts, and media files transmitted through the WhatsApp Business API solely for the purpose of enabling the Customer to communicate with their End Users.
- We comply with the WhatsApp Business Policy, WhatsApp Commerce Policy, and the WhatsApp Business Terms of Service.
- Opt‑in requirement: The Customer is solely responsible for obtaining explicit prior consent (opt‑in) from each End User before sending messages via WhatsApp. MonkeyMachine does not initiate WhatsApp communications without the Customer's instruction.
- GDPR roles: For WhatsApp Cloud API, the Customer acts as the Controller, Meta acts as the Processor of Company Personal Data (phone numbers, message content, message metadata), and MonkeyMachine acts as a sub‑processor on behalf of the Customer. Processing is governed by the Meta Global Processor Terms (MGPT).
- VoIP‑only restriction: WhatsApp Calling via Cloud API is limited to VoIP‑to‑VoIP connections. Public Switched Telephone Network (PSTN) connections on any leg of a call are prohibited by Meta and may result in regulatory sanctions.
- Prohibited data: The Customer must not transmit data subject to heightened regulatory requirements (including data governed by HIPAA or equivalent healthcare regulations) through the WhatsApp Cloud API. The Cloud API is not HIPAA‑compliant.
- No full card numbers: The Customer must not send full payment card numbers, CVVs, or other unmasked cardholder data via WhatsApp messages.
- No cross‑client data sharing: Data received from one Customer's WhatsApp Business Account is logically isolated and is never shared with, transferred to, or made accessible to any other Customer.
- Message content and metadata are stored only for the duration specified by the Customer's retention settings and applicable law. Upon disconnection of the integration, all WhatsApp data is permanently deleted within 90 days.
- We do not use WhatsApp data for any purpose other than providing the Service to the Customer.
5.3 Telegram (Bot API)
- We process messages, user identifiers, chat metadata, and media files received through the Telegram Bot API solely to provide the Customer's bot and messaging functionality.
- We comply with the Telegram API Terms of Service.
- We do not store Telegram data beyond the Customer's configured retention period.
5.4 Other Integrations (Email, Web Chat, SMS)
- For each additional channel, we process only the data necessary to deliver and display messages between the Customer and their End Users.
- The same principles apply: data is processed solely for Service delivery, not sold, and deleted upon account termination or valid deletion request.
5.5 General Commitments for All Platform Data
- All platform data is logically isolated per tenant — one Customer's data is never accessible to another Customer.
- Platform API tokens and credentials are encrypted at rest and are never exposed to other Customers or unauthorized personnel.
- We undergo periodic security reviews and maintain technical safeguards to prevent unauthorized access to platform data.
- In the event that a platform revokes or restricts API access, affected Customers will be notified promptly, and any cached data will be handled in accordance with the platform's requirements.
5.6 CRM Systems and Business Automation Platforms
The Platform provides integration with external CRM systems and business automation platforms (hereinafter — "CRM Systems"). Integration is initiated solely by the Customer for the purpose of bidirectional synchronization of client data, appointments, orders, services, and related information.
When a CRM integration is enabled, the Platform may receive and transmit the following categories of personal data:
- Client identification data: name, phone number, email address;
- Appointment and order data: date, time, service type, amount, status;
- Staff data: name, position, schedule (to the extent provided by the CRM system via API);
- Other data as determined by the specific integration settings.
Legal bases for processing:
- Processing on behalf of the controller (Art. 28 GDPR / Art. 6(3) of Federal Law No. 152-FZ) — the Customer, as the data controller in relation to their clients, instructs MonkeyMachine to process data received from the CRM system for the purpose of providing Platform functionality;
- Performance of a contract (Art. 6(1)(b) GDPR / Art. 6(1)(5) of Federal Law No. 152-FZ) — processing is necessary for the performance of the agreement between MonkeyMachine and the Customer.
Customer obligations:
- Ensure legal bases for the transfer of personal data between the CRM system and the Platform, including obtaining data subject consents where required;
- Notify data subjects of the fact that MonkeyMachine processes their data on the Customer's behalf;
- Ensure the accuracy and completeness of transmitted data;
- Maintain their own privacy policy disclosing the CRM integration.
MonkeyMachine commitments:
- Process CRM integration data solely for the purpose of providing the Service and within the scope of the Customer's instructions;
- Not independently determine purposes of processing for data received through CRM integrations;
- Store data for Russian Federation residents on servers located within the Russian Federation in accordance with Art. 18(5) of Federal Law No. 152-FZ;
- Ensure confidentiality of CRM system API keys and authorization tokens;
- Upon deactivation of the integration, cease synchronization; previously received data remains within the Customer's account until deleted by the Customer or upon account termination.
The list of CRM systems with which integration is available is published on the /legal/subprocessors page. Each CRM system is an independent data controller and is responsible for data processing within its own system in accordance with its own privacy policy.