Last updated: 01/01/2026
This Privacy Policy (the "Policy") describes how tgbot.com, being the domain through which the Services are made available ("Us", "We", "Our"), collects, uses, discloses, retains, and otherwise processes information in connection with the Telegram-based trading bot and any related websites, dashboards, documentation, channels, and tools made available under tgbot.com (collectively, the "Services"). The Policy is incorporated into and should be read together with the Terms and Conditions available at tgbot.com/terms (the "Terms"). Capitalized terms not defined in the Policy have the meanings given in the Terms.
The Services operate primarily through Telegram. Telegram is a Third-Party Service and maintains its own privacy policy, terms, and technical constraints. The Policy governs only Our processing of information in connection with the Services and does not modify Telegram's relationship with You, the data Telegram independently collects, or how Telegram processes information. Your use of Telegram itself is governed by Telegram's own policies, and We do not control Telegram's independent collection and use of data.
By accessing, using, interacting with, or otherwise engaging with the Bot or Services in any manner, You acknowledge that You have read and understood the Policy. If You do not agree, You must immediately discontinue all use of the Services. The Policy may be updated from time to time, continued use after updates constitutes acceptance as described in the Terms.
1.1.1. The Policy describes how information may be processed in connection with operating, securing, supporting, improving, and enforcing the Services. It is not a promise that the Services are risk-free, uninterrupted, error-free, or suitable for any particular purpose. The Terms contain separate and additional risk disclosures, disclaimers, and limitations of liability that apply independently of the Policy.
1.1.2. If there is any conflict between the Policy and the Terms regarding personal data processing, the Policy governs that topic, however, nothing in the Policy is intended to create broader duties than those described here or those required by applicable law. Where mandatory local laws grant non-waivable rights, those rights apply to the extent required. Otherwise, the Terms and the Policy are intended to operate together as a single framework.
1.2.1. In the Policy, "Personal Data" means information relating to an identified or identifiable individual, or treated as personal data/personal information under applicable law. "Bot Data" means information generated through interactions with the Bot (commands, button presses, preferences, workflow states, and system outputs), together with operational logs and records associated with those interactions. "On-Chain Data" means information recorded on public blockchains (including wallet addresses, approvals/allowances, transaction hashes, token transfers, and related metadata), which may be public, persistent, and outside Our ability to modify, restrict, or delete.
1.2.2. "KYC Data" means identity verification and compliance screening information and outputs, which may include documents and verification results, sanctions/PEP screening, adverse-media checks, wallet screening, and related risk indicators, whether processed directly by Us or via Third-Party Services. "Third-Party Services" includes Telegram and any third-party platforms, protocols, infrastructure, hosting, analytics vendors, verification/KYC providers, payment processors, and blockchain infrastructure providers not controlled by Us.
1.3.1. Headings are for convenience only and do not affect interpretation. The Terms such as "including", "without limitation", and "such as" are illustrative and do not limit scope. The Policy applies worldwide to all Users and all use of the Services, subject to mandatory local law. The Policy describes how information may be processed, it does not guarantee that any particular processing will or will not occur in every case, since processing may depend on how You use the Services, which features are enabled, and operational and legal requirements at the relevant time.
2.1.1. The Bot generally processes information You provide through interactions with the Bot (commands, button presses, replies, settings) and the metadata Telegram makes available for bot functionality (such as your Telegram user ID, username/handle, language/locale signals, and certain chat context identifiers where applicable). This processing is necessary to identify your session, apply preferences, prevent abuse, and deliver outputs to the correct user or chat context.
2.1.2. The Bot does not inherently have access to your Telegram password, the content of your messages in other chats, or your phone number, except to the extent Telegram discloses certain information through platform features You choose to use or through platform behavior outside Our control. Telegram may independently collect, store, and process data under Telegram's own policies, the Policy does not control Telegram's independent processing.
2.1.3. Telegram delivery behavior can cause delays, missing messages, message ordering differences, and UI inconsistencies across devices. We may log delivery errors, timestamps, and interaction records to operate the Services, prevent abuse, and investigate incidents. We do not control Telegram's infrastructure and do not guarantee delivery, timing, or availability of Telegram.
2.2.1. The Services operate in a high-risk environment involving public blockchains, self-custody wallets, and third-party infrastructure. Some information that relates to Your use of the Services, particularly On-Chain Data, may be publicly visible and outside Our control. Linking your Telegram identifier to a wallet address may increase privacy risk by making activity more attributable.
2.2.2. You are responsible for safeguarding your Telegram account, device, and Wallet credentials. If your Telegram account is compromised, an attacker may interact with the Bot as if they were You. We may have limited ability to distinguish authorized from unauthorized activity, and certain activity (especially on-chain) may be irreversible.
2.2.3. The Policy describes data processing and does not reduce or replace the risk disclosures, disclaimers, and responsibility allocations in the Terms. The Terms remain the controlling document regarding risk, liability, and responsibility for trading activity.
3.1.1. You may provide information when using the Services, including your Telegram handle/ID, Bot settings and preferences, wallet addresses you submit or link, transaction-related parameters you input, support requests, reports, feedback, and communications. If You choose to contact Us, we may keep records of correspondence, including dates, content, and any identifiers necessary to address the request.
3.1.2. You may also choose to provide additional contact details such as an email address for notices, support, verification, or account-related workflows to the extent such workflows exist. You are not required to provide an email unless We request it for a specific feature, compliance step, risk-control step, or support case.
3.1.3. You MUST NOT send seed phrases, private keys, authentication codes, or similar secrets via Telegram or any channel. We do not need them and will not request them. If You share them anyway, You do so at Your own risk and acknowledge We may be unable to assist.
3.2.1. We may collect technical and usage information associated with operation and security of the Services, including timestamps, device/client metadata, approximate location inferred from IP (where applicable), crash reports, performance metrics, abuse-prevention signals, rate-limit events, and feature usage logs. Such information helps us maintain reliability, diagnose issues, prevent misuse, and improve the Services.
3.2.2. We may maintain records of Bot interactions (commands, button presses, workflow state changes, and system responses) to provide functionality such as session continuity, feature operation, activity views (where offered), debugging, fraud prevention, and dispute handling. These logs may contain identifiers (Telegram ID, wallet address) if necessary to tie the event to your session.
3.2.3. If You access web components under tgbot.com (landing pages, dashboards, documentation), we may collect browser information and use cookies or similar technologies for session management, security, and analytics as described in Section 9.
3.3.1. To provide trading-related workflows and outputs, we may process wallet addresses, transaction hashes, token addresses, approvals/allowances, routing metadata, slippage settings, and other parameters. Some of this information may be publicly visible on-chain and may be accessible to anyone via blockchain explorers or analytics.
3.3.2. We may associate an off-chain identifier (Telegram user ID/handle) with one or more wallet addresses you submit or link so the Services can function. You acknowledge that this association may increase privacy risk and that on-chain activity is typically traceable and persistent.
3.3.3. We do not request, store, or recover private keys or seed phrases as part of normal Services operation, and we do not custody funds (as stated in the Terms). Transaction signing occurs via your Wallet environment; however, we may store non-secret identifiers and logs necessary to operate or secure the Services.
3.4.1. As described in the Terms (including Section 2.5.5–2.5.6), We may request identity verification and/or compliance screening. In such cases, You may provide KYC Data directly to Us and/or to Third-Party Services used for verification, and we may receive verification outcomes and risk indicators.
3.4.2. KYC Data may include identity documents, selfies/liveness checks, proof of address, business information (KYB), and other documentation depending on the verification flow, together with outputs such as pass/fail decisions, risk flags, sanctions/PEP screening results, adverse-media indicators, and wallet screening risk signals. We may also re-run checks over time, request updated documents, or apply additional screening based on risk, legal requirements, operational needs, or changes in your usage patterns.
3.4.3. We may retain KYC-related records and outputs to the maximum extent permitted by law for compliance, audits, security, and dispute purposes, even after You stop using the Services, and even if access is restricted or terminated.
3.5.1. We may receive information from Third-Party Services that support the Services, such as infrastructure providers (security logs), analytics services (aggregated usage metrics), payment processors (subscription status), verification providers (KYC outputs), and blockchain infrastructure (network telemetry). We may combine such information with other information we hold to operate, secure, and improve the Services.
3.5.2. In order to read blockchain data, simulate routes, estimate fees, and broadcast transactions (where applicable), the Services may send requests to third-party remote procedure call providers, node operators, or endpoint providers ("RPC Providers"). RPC Providers may receive and process certain technical information as part of providing connectivity, which may include Your IP address (or network identifiers), user-agent/device metadata, wallet address queries, transaction payloads, transaction hashes, and timing data. RPC Providers operate as Third-Party Services under their own policies and practices. We do not control, endorse, or assume responsibility for how RPC Providers collect, use, retain, share, or secure information, and any interaction with an RPC Provider occurs at Your own risk to the maximum extent permitted by law.
3.5.3. Third-Party Services may collect information independently under their own policies. We do not control how they use your information when they act as separate controllers (for example, Telegram as a platform).
4.1.1. We use information to operate the Bot, provide features, maintain sessions, store settings, deliver outputs, and perform technical functions that allow the Services to work. This includes using Telegram identifiers to route messages and responses and using Bot Data to maintain feature state and workflow continuity.
4.1.2. We use logs and usage data to monitor performance, debug issues, detect outages, measure reliability, and improve usability and functionality over time. We may also use data to run internal testing, feature rollouts, and operational changes, including feature gating and phased releases.
4.1.3. We use communications and support requests to respond to inquiries, investigate issues, and maintain records for quality control, disputes, and enforcement of the Terms. Support is provided on a best-efforts basis as stated in the Terms and does not create any duty to resolve issues.
4.2.1. We use information to protect the Services and Users, including detecting and preventing abuse, spam, scraping, denial-of-service activity, attempted circumvention of controls, impersonation campaigns, and other harmful behavior. We may use security logs, rate limiting, anomaly detection, and other safeguards.
4.2.2. We may use automated signals (unusual usage patterns, repeated failed attempts, high-risk indicators) to impose limits, require additional verification, restrict access, or terminate access. Such systems may be imperfect and may result in false positives. To the maximum extent permitted by law, we are not obligated to disclose internal thresholds, scoring criteria, or details of our security systems.
4.2.3. We may preserve logs and relevant records to investigate misuse, respond to incidents, enforce the Terms, and defend against claims. We may also use information to coordinate with service providers and advisers during incident response.
4.3.1. We may use information to comply with legal obligations, respond to lawful requests, and enforce our policies and Terms. Where verification is requested under the Terms, we may process KYC Data and related outputs to determine eligibility, impose limits, and manage risk.
4.3.2. We may use verification outcomes to decide whether to provide Services, whether to provide particular features, and whether to apply limits, restrictions, or terminations consistent with the Terms. We may also re-run checks, request updates, or apply additional screening based on risk and compliance needs.
4.3.3. To the maximum extent permitted by law, verification requirements or outcomes do not create a duty for Us to monitor your activity, prevent losses, reverse transactions, or provide remediation, and we may make verification-related decisions in our sole discretion.
4.4.1. We may use information to send operational messages through the Bot (service notices, security alerts, feature changes, policy updates). If You provide an email, we may send notices by email as well, but Telegram delivery behavior may still affect timeliness and visibility of messages.
4.4.2. We may administer community channels and informational communications, including announcements and updates. We may process identifiers necessary to manage participation, prevent spam, and enforce community guidelines.
4.4.3. We may deliver in-product messages we believe are relevant (for example, changes to fees, features, risk warnings, or security guidance). Where required by applicable law, we may offer opt-outs for certain communications, but some communications may be necessary for operation and security.
4.5.1. We may use aggregated and/or de-identified information to analyze trends, administer the Services, study usage patterns, measure feature performance, and improve reliability. De-identification may reduce risk but may not be irreversible in all cases depending on data type and context.
4.5.2. We may use information to improve fraud prevention, develop security features, and test new workflows. Testing may occur in live environments. Any risk controls are best-effort and do not guarantee prevention of losses.
4.5.3. If You submit feedback, suggestions, ideas, bug reports, or other materials, processing and rights related to those submissions are addressed in the Terms (including ownership and license to use feedback).
5.1. Where applicable law requires a legal basis (for example, under GDPR-style regimes), we process Personal Data based on one or more of the following: performance of a contract (providing Services under the Terms), legitimate interests (security, fraud prevention, service improvement, enforcement), compliance with legal obligations, and consent (where required, typically for certain cookie categories or marketing).
5.2. The applicable legal basis depends on the purpose and data type. Some processing is necessary for operation and security and may not be optional if you wish to use the Services. Where processing is based on consent, You may withdraw consent, but withdrawal may limit functionality and does not affect processing already performed.
5.3. Some decisions may be influenced by automated signals (e.g., fraud heuristics, abuse signals, verification outcomes). To the maximum extent permitted by law, we may limit what we disclose about internal logic to protect the Services and Users and to prevent circumvention.
6.1. We may share information with service providers that support the Services, including hosting/infrastructure providers, analytics vendors, customer support tooling, security vendors, verification/KYC providers, communications services, and payment processors. We may share information on a need-to-know basis and use access controls and contractual restrictions where appropriate, but operational constraints may require broader access during incidents or investigations.
6.2. We may disclose information to law enforcement, regulators, courts, and other authorities in response to legal process, lawful requests, claims, subpoenas, court orders, or when necessary to protect rights, safety, and security of Us, Users, Third-Party Services, or the public. We may disclose information to professional advisers (legal, compliance, auditors) when necessary for risk management, investigations, dispute handling, or defense.
6.3. We may disclose or transfer information in connection with a corporate transaction, such as a sale, merger, consolidation, financing, reorganization, acquisition, asset sale, change of control, or (if applicable) bankruptcy or similar proceedings. You acknowledge that in such events information may be transferred to a successor operator, subject to applicable law and updated policies.
6.4. We do not sell Personal Data in the sense of selling user lists to third parties for their independent marketing. However, some jurisdictions define "sale" or "sharing" broadly, and we may use vendors and measurement tools to provide and improve the Services and to understand usage; jurisdiction-specific rights and opt-outs may apply depending on configuration and law.
7.1. We implement commercially reasonable technical and organizational measures designed to protect Personal Data from unauthorized access, use, disclosure, alteration, and destruction, including access controls, least-privilege permissions, monitoring, and incident response practices. Specific security measures may be confidential to preserve their effectiveness.
7.2. No security program can guarantee absolute security, especially given reliance on Third-Party Services and public blockchains. You are responsible for security of your Telegram account, devices, and Wallet. We cannot recover or restore lost private keys or seed phrases and cannot reverse on-chain transactions.
7.3. We may investigate suspected incidents, preserve logs, and take actions we deem necessary to protect the Services, including limiting or suspending access, rate limiting, disabling features, or other security measures. Where required by law, we may provide notice of certain security incidents through reasonable means (Bot notice, website posting, email), taking into account the nature of the incident and operational constraints.
8.1. We retain Personal Data for as long as reasonably necessary to fulfill purposes described in the Policy, comply with legal obligations, resolve disputes, enforce agreements, and maintain security. Retention periods vary depending on data type, risk context, operational needs, and legal requirements. Security logs and abuse-prevention records may be retained longer to detect recurring threats and support investigations.
8.2. Consistent with data minimization and security principles, logs and records related to specific trade execution, transaction routing, simulation, and technical request/response handling are generally minimized and are not intended to be retained permanently, except to the extent We reasonably determine retention is necessary for security, abuse prevention, incident investigation, compliance, audits, dispute handling, or enforcement of the Terms. Retention practices may vary based on risk level, system integrity needs, and legal obligations, and We may delete or aggregate such logs on a rolling basis.
8.3. KYC-related records and verification outputs may be retained as necessary for compliance, audits, security, and dispute handling, even after you stop using the Services, to the maximum extent permitted by law. We may also retain communications and operational logs to defend against claims and enforce Terms.
8.4. You represent that information You provide is accurate, complete, and not misleading, and You agree to keep it current where relevant. If inaccurate or incomplete information affects verification outcomes, compliance screening, or access decisions, We may restrict or terminate access consistent with the Terms.
9.1. Web components of the Services (including tgbot.com and any dashboards or documentation) may use cookies or similar technologies (session identifiers, analytics tags, local storage) to operate, maintain sessions, prevent abuse, and measure usage. Cookies may be session cookies or persistent cookies. Your browser may allow you to restrict or delete cookies, but doing so may limit functionality or prevent certain features from working.
9.2. We may use third-party analytics services to obtain statistical data, analyze trends, administer web components, and study navigation patterns. Where required by law, consent banners or preference tools may be provided. The Services may include embedded content (videos, images, articles) that behaves as if you visited the originating website and may collect data under that website's policies.
9.3. Telegram-based Bot interactions are separate from browser cookie systems, but linked websites, dashboards, and documentation may use such technologies. This section applies only where You access web components.
10.1. Depending on your jurisdiction, you may have rights to request access, correction, deletion, portability, restriction, or objection, and rights related to automated decision-making and profiling. We may require reasonable verification to process requests, including to prevent fraud and protect Users. We may refuse or limit requests to the extent permitted by law, including where retention is required for legal, security, compliance, or dispute reasons.
10.2. On-chain data is generally public and immutable. We cannot delete or modify blockchain records and cannot guarantee removal of on-chain traces, including wallet addresses and transaction history that may be visible through third-party explorers and analytics.
10.3. Requests should be submitted to: info@tgbot.com. Your request should include sufficient information to identify you, such as your Telegram handle/ID and, where relevant, wallet address(es). We may respond within a reasonable period subject to legal requirements and operational constraints, and we may request additional information.
11.1. The Services are not intended for individuals under 18. We do not knowingly process Personal Data of minors. If You believe a minor has provided information, contact info@tgbot.com. We may restrict or terminate access consistent with the Terms.
12.1. Your information may be processed and stored in multiple jurisdictions due to global infrastructure and Third-Party Services. Where required by law, we may rely on lawful mechanisms for cross-border transfers. You acknowledge that protections may differ between jurisdictions and that cross-border processing may be necessary to operate the Services.
12.2. By using the Services, You acknowledge and accept cross-border processing to the maximum extent permitted by applicable law.
13.1. We may amend, modify, supplement, or replace the Policy at any time in Our sole discretion. Any updated Policy becomes effective upon posting at tgbot.com or being presented through the Services, whichever occurs first. We may provide notice through the Bot, by posting, or by email if provided. Continued use after updates constitutes acceptance.
13.2. The Policy is intended to evolve with the Services, operational changes, legal developments, and industry practices.
14.1. To the maximum extent permitted by applicable law, the Policy (and any disputes arising out of or relating to the Policy) is governed by the laws of the Republic of Panama, without regard to conflict of laws principles, consistent with the Terms. Where mandatory local law grants non-waivable rights, those rights apply to the extent required. Nothing in the Policy is intended to waive non-waivable rights.
Domain: tgbot.com
Privacy Policy: tgbot.com/privacy
Data inquiries email: info@tgbot.com
Support email: info@tgbot.com