Privacy Policy

1. Who we are

Animindus (“we”, “the service”) is a Telegram client app with an additional work layer (Workspace): tasks, calendar, files, integrations with outside services. Privacy contact: info@animindus.com.

2. What data we process

• Identification through Telegram. You sign in through our Telegram bot: we confirm that you own the Telegram account given before creating an account in the service. Your Telegram chats themselves are processed by the app locally on the device through Telegram’s official protocol (TDLib) and are not sent to our server, except when you yourself explicitly save a file or message to the Workspace (a task, a link to an event, etc.) or run AI features — see section 4.
• Device and session data. Device type, app version, session tokens — for sign-in and the list of active devices to work.
• Crash reports. If the app quit with an error or stopped responding, on the next launch it sends us a report: the type and text of the error, where in the code it happened, the app and Android versions, the device model. Reports are only used to fix errors, are stored encrypted and deleted after 90 days.
• Workspace data. Tasks, workspace names and related metadata that you create in the app.
• Data from connected outside services (Google). If you connect a Google account, we receive and store (encrypted) an access token limited to the permissions you explicitly granted — see section 3.

3. Use of Google API data

When you connect a Google account, we ask for two permissions only:

• calendar.events — to show your upcoming events and create new events from agreements in Telegram chats, when you ask.
• drive.file — access only to files created through our app (the Animindus folder on your Google Drive) or that you yourself explicitly picked in Google’s file picker (Google Picker). We don’t get access to your whole Google Drive.

Animindus’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

We don’t sell data received through Google APIs, don’t use it for advertising and don’t pass it to third parties, except where needed for the feature itself to work (for example, infrastructure providers handling a request on our behalf) or where required by law. Access can be turned off at any time in the app’s settings — this revokes the token on Google’s side at once and deletes the stored credentials on ours.

4. AI features and Bitrix24

• What is sent. Only when you yourself run an AI feature (a summary, finding tasks, meetings, promises, etc.) or an automation you set up: the text of the chosen messages — for an automation, the new messages of the chats you chose, no more than 200 at a time — with sender names and chat titles. The text goes to our server and from it to the AI model provider Orenagi (orenagi.com), which returns the result.
• Masking. Still on the device, email addresses, bank card and phone numbers in the text are replaced with placeholders, so the AI provider doesn’t see them. The original values are sent to our server so that the saved result reads in full.
• What is stored. AI results (the “AI results” section) are stored on our server encrypted and deleted automatically — after 30 to 365 days depending on the plan — or earlier if you delete them. For automations we store their settings and the numbers of the last messages read, not their text. The original message text itself is not kept after processing. The AI provider doesn’t use the texts sent to train models.
• Bitrix24. If you connect Bitrix24, we store your portal’s webhook address or access token encrypted. Tasks that you (or an automation you set up) send to Bitrix24 — title, description and due date — go to your portal and aren’t kept by us.

5. Storage and protection

Access tokens for outside services are stored encrypted (AES-256-GCM). We don’t store the original passwords for either Telegram or Google — sign-in always goes through the official authorization of the service concerned.

6. Data location and cross-border transfer

The service’s main database is physically located on a server in the Russian Federation. When you connect an outside service (for example, Google), part of the data — to the extent described in section 3 — is sent directly to that service’s provider, including when its servers are outside Russia. By connecting an outside service you agree to such a transfer to the extent stated. The same applies to the text you send to AI features (section 4): the AI model provider’s servers may be outside Russia.

7. Your rights

You can ask us to delete your account and the data tied to it, revoke access to any connected outside service, or ask a question about how your data is processed, by writing to info@animindus.com.

8. Changes to this policy

When this policy changes substantially, the date at the top of the page will be updated.