Effective date: 06.11.2026
1. Parties, Roles and Term
This Data Processing Agreement ("DPA") governs the processing of Customer personal data through Botmindly on behalf of Businesses. The parties are the Business and the Operator - Oleksandr Shapoval, a ФОП registered in Ukraine as Shapoval Oleksandr Serhiiovych (ФОП Шаповал Олександр Сергійович). Terms are used as defined in the Terms of Service.
The Business is the controller of its Customers' personal data, and the Operator processes it on the Business's behalf. The person who creates a Business accepts this DPA on its behalf (Terms of Service, Section 1.4). A Tenant acts for the Businesses associated with it on the same terms. The Operator processes the data of Cabinet users, Payers and Tenants as controller under the Privacy Policy.
For Meta-connected services, the Meta Client is the Business whose channels are connected through Meta, and the Operator is its service provider. A Tenant or a Payer is not a Meta Client by that role and gets no independent rights to the Business's Customer data. The Operator keeps a list of Meta Clients with their channels and contacts and provides it to Meta on request.
This DPA applies for as long as the Operator processes data for the Business. For Customer personal data it prevails over other Botmindly documents.
2. Subject and Nature of Processing
The Operator receives messages sent to the Business's connected Instagram, Messenger, WhatsApp and Telegram accounts, stores conversations and attachments, shows them to the Business, sends replies through the Platform, prepares AI responses from the Business's instructions and knowledge base, and deletes data on the Business's instructions and at the end of retention periods.
Data subjects: Customers, owners and representatives of connected accounts, Business representatives, and people mentioned in messages, contacts, attachments or the knowledge base.
Data: names, usernames and Platform identifiers, WhatsApp sender phone numbers, message text, time, reactions, button taps, notes, conversation statuses and Customers' requests to stop messaging; attachments, including photos, videos, audio, documents, contacts with phone numbers and locations; the Business's knowledge base and instructions; channel access credentials. Messages and attachments may contain sensitive data that Customers or Businesses provide voluntarily.
Duration: while the relevant Business, channel or record exists, within the retention periods in the Privacy Policy, Section 6. The data AI providers receive is described there, in Section 4.
3. Business Instructions
The Business gives instructions through Cabinet and API features: it connects channels, replies to Customers, configures the bot and knowledge base, and deletes conversations, channels and the Business itself. Additional instructions are sent by e-mail to hi [at] botmindly.com from the account's e-mail address. If an instruction would breach the law or Platform rules, the Operator does not follow it and tells the Business by e-mail.
Without a separate instruction, the Operator performs only the standard operations the service cannot run without: security, backup and restore, maintenance and diagnostics, deletion at the end of retention periods, and compliance with mandatory requirements of law, Meta and Telegram. The Business instructs the Operator to perform them by accepting this DPA.
A Business's data is retrieved, deleted or disclosed to third parties only on that Business's instruction, given by an associated Cabinet user or through its Tenant. The Operator acts on its own only on a Meta or Telegram request passed to the Business, or where the law requires it. Meta Platform Data is processed and transferred only for purposes permitted by the relevant Meta Client.
4. Subprocessors
4.1. List
By accepting this DPA, the Business gives general written authorization to engage the following subprocessors:
| Subprocessor | Function and data | Processing location |
|---|---|---|
| OVHcloud | The Botmindly server: database, conversations, Business, Payer and connection data, logs, encrypted backups | European Union; OVHcloud group companies outside the United States may access the server remotely for support and security |
| Backblaze (DPA, subprocessors) | Attachments, knowledge base photos, encrypted backups | European Union |
| Cloudflare (DPA, subprocessors) | API, website and file traffic; the Cabinet and its accounts; technical logs; e-mail | Cabinet data - EU; Cloudflare network |
| OpenRouter (DPA) | Receiving AI requests and passing them to model providers | United States |
| Model providers on the OpenRouter zero data retention list | Generating responses to AI requests | United States and other countries |
Meta and Telegram run their Platforms on their own terms, and browser push services and Google Fonts are contacted by the Cabinet user's browser; these recipients are not subprocessors (Privacy Policy, Section 5).
4.2. Contractual safeguards
The contract terms of OVHcloud, Cloudflare, Backblaze and OpenRouter require them to process data only on the Operator's instructions, protect it and engage their own subcontractors on the same terms. OpenRouter contractually requires model providers to comply with data protection law.
Botmindly does not use Platform Data, including WhatsApp Business Solution Data and data derived or aggregated from it, to train or improve general-purpose models. WhatsApp Business Solution Data is sent to AI providers only once their contracts meet the WhatsApp Business Solution Terms.
4.3. Changes
The Operator notifies Businesses of a new or replacement subprocessor at least 14 days in advance; within that period the Business may object.
Model providers on the OpenRouter zero data retention list are authorized as a category: OpenRouter selects one of them for each request and may change the list without notifying the Operator. The Business may object to this category or to a specific provider at any time by writing to hi [at] botmindly.com. The Operator reviews the objection within 14 days and excludes the provider from routing if this is possible without harming the service; if not, the Business may turn off AI responses by pausing the bot, or end the contract.
5. International Transfers
Processing locations are listed in Section 4.1. Under Article 29 of the Law of Ukraine "On Personal Data Protection", an adequate level of protection is provided by the states of the European Economic Area, where the server and the file storage are located, and by the states whose capital market regulators have signed the IOSCO Multilateral Memorandum of Understanding, including the United States and Canada.
The Ukrainian basis does not replace the requirements of the country where the Business and its Customers are located. For Businesses in Uzbekistan, storage and processing in the European Union rely on part three of Article 27¹ of the Law of the Republic of Uzbekistan "On Personal Data" (as amended by Law No. ZRU-1125 of 26.03.2026): all member states of the European Union are on the list of states with adequate protection approved by Cabinet of Ministers Resolution No. 415. The United States is on that list only for companies operating under the EU-US Data Privacy Framework.
In international transfers and processing of personal data, each party complies with the requirements of the relevant country's law that apply to it; on request, the Operator gives the Business the transfer details it needs for this. Where Meta Platform Terms requirements for the EEA or the United Kingdom apply to a transfer, the transfer must meet them.
6. Security Measures
The Operator applies technical and organizational measures appropriate to the risk to protect personal data:
- Server data, files, backups, channel access credentials and passwords are stored in protected form.
- Access to data is separated by Business; administrative and diagnostic access is limited to people authorized by the Operator and bound by confidentiality.
- Attachments are opened through time-limited links; anyone with a valid link can open the file until it expires.
- Technical logs are kept with set retention periods; browser notifications are encrypted and contain no conversation text.
- Backups are kept for no longer than 7 days, and restoring from a backup does not bring deleted data back.
- Incidents are handled under Section 9.
Botmindly does not provide end-to-end encryption of conversations.
7. Deletion and Return of Data
The Business deletes a conversation, a channel or the Business itself in the Cabinet or through the API (Data Deletion Instructions). The Operator does not restore deleted data. Until the Business deletes its data, the data is kept, including when the Business stops using the service. The Business exports a copy of its knowledge base to Excel itself and receives a copy of its conversations on request to hi [at] botmindly.com. After the contract ends, the Operator, on the Business's written request, sends it a copy of its data or deletes the data.
After deletion, only the records in the Privacy Policy, Section 6, remain: cost totals, tax records, and Business details with confirmations. Internal numbers of deleted conversations, channels and Businesses, including those deleted at a Customer's or Meta's request, are removed from usage records immediately; after that the records are not linked to a Customer or to Platform activity and contain no Platform Data. Deleted data may remain temporarily in backups and technical logs until their periods expire.
8. Data Subject Requests
The Operator helps the Business respond to Customers' requests for access, correction and deletion: it passes the Business every request it receives about its Customers and, at the Business's request, prepares a copy of a conversation or corrects or deletes an individual message. Within 10 working days the Operator tells the person whether the request will be fulfilled and completes its own part within 30 calendar days; the Business decides on Customer data within the periods of the law that applies to it.
The Operator promptly passes the Business any Meta notice of a person's request concerning Platform Data and acts on the Business's instructions. If a supervisory authority contacts the Business or the Operator about the Business's data, the Operator gives the Business the processing information it holds.
9. Security Incidents
When the Operator becomes aware of a security incident affecting personal data or Platform Data, or of an incident that may compromise the security of its systems or its providers' systems, it:
- takes steps without undue delay to contain the incident and remedy its effects;
- notifies Meta as soon as possible through its incident reporting form if the incident concerns Meta Platform Data or systems processing it, and keeps Meta informed;
- notifies each affected Business by e-mail without undue delay and no later than 24 hours after becoming aware of the incident: what happened, what data is affected, what has been done and what the Business can do; further details follow as they become known;
- gives the Business the information it needs to notify supervisory authorities and affected people;
- notifies Telegram users where Telegram's terms and applicable law require it;
- notifies the supervisory authority and affected people in the cases and within the periods set by law for data the Operator is responsible for;
- records the incident, its investigation and the measures taken.
10. Information and Audits
On request to hi [at] botmindly.com, the Operator provides within 30 days a description of its security measures, its providers' terms and audit reports to the extent the providers allow them to be shared, and other information showing compliance with this DPA.
If this information is not sufficient, the Business may carry out an audit no more than once every 12 months, except after an incident or at a supervisory authority's request. The audit is agreed at least 30 days in advance, is carried out remotely and on documents, and does not cover other Businesses' data or confidential information of the Operator or its providers. The Business bears the costs unless the audit reveals a material breach of this DPA by the Operator.