Terms of Service

Version of September 27, 2026
Seller: Zion Tools LLC, Belize, Email: support@zion.tools, Telegram: @zion_tools

1. Subject

The Seller provides the User with access to the Zion Tools online service (the “Service”), a set of tools for working with Telegram. The Service consists of modules:

Forwarding: automatic forwarding or copying of messages between Telegram chats the User has access to, with filters and text replacement, and to webhook addresses the User specifies (Discord, Slack, the MAX messenger, own address).
Alerts: Telegram notifications about messages in selected chats that contain a given text and amount, and to webhook addresses the User specifies (Discord, Slack, the MAX messenger, own address).
Validator: detection of repeated messages using the User’s template and a “Duplicate found” reply; the Service can also report duplicates to webhook addresses the User specifies.
Receipt scanner: AI recognition of the amount, fee and currency on receipt images and PDF files, and keeping a running total; at the User’s choice, receipt details are also sent to the User’s webhook addresses.
Bookkeeping: tracking amounts by the User’s categories in the dashboard and via a Telegram bot, category shares and an AI forecast of amounts for 30 days based on the account’s entries; at the User’s choice, entries are also sent to the User’s webhook addresses. The AI forecast is an indicative estimate based on past entries, and the User makes any decisions based on it at their own discretion.
Transaction analytics: tracking incoming and outgoing transactions from bank notifications in the User’s chat.
AML check: risk assessment of a crypto wallet address and audit of a token contract based on open data sources, with a report in the dashboard, in the Telegram bot and as a PDF.
P2P exchange: a marketplace for exchanging USDT for national currencies between Users, with ads, deals with the seller’s USDT locked for the duration of the deal (deal guarantee), a deal chat and dispute resolution by the Service’s support.
VoIP number: a temporary virtual phone number in a country chosen by the User for receiving an SMS verification code from a third-party service; the number and SMS are provided by the number provider SMSFAST.
Staking: a service under which the User places part of their USD balance within the Service and earns income at the rate shown in the “Staking” section.
Webhooks & API: API keys with which the User’s programs receive data from their dashboard and perform the actions allowed by the key (messages from Telegram accounts, Bookkeeping entries, AML checks), and incoming webhooks (URLs where a request makes the Service send a Telegram message or add a Bookkeeping entry). Top-ups, withdrawals, staking and plan changes are not available via the API.
Multi-accounting: chats of all the User’s connected Telegram accounts in one dashboard window, with reading, sending, forwarding and other actions with messages on behalf of these accounts. Works only through the proxy assigned to the account. The Service does not store messages; they are loaded from Telegram each time. It also covers the account profile (name, @username, bio), stories, creating groups and channels, clearing history, search by @username, GIFs, voice messages, Telegram gifts, chat folders, privacy settings, blocking users and the account’s list of devices (sessions) with the option to end a session. The User changes these settings in Telegram itself through the dashboard and is responsible for their consequences. An account PIN locks its chats in the dashboard and works only within the Service. Gifts are paid with Telegram Stars from the User’s account balance: Telegram makes the charge, the Seller receives no money for gifts and does not refund spent Stars. The Seller does not sell Stars: the User buys them in the Telegram app or on Fragment, and the dashboard only opens the Fragment page. There are no calls in the dashboard.
Neurocommenting: comments under new posts in channels and replies to members’ messages in groups chosen by the User, on behalf of the User’s Telegram account; the comment text is written by artificial intelligence in the style set by the User, with a pause and no more often than the hourly limit. Works only through the proxy assigned to the account.

Modules work through the Telegram account connected by the User and/or through the Service’s Telegram bots, depending on the module and the chosen settings. The list and description of modules are given on the website. In addition, the Service provides proxies for Telegram accounts (section 6), a Telegram notification bot for dashboard events (top-ups, plan, accounts, deals, sign-ins and more; the User chooses what to receive), which also delivers confirmations: the password reset link and confirmation codes; the Service does not send emails, a support chat in the dashboard (the headset icon in the header) and accepts requests for improvements (“Request a feature”), including new modules: requests are reviewed free of charge, and the Seller decides whether and when to build them.

Forwarding, Multi-accounting, Neurocommenting and VoIP number are the core products and are available in the dashboard right away. The other modules are add-ons: the User installs them in the “Modules” section of the dashboard and can disable or remove them at any time. An installed module appears in the dashboard menu; a removed module disappears from the menu, while its data and settings are kept. A module with money still in use (P2P exchange deals and ads, an amount in Staking) cannot be removed until they are completed or withdrawn. A User who installed a module can rate it from 1 to 5 stars; the module catalog shows everyone the average rating and the number of users of each module, without names.

2. Registration and trial

Registration means full and unconditional acceptance of these terms. A new User receives a trial period whose length and limits are stated on the website. Paid add-ons are free during the trial if stated on the website.

An account can be created and accessed with an email and password or with a Google or Telegram account. The first sign-in with such an account creates a dashboard; if a dashboard with the same email confirmed by Google already exists, the sign-in is connected to it. The email is not confirmed: it serves as the sign-in login. A dashboard created with Telegram works without an email; one can be added in Settings → Profile. The Service sends the password reset link to the notification bot connected to the dashboard; if the bot is not connected, access is restored by signing in with Google or Telegram, if connected, or through support. Sign-in services are connected and disconnected in Settings → Security; the sign-in protection enabled there also applies to them. The User is responsible for keeping access to their Google or Telegram account secure.

The trial is provided once. A Telegram account connected to a profile is tied to it and cannot be connected to another profile, including after it is removed from the profile. Creating additional profiles to get the trial again is prohibited.

3. Pricing and payment

In the dashboard the User chooses one of the plans: VIP or Custom. The contents, limits and prices of the plans are stated on the website and in the dashboard.
The VIP plan includes the number of Telegram accounts and source chats and the set of modules stated on the website, plus a quota of Receipt scanner recognitions and Neurocommenting comments for every 30 days. VIP is paid upfront for the chosen term: 1, 3, 6 or 12 months (a month is 30 days); terms of 3, 6 and 12 months come with a discount stated on the website and in the dashboard. At the end of the term VIP renews automatically from the balance for the same term, or for 1 month if the balance does not cover the whole term. The term of the next renewal can be changed in the dashboard; the term already paid for does not change and is not recalculated. Modules not included in VIP cannot be added to it; this requires the Custom plan. Receipt scanner and Neurocommenting beyond the VIP quota are paid per use; prices are stated on the website. A paid VIP plan cannot be purchased again until its paid period ends.
Switching from the Custom plan to VIP takes effect immediately and is charged at the full VIP price for the chosen term; Custom plan days already paid for are not refunded or credited. Switching from VIP to the Custom plan takes effect at the end of the paid period; the paid period is not refunded.
The Start, Lite and Optima plans are no longer provided from 29 October 2026. A User who had paid for such a plan gets VIP at no extra cost until the end of the paid period, and after it the Custom plan with the accounts and sources already connected.
The Custom plan is billed daily: the base part (number of Telegram accounts and source chats) and the paid Multi-accounting add-on. The charge is made from the balance at the start of each day; an add-on enabled in the middle of a paid day is charged for the current day right away. Accounts that are offline at the time of the charge, and source chats read only by them, are not charged on the Custom plan; if an account comes back online the same day, the difference is charged.
The receipt scanner is billed for each successfully recognized image or PDF file at the price stated on the website, after the free recognitions and the VIP quota are used up. If no amount is recognized, nothing is charged. Adding amounts manually is free.
Neurocommenting is billed for each comment sent at the price stated on the website, after the free comments and the VIP quota are used up. Skipped comments (ads, giveaways, the hourly limit, a sending error) are not charged.
A proxy for an account is paid for every 30 days at the price stated on the website, on any plan (section 6).
Transaction analytics, Alerts, Validator, Bookkeeping and AML check are free with any plan, including the trial; the User only needs to install them in the “Modules” section. The number of AML checks per day is limited; the limit is shown in the dashboard. The AML check Telegram bot without a dashboard gives the number of free checks stated in the bot.
A VoIP number is billed per number at a price that depends on the service and the country and is shown before purchase. The cost is charged to the balance on purchase. If no SMS with a code arrives within 20 minutes, the User cancels the number before the code arrives, or the provider does not issue a number, the cost is refunded to the balance. Once the code has arrived, the payment is not refunded. The number is single-use: the Seller does not guarantee that the number will be available later for re-verification.
Staking is free of charge. Only whole USD amounts can be staked, without cents. The staked amount is deducted from the balance and recorded separately; every 24 hours from the moment of each stake the Seller credits income on that stake at the annual rate (APY) shown in the dashboard, and the income is added to the staked amount. Each stake has its own 24-hour countdown; when part of the amount is returned, it is taken from the latest stakes first. The User may return all or part of the amount to the balance at any time with no fee; no income is credited on the returned part for an incomplete day. The rate and the minimum and maximum amounts are set by the Seller; a rate change applies from the next credit. Staking is not a bank deposit, is not insured and is not an investment service; income is credited only to the internal balance of the Service and is withdrawn on general terms. In case of a breach of these terms, including abuse, the Seller may suspend credits.
P2P exchange: there is no subscription fee; the Service fee is the percentage of each completed deal stated on the website, charged to the seller. Releasing USDT in a deal requires confirmation: a passkey, a trading password or the account password and, if enabled, a Google Authenticator code.
USDT withdrawals from the balance are made on the User’s request to the TRON (TRC20) address they specify, not less than the minimum amount and minus the network fee stated on the website; requests are processed manually. The User may restrict withdrawals to addresses on their whitelist. Withdrawing USDT requires confirmation: a passkey, a trading password or the account password and, if enabled, a Google Authenticator code.
Prices and the balance are stated in US dollars (USD). Payment is made in advance to the balance; with cryptocurrency on the TRON network (TRC20) the balance is topped up at 1:1, and a payment is credited after network confirmation.
Refund of unused balance: submit a written request to the support address support@zion.tools. Requests are processed within 14 banking days. The refund is issued in full, without any hidden or additional fees.
If the balance is insufficient, paid services are paused until the balance is topped up; the User’s settings and data are kept. Disabling an add-on does not refund days already paid.
The Seller may change prices by notifying the User on the website; new prices apply to subsequent charges.

4. Referral program

The User may invite new users with a personal link and receive a reward on the balance equal to the percentage shown in the dashboard of the amounts charged to their balance for the Service's modules and services. Self-referrals and sign-ups from the same IP address are not counted. The reward can be used to pay for the Service or withdrawn to the User's crypto wallet in the same way as other balance funds.

5. User obligations

Connect only the User’s own Telegram accounts and use the Service only in chats where the User is entitled to read and process messages and whose members do not object to such processing.
Not use the Service to send spam, distribute illegal content, or violate copyright or Telegram’s rules.
Not use Multi-accounting or other modules for mass mailings, messages to strangers, or advertising without consent. One account can send no more than 30 messages per minute; in case of mass mailings or complaints the Seller may limit sending or disable the module without refunding paid days.
Neurocommenting posts comments on behalf of the User’s account only in channels and groups the User has selected (including those found by keyword search; the search runs through Telegram on behalf of the User’s account, and the Service doesn’t store the queries), no more often than the limit the User has set (no more than 20 per hour). Comments are written by AI; the User is responsible for their content, the choice of channels and groups and compliance with their rules and Telegram’s. The fee is charged for each comment sent and isn’t refunded if a channel or group admin deletes the comment or Telegram restricts the account.
The User uses VoIP numbers only lawfully and in accordance with the rules of the services where they sign up or confirm a login: the User is responsible for complying with those rules, for the consequences of signing up (including restrictions or bans of accounts by third-party services) and for the use of the accounts obtained. Using numbers for fraud, mass sign-ups, bulk messaging, evading bans or impersonating others is prohibited; in case of a violation the Seller may restrict the module without refunding numbers already issued.
Not submit data whose processing is prohibited by law, and be responsible for the lawfulness of processing third-party data (for example, card numbers and amounts in messages).
Check the Service’s results independently: recognized amounts, detected duplicates, notifications and reports are for assistance only.
Specify webhook addresses only of the User’s own services or services the User is entitled to use, and be responsible for processing the data sent there; links to files are valid for 7 days while the account is connected. For MAX the User provides their own MAX bot token: the Service stores it and uses it only to send messages to the chosen chat; the User is responsible for the bot and its chats and can reissue the token via @MasterBot.
Keep API keys and incoming webhook URLs secret: the Service executes a request with a key or to a webhook URL as an action of the User themselves. In case of a leak the User deletes the key or issues a new webhook URL in “Webhooks & API”; the User is responsible for actions performed before that. Messages sent via the API and incoming webhooks on behalf of Telegram accounts follow the same rules as in Multi-accounting: no bulk messaging or messages to strangers, no more than 30 messages per minute per account. Paid actions via the API are charged the same as in the dashboard.
Keep the dashboard password safe.

6. Limitation of liability

The Service works through the official Telegram API and Bot API. The Seller is not responsible for restrictions imposed by Telegram on the User’s account, or for outages of Telegram and the TRON network.

Without a proxy, accounts connect to Telegram from the Service’s server IP address. A proxy is bought in the dashboard, or the User connects their own (SOCKS5 or HTTP); for Multi-accounting every account must have a proxy. The User is responsible for the operation, legality and reputation of their own proxy. Proxies are provided by a third-party supplier (Proxy6), the price for the stated period is charged from the balance and renewed from it automatically unless renewal is turned off; the paid period isn’t refunded when the account is deleted. If a proxy stops responding, Multi-accounting closes for that account and the other features temporarily work directly, without the proxy. The Seller is not responsible for proxy outages caused by the supplier. The User may use the details of a purchased proxy (address, login, password) in their own browser and apps; sharing them with third parties and using the proxy for mass messaging, spam or unlawful actions is prohibited. The User changes the type of a purchased proxy (SOCKS5 or HTTP) in the dashboard.

Receipt recognition, amount detection in messages, duplicate detection and transaction tracking are performed automatically and may contain errors. The Seller is not responsible for decisions made by the User based on this data, including missed notifications, undetected or falsely detected duplicates and incorrectly recognized amounts.

AML check reports are compiled automatically from open sources (sanctions lists, address labels, blockchain data) at the time of the check, are informational only and are not a legal opinion, investment advice or a guarantee. The User makes decisions about transactions independently.

In the P2P exchange the Seller is not a party to deals between Users: Users settle the national-currency payment directly with each other, and the Service only locks the seller’s USDT until receipt of the money is confirmed. The buyer pays for the deal from their own card (account) within the set time and attaches a receipt; the seller releases the USDT only after the money arrives in their account. The buyer may cancel a deal; after three cancellations within 24 hours new deals are blocked for them for 24 hours, and a mutual cancellation accepted by the seller doesn’t count. A dispute (appeal) is reviewed by the Service’s support based on the materials in the deal chat: when an appeal is opened, each party sends a video from their banking app showing the deal details to the chat within 24 hours; support may send a party that hasn’t sent a video a final warning (in the deal chat and the notification bot) with an extra 3 hours. A party that doesn’t provide evidence or doesn’t reply to a support request in time may lose the dispute; support closes the deal in favour of one of the parties. The support decision is final within the Service. Fraud, forged documents, marking a payment as made without sending it and abuse of appeals may lead to restricted access to the P2P exchange and the dashboard. The User is responsible for complying with their country’s laws on currency and digital-asset exchange.

Privacy Policy

What data is processed

Dashboard: email (for a dashboard created with Telegram, once the User links one) and password hash, IP address at registration, time zone, top-up and charge history, referral program data. Profile, if the User fills it in: name, avatar, date of birth, phone, Telegram username. When signing in with Google or Telegram: the account identifier in that service, email (Google) and the name or username the service shares with the User’s consent; the Service never receives the passwords of these accounts.
Website visit statistics: the page viewed, time, the website the visitor came from, campaign tag, device type and country (determined from the IP address at the time of the visit). Instead of the IP address and browser data, an irreversible anonymized fingerprint is stored; our own statistics do not use cookies. Data is kept for 180 days. The public pages of the website (home page, module pages, blog, this document) run a Yandex Metrica counter, which sets its own cookies and collects anonymized visit statistics: the page, the referring source, device, browser, region, link follows and clicks; input recording (Webvisor) is turned off. There is no counter in the dashboard or on the sign-in and sign-up pages. You can opt out of Metrica by blocking cookies in your browser or installing a tracker blocker.
Website language: a Russian page opens in the visitor’s browser language: in English if the browser is set to English, in Uzbek if it is set to Uzbek, and in Russian otherwise. A language chosen with the language switcher is stored in the zt_lang cookie for one year and is not used for anything else.
Telegram account: phone number, name, profile photo, Telegram session key, the list of chats selected in the settings, the address and password of the proxy (current and saved) if one is connected. The Service doesn’t store Multi-accounting conversations; they are loaded from Telegram each time. The Telegram account ID and phone number are kept after the account is disconnected, so that the account cannot be connected to another profile (section 2). A Multi-accounting account PIN is stored only as a hash and can’t be read; the Service doesn’t store the device list, privacy settings or folders, which are loaded from Telegram each time. A voice message recorded in the browser is converted on the Service’s server and sent to Telegram right away; the Service doesn’t keep the recording.
“Request a feature” requests: the request text and the support reply.
Support chat: messages and files (screenshots, PDFs) the User sends to the support chat in the dashboard, support replies and read marks. Only the User and the Service’s administrators can see the conversation. The User is notified of a support reply in the notification bot if it is connected.
Module settings: forwarding routes, alert rules, validator templates, bookkeeping categories, chats connected to the Service’s bots, the list of installed modules and the ratings given to modules (other users see only the average rating and the number of users of a module).
Notification bot: the ID of the private Telegram chat connected to the dashboard, the name or @username of that Telegram account and the chosen events. Sign-in and security notifications, the password reset link and confirmation codes include the browser, system, IP address and country. Confirmation codes (the Telegram code) are stored only as a hash and are valid for 10 minutes. The bot can be disconnected in the dashboard or with the /stop command.
Message content (only to the extent a module needs it):
- Forwarding: messages are passed to recipient chats and are not stored. When forwarding to a webhook, the text, author, a link to the post and links to files are sent to the address the User specifies; the Service stores the webhook address, its secret and a log of recent deliveries (up to 100 entries per webhook) with the beginning of the message text.
- Alerts: the text of the triggering message, the detected amount and a link to the message are stored in the log; if the User selected a webhook, they are also sent to its address.
- Validator: field values from messages matching the template (for example, card number and amount) and message links are stored to detect repeats; the text of duplicate messages is stored in the log; if the User selected a webhook, the matched values, text and links are also sent to its address.
- Receipt scanner: the receipt image or PDF file is processed for recognition and not stored by the Service; the amount, fee, currency, time and the Telegram file ID (if the receipt was sent to the bot) are stored; if the User selected webhooks, the amount, currency, fee and account are also sent to their addresses.
- Neurocommenting: the selected channels and groups, campaign settings, the text of posts and messages commented on, the comment text and its status in the log. If the User selected the module’s webhooks, this data is also sent to their addresses.
- Bookkeeping: amounts and comments entered by the User; if the User selected webhooks, the entry (category, amount, comment, author, account) is also sent to their addresses. For the AI forecast, category names, currencies, dates and amounts of the account’s entries for the last 90 days (without comments or author names) are sent to an AI model.
- Transaction analytics: bank notification texts from the selected chat and the transactions extracted from them. If the User selected the module’s webhooks, this data is also sent to their addresses.
- AML check: checked addresses and their reports; for checks in the Telegram bot without an account, the Telegram user ID and the number of checks. If the User selected the module’s webhooks, this data is also sent to their addresses.
- VoIP number: issued numbers, the chosen country and service, received SMS and codes, the cost and status of each number.
- Staking: stakes, withdrawals and income credits with the amount and time of each operation.
- Webhooks & API: the name, access and hash of an API key (the key itself is not stored in plain form), the time and IP address of the last request with the key; for an incoming webhook, the URL, action, text template and a log of recent requests (up to 100 per webhook): time, sender IP address, the beginning of the text and the result.
- P2P exchange: nickname, ads and payment details, deals, messages and files in the deal chat (receipts, statements, banking-app videos), pre-deal messages, reviews, follows and blocks. Payment details are visible only to the other party of an open deal; the chat is visible to the deal parties and support.
- USDT withdrawals: the wallet address, the address whitelist and request history; security: passkey public keys, the trading password hash and the encrypted Google Authenticator secret (passwords and secrets are never stored in plain text).

How it is used

Data is used only to run the modules configured by the User, for billing and support. The Telegram session key is used only for actions the User has set up in the dashboard.

Sharing with third parties

Anthropic (Claude API) — receipt images are sent for amount recognition, and channel posts in Neurocommenting — to write a comment.
Telegram: to operate the account and the Service’s bots.
Anthropic (Claude API): receipt images are sent for amount recognition, channel posts and group messages in Neurocommenting are sent to write a comment, and category names, dates and amounts of Bookkeeping entries are sent for the AI forecast. [Check the provider’s data processing terms with a lawyer.]
TRON network: payments are public on the blockchain; the Service matches them to the balance by amount.
Cloudflare (Turnstile): on the login and sign-up pages, checks that the form is sent by a human; receives the IP address and browser data.
Proxy6: the proxy provider; when buying, the Seller receives the proxy address from it, no User data is passed to the provider. Traffic of a Telegram account using the proxy goes through the provider’s server.
SMSFAST (smsfast.io): the number provider for VoIP numbers; it receives the chosen country and service, issues the number and passes on the SMS it receives; no User data is passed to it.
Fragment (Telegram’s marketplace for buying Stars): the dashboard opens its page with the recipient’s @username and the number of Stars; no dashboard data is passed to it, and payment is made on Fragment itself.
Google Fonts: the site font is loaded from Google servers, which receive the visitor’s IP address.
Yandex Metrica (Yandex LLC): visit statistics for the public pages of the website: receives the IP address, browser and device data, the addresses of the pages viewed and actions on them; no dashboard data is passed to it. Metrica processes this data under its own terms; the Seller sees only anonymized reports. The Yandex search robot uses the counter’s visits to find new pages of the website.
Google and Telegram: when used to sign in, the User confirms the sign-in on the service’s page; the Service receives only the data listed above and does not share dashboard data with them.
AML check data sources (GoPlus Security, blockchain nodes and block explorers, CoinGecko): receive only the address being checked, with no User data.

Data is not shared with other third parties except as required by law.

Storage and deletion

Data is kept while the User’s dashboard exists. The User may at any time:

disconnect a Telegram account or a data source in the dashboard (the session key is deleted, and the collected data such as logs, transactions and receipts is kept in the dashboard or deleted with it, as the User chooses);
disconnect a chat from a bot, delete rules, templates, receipts, entries and periods;
clear the alert and validator logs, restart duplicate checking;
end the Service’s session in Telegram → Settings → Devices.

To delete the dashboard and all data, contact support: support@zion.tools