Introduction
Buzzio delivers. The developer’s server writes the replies.
Buzzio bots let third-party developers run assistants and room tools inside the app. You search a service bot and tap Start, or an admin installs a worker in an open-history group or Community. Buzzio moves events, enforces limits, and retains ordinary text for about 7 days. The developer’s webhook decides what the bot says.
We do not sell bot data. Never. Bot chat is still not sealed — Buzzio and the developer can read what you type while it is delivered.
Why Buzzio is best for bots
Two kinds, locked at create
Service (1:1, like Telegram bots) or Worker (rooms, like Discord bots) — chosen once in Forge, never converted.
Sealed surfaces stay sealed
No bots in private 1:1, Whisper private chat, Whisper Questions, or E2E groups. Hard product exclusion.
Honest not-E2E banner
Every bot and Forge chat shows that the developer’s server can receive what you type.
Short Buzzio retention
Ordinary bot text ~7 days on our servers, then purged. We are not a permanent bot inbox.
Opaque user ids
Developers get a bot-scoped bu_… id — not your Buzzio ID or @username — in webhook updates.
Forge on the phone
Create bots, rotate tokens, transfer ownership — seed never goes to developers.buzzio.dev.
Service vs Worker vs Forge
Service bot
- Search @…bot (handle ends in bot)
- Tap Start → 1:1 Bot badge chat
- User Starts; developer replies
- Not a silent room install
Worker bot
- Not in people search
- OHG / Community Bots tile
- Admin request → Console Accept
- Pending ≠ installed
Forge (@forge_bot) is Buzzio’s official control bot — labeled Official. Its brain runs on Buzzio, not a third-party webhook. Need both 1:1 and room jobs? Create two bots with separate tokens.
What you get
- Service bots
- Worker bots
- Forge (@forge_bot)
- Start flow
- ~7-day text retention
- Keyboards & polls
- Report / hide
- Bot API + Console
How it works
Chat with a service bot
Search @username
Handles end in bot. Draft, rejected, paused, or worker bots do not appear in people search.
Open the profile
Look for the Bot badge. Forge shows Official.
Tap Start
Same Buzzio button on every bot. Accept Bot Terms if prompted. Buzzio sends a platform /start to the developer.
Chat
Your text is delivered to their webhook so they can answer. Media they send is usually an HTTPS URL they host — your phone loads it from them.
A file you send to a bot may be stored by Buzzio (currently up to 2 MB) for about 7 days so the bot can fetch it by file_id. Buzzio does not download or host outbound bot media bytes — URL only.
Install a worker (admins)
Open Bots in the room
Open-history group or Community → Bots. Workers are not in people search.
Lookup @username
Pick OHG permission ticks or Community roles, then send a request.
Developer Accepts
On developers.buzzio.dev → Requests. Pending is not installed. Reject → bot never joins.
Room privacy label
After Accept, the room shows that a worker can read allowed messages. Platform /bots slash stays admin-only and is never forwarded to the worker.
Admins can use /bots, /bots list, /bots add, /bots remove, and /bots perm. Workers cannot receive Community administrator / manage_roles unless the installer explicitly grants those creator-controlled permissions. Sealed rooms never get workers.
Interactive UI in bot chats
Bot chats can show safe interactive controls: inline and reply keyboards, confirmable single- or multi-choice cards, regular / multi / quiz polls (including timed close), checklists, collapsible sections, developer-hosted media blocks, and action rows. Choice selection is saved before Confirm/Cancel; stale requests roll back instead of silently changing the card.
Payments, checkout, invoices, pay buttons, paid media, Stars, gifts, paid reactions, and subscriptions are permanently not offered in bot chats — those method names return 404.
Forge — developers on the phone
Search @forge_bot. Create on the phone (owner = Buzzio ID). Connect code on the desktop Console with the API token. Newly issued tokens show for about 5 minutes, then the Forge message vanishes — Buzzio stores only a hash.
/newbot
Display name → @username (must end in bot) → Service or Worker → API token once.
/mybots · /stats · /status
List bots, aggregate counts only (not other people’s profiles), and review state.
/token · api reset
Rotate the bot’s password. Old token dies; Console signs out for that bot.
/transferbot
Phone only. Receiver Accepts in Forge. Plan moves; 7-day cooldown before another transfer.
Also: /plan, /renew, /deletebot, /canceltransfer, /accepttransfer, /rejecttransfer, /help. Username rules: unique across people and bots; reserved prefixes such as buzzio_, forge_, support_ are blocked.
Bot lifecycle
Users can Start
- Approved + active plan — in search, Bot badge
Not Startable in search
- Draft / testing / submitted
- Rejected — fix webhook, submit again
- Shadow-banned (e.g. plan expired)
- Suspended (abuse) — offline
If the developer’s server is down, the bot is down. Forge stays up. Full HTTP surface: Bot API · Worker bots.
Privacy & safety
Honest encryption
Bot chats are not end-to-end encrypted. Zero-metadata claims for sealed 1:1 do not apply. Who can read your text: Buzzio (while retained) and the bot developer’s server. Worker events in open-history groups and Communities are also not E2E.
This chat is not end-to-end encrypted. The bot developer’s server can receive what you type.
Do not send recovery phrases, passwords, payment secrets, or anything you would not give that developer. Legal: Bot Terms · Bot Privacy.
What happens to your data
Message text
Buzzio keeps ~7 days, then deletes from our servers. The developer’s webhook copy is their job.
Bot → you media
Not downloaded or hosted by Buzzio — URL only. File stays on the developer’s HTTPS origin.
You → bot file
Stored up to 2 MB for ~7 days so the bot can fetch it. They may retain a download under their policy.
Pending updates
Webhook / getUpdates copies ~24 hours. Last ~100 delivery logs per bot for debug (may include text).
Scheduled messages
Held until sent or cancelled, up to 30 days.
Local bubbles
May remain on your phone until you clear the chat. Reinstalling only restores text still within our window.
Report snapshots may keep recent text for safety review past the 7-day window. Deleting Buzzio’s copy does not wipe the developer’s disk.
Safety & honest ceilings
- Report works on bot chats the same job as 1:1 — hide, pause, suspend, or delete a bot; act on the owner’s Buzzio ID
- Developers must not use bots for scams, CSAM, phishing, or other Bot Terms violations
- Bot premium and bot commerce are permanently not offered — membership flags, payments, Stars, and related methods return 404
- Workers only act after Console Accept and only with granted permissions
- Selling something on the developer’s own website is their merchant relationship — not a Buzzio unlock
Tips
- Never send your 12-word phrase or passwords to a bot or Forge
- Treat every bot as cloud shared — read the not-E2E banner
- For sealed chat, use 1:1, Whisper, or E2E groups — bots cannot go there
- Admins: wait for developer Accept before assuming a worker is live
- Developers: rotate leaked tokens in Forge; create separate Service and Worker bots
Ready to use or build bots?
Download Buzzio to Start approved service bots, or open Forge and the developer Console to create and connect your own.