Ботодел (Ботодел) is a service for creating personal AI assistant bots in Telegram, available via @botodelobot, the bots created with it, their “Manage” mini app, and the website botodel.uniiq.ru. The data controller is individual entrepreneur Aleksandr Loginov (ИП Логинов Александр Владимирович, INN 590773128432). Contact: loginov.uniiq@yandex.ru.
2. Data we collect
Telegram data: user ID, name, username, language and profile photo, as provided by Telegram to bots.
Messages and content: text, voice messages, images, files and documents sent to a bot, and knowledge the owner uploads.
Bot memory: facts, notes, tasks and reminders the bot saves from conversations.
Settings: bot personality, access rules, time zone, connected chats.
Payments: subscription and balance history. Payments are made with Telegram Stars; we never receive card details.
Google user data — only if the bot owner connects Google Sheets (section 5).
3. How we use data
To let the bot reply, remember context and carry out requests and reminders; to manage plans, subscriptions and balance; to operate the service, fix errors and prevent abuse. We do not sell personal data and do not use it for advertising.
4. Sharing
To generate replies, relevant parts of the conversation, materials and bot memory are sent to AI model providers that process them on our behalf: Anthropic, DeepSeek, OpenAI, Google (via OpenRouter) and DeepInfra. Some of them are located outside Russia. Messages are delivered through Telegram under Telegram's own terms. We do not share data with anyone else except where required by law.
5. Google user data
This section describes how Ботодел accesses, uses, stores, shares, protects, retains and deletes Google user data. Connecting a Google account is optional and is done only by the bot owner via “Sign in with Google”.
5.1 What Google user data we access
Google Sheets, via the OAuth scope https://www.googleapis.com/auth/spreadsheets: the contents (cell values) of the spreadsheets the owner asks the bot to work with.
OAuth tokens (access token and refresh token) issued by Google for this scope.
We do not access Gmail, Google Drive files, contacts, calendar, photos, the Google profile or any other Google data.
5.2 How we use Google user data
Only to provide the user-facing feature the owner requested: reading cells from, and writing or appending rows to, the owner's spreadsheet when the owner explicitly asks the bot in the chat (for example, “add October office expenses: 24,378” or “how much did we spend on the office this year?”).
We limit our use of Google user data to providing this user-facing feature. We do not use it for any other purpose, including targeted, personalized, retargeted, interest-based or any other advertising; selling to data brokers or providing to information resellers; determining credit-worthiness or lending purposes; or creating databases.
Google Workspace APIs are not used to develop, improve, or train non-personalized AI and/or ML models. Data obtained through Google Workspace APIs (Google Sheets) is not used to develop, improve or train generalized or non-personalized AI/ML models, by us or by anyone else.
No person at Ботодел reads Google user data, except with the owner's explicit consent (e.g. a support request), for security purposes (investigating abuse), or to comply with applicable law.
5.3 How we share, transfer or disclose Google user data
We do not sell Google user data and do not transfer or disclose it to third parties for purposes other than the ones described in this section.
To answer the owner's request, the relevant cell values are sent to the AI model provider that generates the bot's reply (Anthropic, DeepSeek, OpenAI, Google via OpenRouter). They process it solely to produce that reply on our behalf.
We do not transfer Google user data to third parties for targeted, personalized, retargeted or interest-based advertising, for sale to data brokers or information resellers, for determining credit-worthiness or lending purposes, or for training generalized AI or machine-learning models.
We may disclose data if required by law or to protect against fraud or abuse.
5.4 How we store and protect Google user data
OAuth tokens are stored on our server in a dedicated per-owner credentials store, separate from conversation data, accessible only to the service process.
Security procedures are in place to protect the confidentiality of Google user data, and we use encryption to protect it.
All traffic between users, our server and Google APIs is encrypted in transit (HTTPS/TLS).
Server access is restricted to the service operator via SSH keys; database backups are encrypted.
If we become aware of unauthorized access to or use of user information, including Google user data, we will promptly notify affected users as required by applicable law.
We do not copy entire spreadsheets and do not keep a separate copy of their contents. Cell values the bot read may remain in the chat history with the bot as part of its reply.
5.5 Retention and deletion of Google user data
We retain Google user data only for as long as needed to provide the feature described above, unless a longer retention period is required by law. When that period ends, we delete it.
OAuth tokens are kept only while the Google connection is active.
On request to loginov.uniiq@yandex.ru, we delete the stored tokens within 7 days and delete chat history containing spreadsheet data within 30 days.
5.6 Limited Use
Ботодел's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
6. Storage, security and retention
Data is kept while the bot or account exists. Server access is restricted, connections use TLS, backups are encrypted. On request we delete your data or the bot's memory about you within 30 days, except payment records we must keep by law.
7. Your rights
You may request access to, correction or deletion of your data and withdraw consent by emailing loginov.uniiq@yandex.ru.
8. Children
The service is not intended for children under 14.
9. Changes
We may update this policy; the new version is published on this page with its date.