Privacy Policy

November 1, 2026

AKELA is a personal assistant in Telegram, at @akela_ai_bot. The service is operated by the developer of AKELA and is available at https://akela.tools. This policy explains what data AKELA accesses, why, how long it is kept, and how you can delete it.

AKELA's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

What AKELA does

You write or send a voice message in Telegram. AKELA answers. If you choose to connect them, AKELA can also show and change Google Calendar events you ask about, and read, reply to, send, and file Gmail messages you ask about. Creating or changing an event, and sending or moving mail, happens only after you press a confirmation button. Reading happens when you ask.

AKELA does not generate images. AKELA does not use Google APIs for AI-generated non-consensual intimate imagery (NCII).

Google data AKELA requests

AKELA asks for a Google permission only when you start that connection, and only for the scope below. It does not request access to Drive, Contacts, or your full mailbox.

• Google Calendar. Scope https://www.googleapis.com/auth/calendar.events. This lets AKELA list, create, update, and delete calendar events that you ask it to manage. A narrower read-only scope cannot create or change events. AKELA does not use this access to email guests about a change.
• Gmail. Scope https://www.googleapis.com/auth/gmail.modify. This lets AKELA read messages you ask about, create and send mail you confirm, and apply labels such as inbox, archive, spam, or trash. This scope does not allow AKELA to permanently delete messages while skipping the trash. A read-only scope cannot send or file mail, which the assistant does when you ask it to.

Google also provides the email address of the account you connect, and the OAuth tokens needed to keep that connection working. You can review the same request on Google's consent screen before you accept it.

How Google data is used

Google user data is used only to provide or improve the user-facing features that are visible in Telegram and on akela.tools: answering you, showing your schedule, and carrying out a calendar or mail action you requested and, where required, confirmed.

To compose that reply, AKELA sends your request, the recent conversation, and the calendar or mail information needed for that request to Google's Gemini model. That transfer is made only to provide the feature you asked for. AKELA does not use Google user data to train generalized or non-personalized AI models, and it does not allow that data to be used for advertising.

AKELA does not sell Google user data. It does not transfer or use it for advertising, retargeting, personalized ads, credit-worthiness, or lending. It does not transfer it to advertising platforms, data brokers, or information resellers.

Limited Use

Use of data obtained through the Calendar and Gmail scopes, including data aggregated, anonymized, or derived from it, is limited as follows.

• AKELA uses it only to provide or improve user-facing features that are prominent in the AKELA interface.
• AKELA transfers it only to provide or improve those features with your consent, for security, to comply with applicable law, or as part of a merger, acquisition, or sale of assets after obtaining your explicit prior consent.
• People do not read this data unless you give affirmative agreement to view a specific message, event, or other item; it is necessary to investigate a bug or abuse; it is necessary to comply with applicable law; or the data, including derivations, is aggregated and anonymized and used for internal operations in line with applicable privacy law.

The developer, employees, agents, and contractors of AKELA are required to follow these limits.

Who receives data

• Google stores your calendar and Gmail, and processes the Gemini request described above.
• Telegram delivers the conversation, including the reply you asked for. That reply may quote an event or message you asked AKELA to handle.
• A mailbox provider you choose, such as Yandex, iCloud, or Mail.ru, receives the connection to the mailbox you add. That is separate from Gmail.

Mailbox passwords and Google tokens are not sent to the language model and are not written into the operations log.

What else is stored

• Your Telegram identifier, name, username, and time zone.
• The text of your messages. A voice message is transcribed on the AKELA server and the audio file is deleted immediately afterward. The transcript is then treated as text you sent.
• The last 12 turns of the conversation, so the assistant can follow the current task.
• For a non-Google mailbox: the address, server, and app password you enter, plus mail rules you save.
• An iOS calendar subscription token, if you open that link.
• An operations record for 90 days: the request you sent, whether it succeeded, and a short status. If the reply shown to you quotes an event or message you asked about, that reply text may be in this record. The record is not a copy of your mailbox.
• A pending confirmation, kept for 30 minutes, so AKELA can finish an action after you press the button.

Storage and security

Data is stored in a database on the server operated by the developer of AKELA. Connections to AKELA use HTTPS. Google tokens and mailbox passwords are stored so the connection you created keeps working. They are not placed in the Telegram chat. Access to the server is limited to the developer of AKELA. AKELA does not keep a permanent archive of your Gmail mailbox.

How long data is kept

• Conversation memory: the last 12 turns.
• Operations records: 90 days, then deleted.
• Unconfirmed actions: 30 minutes.
• Google tokens, mailbox credentials, and your profile: until you disconnect that service or ask AKELA to delete your data.

How to disconnect and delete

• In Telegram, send /disconnect. This deletes the stored Google Calendar tokens and the iOS calendar link.
• Open Mail in Telegram and press Disconnect on a mailbox. This deletes the stored credentials for that mailbox.
• Revoke AKELA at Google Account permissions. This stops AKELA from calling Google. Also disconnect in Telegram so the stored tokens are deleted.
• To delete the profile, conversation, tokens, and operations records, email info@akela.tools or send the bot the message “delete my data”. The developer deletes that account record.

You can read this policy at any time from akela.tools without signing in. The same URL is the privacy policy linked from the Google consent screen.

Children

AKELA is not directed to children, and it does not knowingly collect their data.

Changes

If AKELA uses Google user data for a new purpose, this policy will be updated first and you will be asked to accept the updated policy before that new use. The date at the top is the date of the current version.

Contact

Questions about this policy or your data: info@akela.tools. You can also message @akela_ai_bot.