1. Who we are
The Telegram bot @MinutesNetworkAcceleratorBot ("the bot") is operated by Minutes Network FZ-LLC, Compass Building, Al Hulaila Industrial Zone-FZ, Ras Al Khaimah, United Arab Emirates, License No. 47016932 ("Minutes Network", "we", "us"). It is part of the Minutes Network Accelerator. This policy covers what the bot handles inside Telegram. Your Accelerator account, orders, payments, payouts and identity checks are covered by our main Privacy Policy at https://minutesnetwork.io/accelerator/privacy, which also applies.
Telegram's own privacy policy governs Telegram itself. We receive only what Telegram gives bots, described below.
2. What the bot receives and keeps
Your Telegram identity: your Telegram user id (which is also the id of your private chat with the bot), your first name, your username if you have one, and the language your Telegram app is set to. We keep these to know which chat to reply to and, when you connect an account, whose figures to show.
The connection to your account: if you sign in or connect from the portal, we keep which Accelerator account your chat is connected to, when it was connected, and your chat settings (time zone, daily summary time, quiet hours, which alerts you muted, and which reports you receive).
What you type, while a step needs it: for example the email address you sign in with, a one-time code, your name when you create an account, or your bank's transfer reference. The bot reads it, deletes your message from the chat, and keeps it only as long as that step needs (at most 20 minutes for a sign-in; a one-time code is stored only as a keyed hash and expires after 10 minutes). A record that a step timed out is kept for up to one day so the bot can explain it.
The bot's own messages: the message ids of cards the bot sent you, so it can update or tidy them, and a delivery log (message type, success or error) kept for 30 days to monitor the service.
Messages to our team: if you use "Message the team", your messages and any photo or PDF you attach are passed to our support team and kept with your support ticket, as for any support request.
Abuse prevention: to stop misuse (for example, someone guessing sign-in codes, sending codes to other people's addresses, or flooding our team), we count sign-in attempts, codes sent and messages to the team, and we keep a record when our team stops a chat from messaging them. These are kept under a keyed pseudonym (a salted one-way hash) of your Telegram user id or of the email address typed, never in clear, and only as long as each limit needs (at most two days for the counts). A stop placed by our team is kept until they lift it. We rely on our legitimate interest in keeping the service and its users safe.
Usage measurement: which steps of the bot are used (for example "started", "viewed a route", "connected an account"), which command or button was used and when (never what you typed), how long and how often you use the bot (sessions: runs of activity with no gap over 30 minutes), and which link brought you to the bot, recorded under a keyed pseudonym of your chat, never your Telegram id, to see where people get stuck and whether they come back. Our team can see this per chat, alongside the account a chat is connected to. Button response times are measured without any identifier.
Messages the bot could not understand: when you type something outside a step that the bot cannot answer, we may keep it for up to 90 days to help us improve the bot. We remove obvious personal details before storing it.
Errors: if something goes wrong while the bot handles your message or button, or a message to you cannot be delivered, we record where it happened, the technical error and a short reference that the bot shows you, so our team can find and fix it.
The live monitor (Mini App): when you open it, Telegram passes signed launch data that proves which Telegram user opened it; we check it and issue a short-lived session that shows only your own account's figures.
We never read other chats, never use the bot in groups for customers, and never show anyone's figures in shared or forwarded cards: a route you share from the bot carries only public route information.
3. Identity checks
Before capacity goes live, the law requires us to verify your identity. The bot never asks for, receives or stores identity documents or selfies. It gives you a one-time link that opens our identity verification provider's secure panel inside Telegram; the check runs there, and the provider handles your documents under our main Privacy Policy. The bot only learns the outcome (verified, in review, or not completed) so it can tell you.
4. Payments
Purchases made in the bot use the same checkout as the website, under our Terms of Sale. Payout requests made in the bot follow the same rules as the portal, are confirmed with a one-time code, and are only ever paid to payout details already saved on your account. The bot shows the payment details for your own order: a cryptocurrency address unique to it, or our bank details and a payment reference. We record the payment references you give us and the transactions we detect. Cryptocurrency transactions are recorded on public blockchains, visible to anyone by design; bank transfers pass through the banking system. The bot never asks for card numbers, passwords or wallet recovery phrases, and our team will never ask for them. Only pay to addresses shown in the bot's own chat or on your portal order page.
5. Why we use this data
To provide the service you ask for in the bot (information, signing in, buying, alerts and reports), to meet legal obligations (identity, anti-money-laundering and sanctions checks, record keeping), to keep accounts safe (for example, we email you when a Telegram chat is connected to your account, and tell a chat when it is disconnected), and to improve the bot using the measurements described above. We do not sell personal data. The bot may send occasional news and updates about the Accelerator, and new route announcements if you ask for them. You can switch these off at any time in Settings > Notifications, or with the Stop button on any update. Alerts about your own account, orders and payouts are part of the service and are not marketing.
6. Who we share it with
The same categories of service providers as our main Privacy Policy, only as needed: hosting, email delivery, identity verification, electronic signature, and our support tools; and authorities where the law requires it. Telegram, as the platform, carries every message between you and the bot.
7. How long we keep it
Bot data lives only as long as it is useful: sign-in steps up to 20 minutes (plus one day to explain a timeout), one-time codes 10 minutes, abuse-prevention counts (pseudonymous) up to two days, a stop placed by our team until it is lifted, update and delivery logs up to 30 days, response-time measurements 14 days, messages the bot did not understand and error records 90 days, the record of which commands and buttons were used 120 days, usage measurements (the bot steps described above) 13 months, session summaries (when and how long, never content) 400 days, and your chat connection and settings until you disconnect or delete them. Account, order, payment and verification records follow the retention periods in our main Privacy Policy.
8. Your choices and rights
Delete my Telegram data: send /privacy (or open Settings > Privacy and account) and choose "Delete my Telegram data". After you confirm, the bot removes everything it holds about your chat: the connection to your account, your chat settings, sign-in steps and codes, its message records and delivery log, usage measurements, sessions, error records and messages the bot did not understand from your chat, and the Telegram side of your conversations with our team. If you wrote to our team without being signed in, the web copy of those conversations and any files you sent are deleted too; conversations held under your account stay with your account's support history. It also deletes its recent messages from the chat. Two things are kept, because they protect the service and identify no one on their own: the pseudonymous abuse-prevention counts above, and, if our team stopped your chat from messaging them, that stop (under a pseudonym of your Telegram user id), so deleting your data does not lift it. Your account's own security records (for example sign-in attempts, payout confirmations and when a chat was connected) stay with your account as account records; they refer to your chat only by that pseudonym, never by your Telegram id or username. Your account, orders, payouts and identity records are not affected; to close your account or exercise your other rights over account data, contact us.
Disconnect: send /stop, or use Settings > Privacy and account > Disconnect this chat.
Block the bot: blocking the bot disconnects the chat automatically.
Requests by email: accelerator@minutesnetwork.io. We reply within 30 days.
9. Security
Buttons in the bot are signed so they only work in your own chat, for your own account. One-time codes and session tokens are stored only as keyed hashes. When your password is reset or changed, you sign out everywhere, or your email changes, the bot disconnects your chat and ends its live-monitor sessions, and tells the chat once; sign in again to reconnect. Identity-check links work once, and only in the browser that started the check. Your own typed messages are deleted from the chat once read. Access to data is restricted and audit-logged.
10. Changes
We may update this policy; the date above shows the latest version, and material changes are announced in the bot or the portal.
11. Contact
Minutes Network FZ-LLC, Compass Building, Al Hulaila Industrial Zone-FZ, Ras Al Khaimah, United Arab Emirates. accelerator@minutesnetwork.io