Telegram bot privacy

This notice covers @OnchainToolsAppBot, the OCT Telegram bot. It is the page the bot links to from /track on and /track status, and the one its @BotFather privacy-policy setting points at.

What the bot can see

Telegram decides what a bot receives, not OCT:

• In a private chat, the bot sees what you send it.
• In a group where it is not an admin, it sees only commands addressed to bots (messages that start with /) and replies to its own messages. It cannot see ordinary conversation.
• In a group where a group admin has made it an admin and turned on track mode (/track on), Telegram delivers every message to it. That is the only case in which the bot reads a group's ordinary messages, and making the bot an admin plus running /track on is the group's consent.

Track mode: what is read, and what is kept

In a group with track mode on, the bot reads each new message once, in memory, only to find contract addresses in it. For every address it finds (a "call"), it keeps:

• the group's Telegram chat ID;
• the caller's Telegram user ID (a number), used to tell callers apart;
• the caller's public @username, or, if they have none, an anonymous tag (anon-…). The tag is a keyed hash of the group and the user ID under a server-held secret: it cannot be reversed without that secret, and the same person has a different tag in every group, so tags cannot be matched up across groups;
• the contract address, its chain, and the time it was posted;
• the token's price, market cap and pool liquidity at the time of the call, and its price at about 15 minutes, 1 hour, 4 hours and 24 hours after the call.

For the group itself it keeps:

• whether track mode is on;
• the Telegram user ID of the admin who turned it on (the consent record);
• when it was turned on and off;
• whether the group opted into public listing;
• the group's title, but only while the group is opted into public listing.

It never keeps message text, first or last names, profile photos, phone numbers or any other message content. Messages from groups that have not turned track mode on are checked only for commands addressed to the bot and are otherwise discarded; nothing from them is recorded. Posts made on behalf of a channel or anonymously as the group, and automatic forwards from a linked channel, are not recorded.

Who can see it

Grades are shown only inside the group they came from, in reply to /lb and /grade. Nothing is published anywhere else. An admin can run /track public on to opt the group into a future public leaderboard. Today that only sets a flag, and no public page exists yet. If one launches, this notice will say so before any group's data appears on it.

Inside OCT, this data is held in OCT's database. Only the OCT backend can access it; it is not readable from the OCT website or console.

Anonymous usage counts, keyed by a hashed group ID and never a user or chat ID, are sent to our analytics provider.

How long it is kept

• Calls: 90 days, then deleted automatically.
• A group's track-mode settings: while track mode is on. Once it is turned off, they are deleted automatically after 90 days, together with any calls still kept.
• Immediately: a group admin can run /track forget confirm to delete every recorded call and the group's track-mode settings at once.

/track off stops new calls being recorded; calls already kept then age out as above.

The bot's other features

Outside track mode, the bot keeps a small record for each chat that has run /start:

• the chat ID, its type and title;
• the Telegram user ID of the person who added it;
• the alert settings chosen there;
• if the chat was linked to an OCT account with /link, which account.

A link code used by /link is kept for ten minutes and is stored only as a hash.

Contact

Questions and deletion requests beyond what the commands above do go to the OCT team through the contact links on the OCT website.