Effective date: 06.11.2026
1. Operator and Roles
Botmindly is provided by Oleksandr Shapoval (the "Operator"), a ФОП registered in Ukraine under the legal name Shapoval Oleksandr Serhiiovych (ФОП Шаповал Олександр Сергійович). Website: https://botmindly.com, Cabinet: https://app.botmindly.com, data protection contact: hi [at] botmindly.com.
This Policy explains what personal data Botmindly processes, why, who receives it, how long it is kept and how to delete it. It covers Customers who message Businesses, Cabinet users, owners of connected accounts, Payer contacts, Tenant representatives and website visitors. Terms are used as defined in the Terms of Service.
For Customer conversations, the Business is the controller of personal data: it decides why it communicates with Customers and what data it puts into Botmindly, and the Operator processes this data on its behalf under the Data Processing Agreement. For the data of Cabinet users, Payers, Tenants and website visitors, the Operator is the controller.
2. Data We Process
Customers. From Platforms: the Platform identifier (the sender's number on WhatsApp), name and profile name, message text, time and message identifiers, replies and quotes, message edits and deletions, reactions and button choices. Attachments: photos, videos, audio, voice messages, documents, stickers, shared contacts with names and phone numbers, shared locations with coordinates, and place names. A conversation also holds AI responses, messages from Business representatives, including those written directly in Instagram or the Facebook Page inbox, notes for the bot, records of handover to a person, and a Customer's request not to be messaged again. For Messenger and Instagram, Botmindly may request available profile details from Meta.
Cabinet users. Name, e-mail address, sign-in data in protected form, time zone and display formats, links to Businesses and, if browser notifications are enabled, the subscription data for them.
Owners of connected accounts. Account, bot or Page identifiers and names, connection status, the identifier of the Meta user who authorized the connection (used to find channels when Meta sends a deletion request), channel access credentials. Through Instagram Login, Botmindly receives the account's identifier, username and name and access to its messages.
Businesses, Payers and Tenants. The Business name, country and time zone, records of accepted documents, instructions and knowledge base with photos. Payer data: type, country, legal name, tax number, billing address, contact person, billing e-mail, assigned Businesses and periods. Usage records: time, Business, channel, model, tokens, cost, processing result, content types and internal conversation and message numbers - without message text, Customer names or Platform identifiers. Tenant data: name, API access data in protected form, event delivery addresses.
Website visitors. The channels and account addresses to connect, the contact method, contact details, page language and the campaign tags of the link they came by (UTM, ref) from the connection request form, and e-mails sent to hi [at] botmindly.com.
Technical data. IP addresses and technical request details.
3. Purposes and Legal Bases
The Operator processes personal data on the legal bases of Article 11 of the Law of Ukraine "On Personal Data Protection":
- Customer communication and AI responses - the basis is determined by the Business as owner of its Customers' data; the Operator processes it on the Business's instructions under the DPA.
- Accounts, Platform connections and Tenant events - performance of the contract under the Terms of Service.
- Browser notifications - consent, given by turning notifications on and withdrawn by turning them off.
- Website inquiries - steps taken at the person's request before a contract.
- Usage accounting and invoices - performance of the contract and the Operator's duty to keep tax records.
- Cost records with internal numbers and details of a deleted Business with its confirmations - the Operator's legitimate interest in checking charges, settling claims and proving the terms under which the Business worked.
- Security and diagnostics - the Operator's legitimate interest in protecting the service and its users.
The Operator's legitimate interest does not extend to the content of Customer conversations: the Operator processes it only on behalf of the Business and only for purposes the Business determines.
Botmindly sends no advertising or bulk messages. A Customer sends marketing opt-outs and objections to processing to the Business, which handles them as controller. When a Customer asks not to be messaged again, Botmindly blocks bot replies and messages sent by a person through Botmindly until the Customer writes again.
4. Data Shared with AI Providers
To prepare a response, Botmindly sends OpenRouter and the model provider it selects (together, AI providers): the bot's general rules, the Business's instructions and knowledge base text, messages and notes of the current conversation, quoted message text, including older messages, attachment types, names and sizes, names of shared contacts and place names, and descriptions of knowledge base photos.
The model does not receive, as separate fields, attachment files, phone numbers from contacts, coordinates, Customers' Platform identifiers or their stored names. If such details are written in message text or in the knowledge base, they are included with that text.
Botmindly sends requests only to model providers on the OpenRouter zero data retention list; if no suitable provider is available, no response is generated. OpenRouter keeps technical request metadata, such as token counts and response time, and, under its privacy policy, does not train models on prompts and responses. Providers on that list state in their published policies that they neither keep request data nor train on it; this is the providers' statement, not a guarantee by OpenRouter or the Operator. The Operator does not train models on a Business's conversations or knowledge.
5. Recipients and Processing Locations
| Recipient | What it receives | Where |
|---|---|---|
| OVHcloud | The Botmindly server: database, conversations, Business, Payer and connection data, logs, backups | European Union |
| Backblaze B2 | Attachments, knowledge base photos, encrypted backups | European Union |
| Cloudflare | API, website and file traffic; the Cabinet, accounts, sessions and push subscriptions; technical logs; receiving e-mail to hi [at] botmindly.com and sending service e-mail from no-reply [at] botmindly.com | Cabinet data - EU; Cloudflare network |
| OpenRouter and model providers | The data in Section 4 | United States and other countries |
| Meta and Telegram | Outgoing messages and attachments, profile requests, authorization data; Meta, on its request, details of Businesses with Meta channels and their current Payers (without Cabinet sign-in e-mail addresses) | Platform infrastructure, on their own terms |
| Browser push services | The subscription address and an encrypted notification: Business name, event type, reason for calling a person, internal numbers - without Customer names or message text | Where the browser vendor operates |
| Google Fonts | IP address and request headers when the Cabinet loads fonts | Google servers worldwide |
| The Operator's Telegram chat | Website inquiries | Telegram |
Subprocessors that process data on the Operator's behalf, and their contract terms, are listed in the Data Processing Agreement, Section 4. Platforms also process messages under their own terms and privacy policies.
Personal data may be processed outside the country where the Customer or Cabinet user is located. 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; transfers to these states rely on this basis. The Ukrainian basis does not replace the requirements of the country where the Business and its Customers are located; the bases for transferring Customer data are described in the DPA, Section 5.
6. Retention
- Conversations - one year after the last new or edited message, switch between bot and person, or change of the "needs manager" status; then deleted automatically.
- Attachments - 90 days unless deleted earlier with the message or conversation; attachment details (name, type, size) - until the conversation is deleted.
- Knowledge base, instructions and settings - until the relevant records or the Business are deleted.
- Channel connection data - until the channel is deleted.
- Cabinet profile - until the profile is deleted.
- Usage records with internal channel, conversation and message numbers - 12 months, after which the numbers are removed and only totals per Business and period remain. Internal numbers make it possible to link a record to Platform activity, so the Operator treats these records as pseudonymized personal data and removes the numbers of a deleted conversation, channel or Business immediately.
- Tax records (invoices, Payer data, totals per period) - for the periods set by the tax legislation of Ukraine, including the extensions it provides.
- Name, country and confirmations of a deleted Business - 3 years after deletion (the general limitation period, Civil Code of Ukraine, Article 257); Tenant records - 3 years after its access ends.
- Website inquiries and e-mails - while needed, but no longer than 12 months.
- Technical logs and service records - up to 30 days.
- Database backups - up to 7 days. Deleted data may remain in backups until they are deleted; restoring from a backup does not bring deleted data back.
A record under dispute or review is kept until the dispute or review ends.
7. Rights and Requests
Under Article 8 of the Law of Ukraine "On Personal Data Protection", a person whose data Botmindly processes has the right to:
- Know where their data comes from, where it is, why it is processed, who its owner and processor are and to whom it is disclosed.
- Access their data and learn whether and what data is processed.
- Object to processing, giving reasons.
- Require correction or deletion of data that is inaccurate or processed unlawfully.
- Be protected from unlawful processing and from accidental loss, destruction or damage of their data.
- Limit processing when giving consent, and withdraw consent.
- Know how automated processing of their data works (Sections 3 and 4) and be protected from an automated decision with legal effects for them.
- Complain to the Ukrainian Parliament Commissioner for Human Rights or to a court.
Requests are accepted at hi [at] botmindly.com, including from Customers without a Botmindly account. Do not send passwords or identity documents unless necessary. Within 10 working days the Operator says whether a request will be fulfilled or why it cannot be. A request about data the Operator is responsible for is fulfilled within 30 calendar days of receipt. A request about conversation data is passed within the same period to the Business responsible for it, and the person is told so; the Business decides.
The Operator prepares a copy of a Business's conversations or of Cabinet account data on request; a Business exports its knowledge base to Excel itself. How to delete data is described in the Data Deletion Instructions.
8. Data Protection
Data, Platform access credentials, passwords and backups are stored in protected form, access is limited to people authorized by the Operator, and technical logs are kept. Botmindly does not provide end-to-end encryption of conversations.
If a security incident affects personal data, the Operator takes steps to contain it without undue delay, notifies Meta if Platform Data is affected, notifies affected Businesses within the period in the DPA, Section 9, notifies the supervisory authority where the law requires it, and notifies affected people if the risk to them is high.
Report a possible vulnerability in Botmindly to hi [at] botmindly.com, without accessing, changing or disclosing anyone else's data.
9. Cookies and Browser Storage
The public website sets no cookies and uses no browser storage, analytics or advertising trackers. The Cabinet uses only necessary cookies: for sign-in (30 days) and for interface settings (365 days), so no consent banner is shown.
In browser storage the Cabinet keeps a device identifier for notifications and display settings. Signing out and deleting the profile do not clear this data; it can be removed in the browser settings.
10. Changes to this Policy
A new version of this Policy is published on this page with its effective date. If a change affects how personal data is processed or people's rights, the Operator notifies it by e-mail to the address of each account before the new version takes effect.
This Policy describes how data is processed and is not in itself consent to processing. If new processing requires a person's consent, the Operator asks for it separately and does not start such processing without it.