Scope
This policy applies to gettgapi.com and the dedicated website support bot @GetTGAPIComBot. Updated October 2, 2026.
Application data
We process access-code balances, required phone numbers, developer portal codes, temporary cookies and application results. We do not log into the Telegram client, read chats or collect two-step verification passwords. Portal verification still requires temporary server-side processing of sensitive data.
API result retention and deletion
Results are encrypted in the server's memory filesystem for temporary delivery for up to 30 minutes. They are not written to the database or backups. After copying, confirm deletion in the dialog, or use Delete result to remove the copy early. It is cleared automatically at expiry.
Keep your own copy: historical retrieval is unavailable. Balances and necessary operation records remain. Deleting a copy does not revoke your Telegram API credentials or return a consumed use.
Temporary portal data is cleared after completion or safe termination. Uncertain applications retain necessary context for a bounded reconciliation period. Clearing local cookies does not revoke authorization on Telegram's servers.
Support chats
Website support opens a dedicated Telegram bot. Telegram forwards the text, images, voice notes, videos, files and payment evidence you voluntarily send, and administrators reply through the management app. We also process Telegram user and chat identifiers, display names, usernames and available profile photos to identify chats, respond, manually verify payment and deliver access codes.
Support text, attachments and cached profile data are encrypted at rest. Management access requires authentication and encrypted transport. Telegram bots are not Secret Chats: the full customer-to-administrator path is not end-to-end encrypted. Administrator notifications use Firebase Cloud Messaging and contain generic alerts and chat identifiers, not message text, attachments or payment evidence.
Individual messages and attachments remain online for 30 days. Cached names and avatars are retained for up to 30 days after the last update or related chat activity. These contents are then cleared. Chat identifiers, timestamps, handling status and necessary operation records are retained separately. Encrypted backups rotate within 30 days, so older copies may briefly remain after online deletion.
Aggregate public page analytics
We count views and button clicks on public pages such as the home page, guides and help, grouped by date, page, source category and action. This helps us evaluate our content. Analytics do not set tracking cookies, create visitor profiles or record complete referrer URLs, search terms, phone numbers, access codes, verification codes, API results or support content.
Application, access-code verification and management pages are excluded. Public pages respect Do Not Track and Global Privacy Control. Only the last 90 days of aggregates are displayed; older data is cleared periodically. Security rate limiting still processes necessary network information, but raw IP addresses are not stored in the analytics table.
Your language choice is saved in this browser's local storage so later visits can use the same language. You can change it in the header or clear browser storage to reset it.
Third parties and payment
Telegram delivers bot messages and WeChat processes appreciation-code payments. Their own privacy rules also apply. Provide only information needed to verify payment; hide unrelated balances and contacts. Never send verification codes, two-step passwords or API Hash in support chats.
Access and deletion requests
Contact @GetTGAPIComBot to request access, correction or deletion. We verify the relevant chat and scope to protect your data. Our deletion does not remove copies held by Telegram, WeChat or your devices.
Keep your own API credentials
Finish in the browser where you started and save your results. An access code validates remaining uses; it cannot access historical applications from another browser. Code-issuing staff cannot read API results. Saving and deletion steps