This website
No cookies
This website sets no cookies and stores nothing in your browser.
No account
There is no login, no form that saves data, and no newsletter on this site.
No ad trackers
We do not load ad networks or tracking pixels. If we add privacy-friendly page counts later, we will list them here first.
AddThisBot is a static website. It is hosted on Cloudflare Pages. Like every web host, Cloudflare processes your IP address and request details to deliver pages and to block attacks. See the Cloudflare privacy policy.
Pages load fonts from Google Fonts. Your browser sends a request to Google to get them. See the Google privacy policy.
When you tap “Open in Telegram”, you leave this site and go to Telegram. The link contains ?start=site so the bot knows you came from here. It contains nothing about you.
The bots
The bots run on the Telegram Bot API. When you use a bot, Telegram sends it the commands, messages and taps meant for that bot, plus your Telegram user ID, name and @username. In a group, a bot that you make an admin (for example a moderation bot) can see all messages in that group, because it needs them to do its job. A bot does not see your phone number unless you share it.
Each bot stores only the data it needs to work: for example your reminders, your group's expense list, or your Pro status. Every bot page has a privacy section with the exact list. The full list for each bot is also below.
We do not sell your data. We do not use the content of your messages for ads.
Payments
Pro is paid in Telegram Stars inside the bot. Telegram handles the payment. The bot receives a payment confirmation and your user ID so it can turn on Pro. We never see your card or bank details.
Some bots also offer a monthly Stars subscription. You can cancel it in Telegram at any time.
Data per bot
Tap a bot to see what it stores. This text comes from the same data as the bot pages.
WhisperLock @WhisperLockBot
- Message text you write is stored in a
whispersrow (sender id, sender name, target, body, reveal count) so it can be shown again when the recipient taps it. - Your Telegram user id, username, and Pro status are stored in a
usersrow. - No message content is shown to anyone except the addressed recipient and you, the sender; other chat members only ever see the locked card.
Nudge @NudgeRemindBot
- Each reminder is stored as a row with your user id, chat id, the reminder text (
body), fire time, and repeat interval, so the 1-minute cron can find and deliver it. - Your Telegram user id, username, timezone offset, and Pro status are stored in a
usersrow. - Reminder text is only ever sent back to the chat it was created in.
Anon Inbox @AnonInboxProBot
- Incoming anonymous messages are stored in a
messagesrow (owner id, sender id, body) so you can read and reply to them. - A
sessionsrow tracks that you're mid-conversation;link_openscounts visits to your link;blocksstores who you've silently blocked. - The sender's Telegram identity is never shown to the owner on the free tier; Pro adds limited hints, not the sender's full identity.
- A public-answer card you build from a message shows your answer, the question, and your link — never the original sender's identity.
SplitTabs @SplitTabsBot
- Each group's ledger is stored per chat: a
groupsrow (title, Pro flag, currency, language, last /nudge time, whether the tip was shown),members(handles seen in the chat), and anexpensesrow per entry (payer, amount, description). - No banking or payment details are ever stored — /settle only calculates and displays a settlement plan; it doesn't record or move real money.
- Data is scoped to the group chat it was entered in; /clear wipes that group's ledger.
HabitStreak @HabitStreakProBot
- Each habit is stored as a
habitsrow under your user id; daily check-ins are stored incheckins(habit id, day) — just a date marker, no notes or content. - Your check-in hour and timezone are stored in a
prefsrow; a background check runs every hour and prompts you once a day, at your chosen local hour. - No habit data is shared to any group or other user — it's private to your account and visible in the Mini App board.
Event RSVP @EventRSVPProBot
- Each group's events are stored per chat:
events(title, time, creator, card message id) andrsvps(one row per user per event, so a repeat tap moves you between buckets instead of duplicating). - Names shown on the event card come from your Telegram display name, capped at 30 names per bucket before it switches to a '+N more' count.
- Cancelling an event marks it cancelled rather than deleting history, so the group's event id numbering stays consistent.
AnonSay @AnonSayProBot
- Anonymous posts are stored in a
postsrow (chat, message id, sender id, body) — the sender's identity is kept internally so /reveal and /ban can work, but is never shown to other group members. - A per-group
saltis generated once and used to hash the sender id shown to admins via /reveal, so the hash isn't reversible without the bot's data. bansstores a silent per-group block list;admin_cachecaches admin-status checks for 10 minutes to avoid hammering Telegram's API.- A
sessionsrow holds the group you picked when posting via DM, so the bot knows where to relay your next message; it is cleared after that post. - Posts are purged automatically after 30 days.
Party Pack @PartyPackProBot
- The bot stores which prompts each chat/category has already shown (
seen), the Spicy toggle per chat (chats), and recent members per chat (members) so "Next player" can pick someone. - No prompt responses or personal answers are stored — only which prompt indexes have been shown, to avoid repeats.
- Spicy content is tasteful 18+ only — no explicit sexual content, no illegal acts — and is off by default even for Pro users.
Group Pulse @GroupPulseProBot
- Only counters are stored:
counts(per chat, user, day: text/media/other counts) andhours(per chat, day, hour) for the busiest-hour stat — never message text. membersstores a display name and last-seen timestamp per chat so leaderboards and /quiet can show who's who.- Data is retained 14 days on the free tier and 90 days on Pro, then cleaned up automatically; /reset (admins only) wipes a group's data immediately.
When Is It @WhenIsItBot
- Each member's saved timezone and preset zones are stored under their user id; named /team sets are stored per group for Pro.
- No message content is stored — only zone names/offsets you explicitly save with /tz, /preset, or /team.
- Daylight saving offsets are computed live via the JavaScript Intl API rather than stored, so they're never stale.
Birthday Reminder @BirthdayReminderProBot
- Each member's birthday is stored per group as day and month, plus an optional year if you choose to include one — nothing is stored beyond what you send with /bday.
- A birthday saved in one group is not shared with any other group the bot is in; /forgetme deletes your saved birthday from every group, after you confirm.
- The day-before DM reminder (Pro) only reaches members who have started a private chat with the bot; it never messages someone the bot can't already DM.
Countdown Days @CountdownDaysBot
- Each group's countdowns are stored per chat: target date, label, creator id, and the message id being edited — no personal data beyond who created it.
- Ending a countdown marks it stopped rather than deleting the row, so the group's countdown id numbering stays consistent.
- The bot only edits the one message it posted for each countdown; it doesn't read or store any other group messages.
Word A Day @WordADayLearnBot
- Each word's review schedule (last answer, next-due date, an interval index) is stored per user, per word, so the SM-2-lite spacing can decide when that word comes back.
- Your Know/Don't know taps are only used to update that schedule — no answer text or free-form input is stored, since the interaction is button-only.
- Custom words added with /add (Pro) are stored per user, up to 500, and are never shared with other users.
Focus Timer @FocusTimerProBot
- The bot stores each completed session's length in minutes, per user, per day, to build your daily total and streak — it doesn't know what you actually worked on, only how long the timer ran.
- Group "study together" sessions store who joined a given session so the end-of-session summary can name them; that membership isn't kept beyond the summary.
- Stopping a timer early (the ⏹ button on the session card) logs only the minutes actually completed, not the originally requested length.
Budget Log @BudgetLogBot
- Each expense you log — amount and the note text you sent — is stored per user, so /today, /week, /month, and /export can total and list them back to you.
- The category is guessed from keywords in your note and stored alongside the expense; it's only ever used to build your own totals.
- This is a DM-only bot — nothing you log is posted to a group or visible to anyone but you.
Time Sheet @TimeSheetProBot
- Each time entry — duration, client name, and any task note from /log — is stored per user, so /week, /month, and /invoice can total and list them back to you.
- A running /in clock is stored as an open entry with its start time until you /out; if you stay clocked in past 10 hours, the bot DMs you a reminder to close it out.
- This is a DM-only bot — client names and task notes aren't shared or posted anywhere beyond your own totals.
Icebreaker Daily @IcebreakerDailyBot
- The bot stores which question it posted to each group and when (
posted), so it can avoid repeats and know when the next day's question is due. - Reply counts per posted question are stored per group, along with each responder's user id and display name and the posted question text — used to show the group its own engagement and, for Pro, to build the end-of-day digest.
- The bot never reads or stores what a member actually writes in their reply — only that they replied.
Santa Draw @SantaDrawProBot
- Participants, their drawn match, and any wishlist text sent with /wish are stored per exchange, per group, so matches can be delivered and wishlists forwarded to the right Santa.
- This data is kept until the exchange date plus 30 days, then deleted automatically; the organizer can also run /santa end to remove it sooner.
- Matches are only ever sent privately by DM to each participant — the group chat never sees who has who, and only members who've started a private chat with the bot can be matched.
Trivia Daily @TriviaDailyProBot
- The bot stores each member's correct-answer counts and current/best streak per group (
answers,members), read from Telegram's own quiz poll results, to build /leaderboard and streak badges. - The weekly leaderboard reads a rolling range of recent answers; Pro's champion post covers a roughly 28-day window from an internal day counter, not a calendar month.
- No answer content beyond Telegram's own poll results is stored — the bot doesn't see or keep anything members type outside of tapping a poll option.
Tick My Price @TickMyPriceBot
- The bot stores your watchlist coins and your alert lines (coin, direction, target price) per user, so it can answer /watchlist and check alerts.
- When an alert fires it is marked as sent and removed — the bot messages you once per alert, never repeatedly.
- Prices come from the CoinGecko public API and are cached for a minute; no wallet addresses or balances are ever requested.
My Hold Folio @MyHoldFolioBot
- The bot stores only what you log: coin symbols, quantities, and optional cost prices, keyed to your user id.
- In groups the bot stores nothing for /folio — it tells you to DM it — and /val prices what you ask without saving it.
- No wallet addresses, keys, or exchange connections are ever requested: you type what you hold and the bot prices it.
Join Approve @JoinApproveProBot
- For each chat the bot serves it stores the chat id, title and type, the mode (auto or paused), the welcome text and button you set, the approval delay, the Pro status and the id of the person who added the bot.
- For each join request it stores the chat, the requester's Telegram id and private chat id, the time, the result (approved, held, failed or no rights) and whether the welcome message was sent. A request held by the Pro delay is kept until it is approved.
- The bot keeps a count of welcome messages per chat per minute for its limit of 20 a minute, totals as counters, and the link tag a user first arrived from, such as site. The only other text it stores is a message you send with /paysupport.
Spy Party @SpyPartyProBot
- For each round the bot stores the group id, the host, the players who joined (Telegram id, display name, language), the role of each player, the votes and the result.
- The bot sends the secret place and the role in a private message. It posts no role in the group before the reveal.
Group Gate @GroupGateProBot
- For each group the bot stores the id, title, whether the check is on, the Pro status, the welcome text and button you set, the member count and the id of the person who added the bot.
- While a check is open it stores the group, the new member's Telegram id, the id of the card message and the time limit. It also stores the time each member joined, so that the filter knows who joined less than 24 hours ago.
- The link filter of Pro groups is the only part that looks at message text. It checks messages of members who joined less than 24 hours ago and does not store the text.
- Payment-help messages you send are stored as text. The bot also keeps totals as counters and the link tag a user first arrived from, such as site.
Giveaway Draw @GiveawayDrawProBot
- For each giveaway the bot stores the creator's Telegram id, the chat id, title and username, the prize text, the number of winners, the deadline, the secret seed and its hash, the status and the result.
- For each participant it stores the Telegram id, the display name and the time of joining. With bonus tickets it also stores the personal invite code of each participant and who invited whom.
- It stores the wizard answers while you create a giveaway, the Pro status of a chat, totals as counters and the link tag a user first arrived from, such as site.
Mafia Night @MafiaNightProBot
- For each group the bot stores the id, title, the Pro status and its end date, who added the bot and the time of the last game.
- For the game in progress it stores one record: the host, the players (Telegram id, display name, language), each player's role, the night choices and the votes. A timer closes a game after 3 hours at most.
- Reports and payment-help messages you send are stored as text. The bot also keeps totals as counters and the link tag a user first arrived from, such as site.
Daily Tarot @DailyTarotGroupBot
- For each user the bot stores the Telegram id, language, whether the daily card is on and at which hour, the days on which you drew a card, and your current and best streak.
- For each reading you buy it stores the kind (3-card spread or Celtic Cross), the payment charge id and the time. The cards of a reading are not stored.
- For each group it stores the id, title, language, Pro status and the daily post setting. The tables hold no message text from the group.
- Reports you send are stored as text. The bot also keeps totals as counters and the link tag a user first arrived from, such as site.
Truth Dare Friends @TruthDareFriendsBot
- For each group the bot stores the id, title, the pack in use, whether the game is off, the Pro status and who added the bot.
- For a round it stores who started it, the players who joined (Telegram id, display name, language), whose turn it is and which prompts were already used.
- Your own truths and dares are stored as text for the group that wrote them. The bot also stores whether it can write to a player in private.
- Reports you send are stored as text. The bot also keeps totals as counters and the link tag a user first arrived from, such as site.
Subgate @MostLikelyToProBot
- The bot stores group and channel IDs, channel links, settings and Pro status. It keeps membership check results and records of members it restricted so it can check again and lift its own restrictions.
- It also stores source tags and counters. Payment support messages you send to the bot are stored as text. It doesn't store the contents of ordinary group messages in its group tables.
Group Shield @WordRaceGroupBot
- The bot stores group settings and Pro status, allowed domains and blocked words. It records member IDs and message timestamps for flood checks, along with its own mutes and temporary exemptions.
- It also stores source tags and counters. Payment support messages are stored as text. Ordinary group message contents aren't saved in the group tables.
For Tiny Telegram Tools, Which One Are You, Charades Party, Who Knows Me Best, Crush Check, we do not have a full data list on this site yet. Ask us and we will tell you what they store.
Your choices
- Stop a bot at any time: open the chat with the bot and tap “Stop bot”, or remove the bot from your group.
- Ask what a bot stores about you, or ask us to delete it. Write to the contact below and include the bot name.
- If you live in the EU, the UK or another place with data protection law, you have the rights that law gives you. We will answer your request.
Contact
AddThisBot and the bots are run by Zovo. Email support@zovo.one or message us on Telegram.
If we change this policy, we change the date at the top of this page.
Try any bot free. Pay only if you want Pro.
Pro is paid in Telegram Stars inside the bot. Each bot page shows Free vs Pro.