Effective date: 06.11.2026
1. Parties and Authority
1.1. Operator and these Terms
Botmindly (the "service") is operated by Oleksandr Shapoval, a ФОП registered in Ukraine under the legal name "Shapoval Oleksandr Serhiiovych" (ФОП Шаповал Олександр Сергійович) (the "Operator"). These Terms of Service ("Terms") govern the use of Botmindly through the website at https://botmindly.com, the Cabinet at https://app.botmindly.com and the Botmindly API.
1.2. Definitions
- Business - a legal entity or registered entrepreneur (including a sole proprietor) that connects messaging channels and uses Botmindly to communicate with its Customers.
- Customer - a person who communicates with a Business through a connected channel. Customers do not need a Botmindly account.
- Cabinet user - a person who signs in to the Botmindly Cabinet and accesses the Businesses associated with their account.
- Payer - a company or registered entrepreneur designated to pay for a Business's use of Botmindly.
- Tenant - a system that accesses Botmindly through its API and manages the Businesses associated with it.
- Platform - a messaging service such as Instagram, Messenger, WhatsApp or Telegram.
- AI provider - OpenRouter or an external model provider involved in generating AI responses.
These terms have the same meaning in all Botmindly legal documents.
1.3. Contracting parties
The contract under these Terms is made between the Operator and the Business. The person who registers in the Cabinet and creates a Business accepts these Terms on behalf of that Business.
A Payer that is not the Business itself joins these Terms, as far as payment is concerned, by its own act: a written confirmation sent to the Operator by e-mail, or payment of an invoice that names the Business being paid for and refers to these Terms. Until it does, the duty to pay rests with the Business.
An organization that connects its own system to the Botmindly API as a Tenant joins these Terms by a written confirmation from its authorized representative, sent to the Operator before API credentials are issued. A Tenant may access only the Businesses associated with it and may use its credentials only within the authority granted; technical access gives it no independent rights to a Business's Customer data.
Actions of a Cabinet user within their access to a Business are actions of that Business, except actions made possible by a security breach on the Operator's side.
1.4. Acceptance of documents
When registering, a Cabinet user accepts these Terms and confirms that they have read the Privacy Policy.
When creating a Business and when connecting a channel, the Cabinet user confirms their authority to act on behalf of the Business, accepts these Terms and the Data Processing Agreement (DPA), instructs Botmindly to process Customer personal data under the DPA and confirms the Business's duty to share Customer data lawfully and to inform Customers about the processing. When connecting a channel, they also confirm that new messages from that channel will be stored in the Business's conversations.
These confirmations do not establish authority to enter into contracts on behalf of a separate Payer or another legal entity: a Payer and an external Tenant join these Terms themselves, as set out in Section 1.3.
Botmindly records the time of each confirmation, the account and the version of the accepted document. The parties accept these records as evidence of the contract and of the accepted version.
These Terms are published in English and Russian with the same content. The contract is made in the language version that the Cabinet user selects and accepts; if the versions differ, the accepted version prevails.
2. Services
Botmindly helps Businesses manage Customer conversations through connected Platforms: it receives and stores conversations, prepares AI responses from the Business's instructions and knowledge base, and lets a person take over a conversation.
Botmindly sells nothing to Customers and accepts no payments from them: the bot only answers Customers' questions on behalf of the Business. Sales, payment, delivery and any other obligations to a Customer arise between the Business and that Customer.
By connecting a channel, including a Telegram account through Telegram Business, the Business allows Botmindly to send messages from its conversations to AI providers only so that the bot can prepare a response. The data AI providers receive is described in the Privacy Policy, Section 4.
The service depends on Platforms, hosting providers and AI providers. The Operator does not guarantee their uninterrupted operation and is not liable for their independent actions, except where the Operator's liability is established by applicable law or results from its own breach. Connecting a Platform does not override its rules and restrictions.
3. Business Obligations
3.1. Accounts and access
A Cabinet user must be entitled to represent the Business and to authorize access to its Platform accounts. Connecting accounts that the user does not own or is not authorized to manage is prohibited.
Businesses and Tenants use the authorization methods supported by the Platform and do not request or collect Meta or Telegram account passwords, login codes or one-time verification codes from anyone.
Cabinet users and Tenants protect their passwords, API keys and Platform tokens and do not share them.
3.2. Customer data
The Business must inform Customers that their messages and personal data are processed through Botmindly and must have a lawful basis to receive, store, use and share this data, including processing by AI providers. The Business complies with applicable data protection law and Platform rules and does not configure the bot to request data that is not needed to communicate with the Customer.
A Business that uses a Telegram bot or WhatsApp gives Customers easy access to its own privacy policy, which explains the Business's role, the processing of conversations through Botmindly and the involvement of AI providers. For Telegram, if Telegram's standard bot privacy policy does not match the actual processing, the Business publishes its own through BotFather.
Acceptance of the DPA does not by itself prove that every Customer received the required notice or gave consent.
If a Business permanently stops a Telegram bot, it arranges the deletion of the user data collected through that bot as Telegram requires. Revoking the bot token or removing its webhook does not delete conversations in Botmindly: to do that, the Business deletes the conversations or the channel (Data Deletion).
4. Business Materials and AI Responses
4.1. AI responses
AI responses may be inaccurate, incomplete or based on outdated information and are not reviewed by a person before they are sent. The Business keeps its instructions and knowledge base accurate and up to date and is responsible for their content and for how it uses bot responses with Customers. The Operator is responsible for its own failures: a technical error of the service, delivery of a response to the wrong Customer or channel, disclosure of one Business's data to another - within the limits of Section 9.
The bot introduces itself to Customers as an AI assistant, and the Business's instructions cannot turn this off.
4.2. Rights to materials
The Business confirms that it holds the rights to the instructions, knowledge base, photos and other materials it uploads to Botmindly and that their use in the service does not infringe third-party rights.
The Business grants the Operator a non-exclusive, royalty-free right to store, process, transmit and display these materials for the term of the contract and only to provide the Botmindly services, including transfer to Platforms and AI providers. The Operator claims no rights to the knowledge, instructions and bot responses and does not train models on them.
5. Payment
Prices are in US dollars. The current rate is shown on the Botmindly website; another rate applies only if the parties agreed on it before the period starts. The billing period is a calendar month unless the invoice states another period.
AI usage is calculated from the Botmindly cost records for the period. A payment is made on the day the funds reach the Operator's account.
Early access. While a Business has early access, the Payer pays for actual usage at the end of each period against the Operator's invoice; the payment deadline is stated in the invoice. The terms and duration of early access are agreed between the Operator and the Business separately.
After early access, the Payer pays an advance against an invoice at the start of each period. If the advance exceeds actual usage, the difference is credited to the next invoice; if it falls short, the difference is added to it. The Operator gives at least 30 days' notice of the switch to advance payment.
Each party pays its own bank and payment service fees. Taxes charged to the Payer in its own country are paid by the Payer.
When the contract ends, the Operator refunds the Payer the unused balance of the advance and any payments for periods that have not started. To request a refund, the Payer writes to hi [at] botmindly.com; the Operator sends the refund within 7 working days of the request, and the time it takes to arrive depends on the banks and payment systems. The costs of the refund, including bank and payment service fees, are borne by the Payer and deducted from the refunded amount.
The Operator gives 30 days' notice of price changes. If a period is not paid, the Operator may suspend the service until payment; the Business's data is not deleted.
A charge may be disputed by a claim under Section 10.2. The Operator reviews the claim and replies within 30 days. A confirmed incorrect charge is credited to the next invoice or refunded, as the Payer chooses.
6. Acceptable Use
6.1. Prohibitions
Cabinet users, Businesses and Tenants comply with the law and the rules of every connected Platform. The bot itself is not a party to the contract: the Business configures and uses it so that the bot complies with this section. Botmindly, including AI responses and human messages, must not be used for:
- Spam, unsolicited bulk messages, phishing, fraud, or obtaining money, credentials or personal data by deception.
- Impersonating other people, Businesses or account owners, harassment, intimidation or threats.
- Continuing to message a Customer who asked to stop, including through other channels, or sending messages outside the conditions the Platform allows.
- Circumventing Platform blocks and restrictions, including by replacing tokens, reconnecting accounts, or using alternative channels or Tenants.
- Illegal goods and services, malware, and materials that infringe others' rights or are prohibited by the Platform.
- Collecting, extracting, combining, disclosing or selling personal data without the necessary rights and lawful basis, including passing information from one Customer's conversation to another Customer.
- Buying, selling or licensing Meta Platform Data, or using it for surveillance, discriminatory decisions, decisions on eligibility for rights or opportunities, or unauthorized profiling.
- Scraping Telegram data, building datasets from conversations, or training or improving AI models on Platform data without the necessary permission and consent.
- Instructing the bot to deceive Customers, to hide that it is an AI assistant or to disclose Customer data to unauthorized recipients, or making medical, legal or financial decisions without human involvement.
- Accessing another Business's or Tenant's data without permission, exploiting vulnerabilities, deliberately overloading the service, or bypassing rate limits.
6.2. Violations
Depending on how serious a violation is, the Operator sends a warning, restricts access, suspends a channel or blocks access. In case of a serious violation, a threat to the security of the service, Customers or other Businesses, or where the law, Meta or Telegram requires it, the Operator suspends the channel, bot or access immediately, without waiting for the review to finish; it tells the Business the reason and lifts the suspension if the suspicion is not confirmed. A decision can be appealed by writing to hi [at] botmindly.com.
Suspected violations and vulnerabilities in Botmindly can be reported to hi [at] botmindly.com, without accessing, changing or disclosing anyone else's data.
7. Related Documents
Personal data, recipients and retention are described in the Privacy Policy, processing of Customer data on behalf of the Business and subprocessors in the Data Processing Agreement, and deletion methods in the Data Deletion Instructions. These documents do not override applicable law or Platform rules.
If the documents conflict, the DPA prevails for Customer personal data processed on behalf of a Business, and the Privacy Policy for data the Operator processes for its own purposes, followed by these Terms.
8. Termination
The Business may end the contract at any time by deleting the Business in the Cabinet or through the API or by writing to the Operator at hi [at] botmindly.com. The Operator may end the contract by giving the Business at least 30 days' notice by e-mail.
If these Terms are breached, the Operator sends the Business a notice describing the breach and gives it 14 days to remedy it. If the breach is not remedied, the Operator may end the contract. The contract is ended or access blocked immediately, without a remedy period, in the cases of Section 6.2 or if the breach cannot be remedied.
After the contract ends, the Business's data is returned or deleted under the Data Processing Agreement, Section 7.
9. Liability
Botmindly is provided "as is". The Operator does not guarantee uninterrupted availability and gives advance notice of planned downtime. Support is by e-mail at hi [at] botmindly.com on working days; security incidents affecting data are handled on any day.
The Operator's liability for all claims of the Business and the Payer related to these Terms is limited to the fees the Operator received for its own services in the last 12 months, but not less than USD 1. Amounts passed on to model providers and other providers are not included. This limitation does not affect the statutory rights of Customers and other third parties.
The limitation does not apply where and to the extent that the law prohibits it, or to intentional breaches by the Operator.
Neither party is liable for lost profits or indirect damages, except where the law does not allow such an exclusion.
The Business reimburses the Operator for documented, reasonable costs of third-party claims caused by the Business's breach of the law, of third-party rights or of these Terms, except where they are caused by the Operator's own breach.
10. Final Provisions
10.1. Changes
A new version of these Terms is published on the website with its effective date. If a change affects users' rights or obligations, the Operator notifies it by e-mail to the address of each account before the new version takes effect. Continuing to use Botmindly after the new version takes effect means accepting it.
10.2. Governing law and disputes
These Terms are governed by the law of Ukraine. This choice does not override mandatory rules of another country that apply regardless of the parties' choice.
A dispute is first settled by a claim sent to hi [at] botmindly.com; the Operator replies within 30 days. A dispute not settled this way is heard by a competent court of Ukraine.
Legal notices are sent by e-mail to hi [at] botmindly.com and to the account's e-mail address. A notice is deemed received on the working day after it is sent, unless the sender receives a non-delivery message.
10.3. Force majeure
A party is not liable for failing to perform an obligation caused by circumstances it could not foresee or prevent: military action, regional power or communications outages, decisions of public authorities, or a prolonged failure of a Platform or infrastructure provider. The party informs the other as soon as it can. If such circumstances last more than 60 days, either party may end the contract by e-mail.
10.4. Severability and assignment
If a provision of these Terms is held invalid, the remaining provisions stay in force, and the invalid provision is replaced by a valid one closest in meaning.
The Business may transfer its rights and obligations under the contract only with the Operator's written consent. The Operator may transfer the contract to a successor that continues to provide Botmindly, with at least 30 days' notice to the Business by e-mail.
11. Operator Details
Operator: Oleksandr Shapoval
Legal name: Shapoval Oleksandr Serhiiovych (ФОП Шаповал Олександр Сергійович)
Legal status: ФОП (Фізична особа - підприємець)
Country of registration: Ukraine
Website: https://botmindly.com
Cabinet: https://app.botmindly.com
E-mail: hi [at] botmindly.com