Privacy Policy

In short

AdminHub is a platform that runs inside Telegram. We collect the minimum data needed to operate: your Telegram user identifier and workspace settings. We don't store card data — payments in your shop flow directly through your bot in Telegram. When you pay AdminHub itself by card in the browser version, you enter the card on the payment page of Whop, our payment processor; we do not receive your card number or security code.

What we collect

When you open AdminHub as a Mini App in Telegram, we receive initData from Telegram — your user_id, first name, username and interface language. We keep this user_id to link you to your workspace. If you reached AdminHub through an ad or a tagged link that led to our site, we also keep the click ID and campaign tags of that link with your account (see “Cookies and analytics”).

Channel and bot data: channel IDs, subscriber info (their Telegram ID, name, username and subscription status), bot settings, product catalog, subscription configuration.

Operational logs: API request facts, moderation events, broadcast delivery records, the workspace operations log (payment and report events). Server logs and error reports are kept for a limited period. Moderation events, operations log entries and broadcast delivery records are deleted after 12 months, and the message text saved in a moderation event after 30 days; the only exception is the recipient list of a broadcast that has not gone out yet, which is kept until the broadcast is sent or canceled. Used for debugging and support.

Browser-version purchases (card payments through Whop): we keep the order (workspace, the Telegram account that placed it, kind of purchase: a Pro plan or a credit pack, amount, status, dates), the identifiers of the Whop payment, checkout and subscription, the payment, tax and refund amounts, and the moment you confirmed that you want to start right away together with the version of that confirmation text. From Whop's payment notifications we keep a trimmed copy: identifiers, status, amounts, currency and dates, plus technical marks (such as the billing reason, the decline code and whether the subscription is set to end). Names, email addresses, phone numbers, addresses and card details (such as the card brand and the last four digits) in those notifications are not kept.

What we DON'T collect

We do not receive bank card numbers, security codes or bank account numbers, and we do not store card data: if a payment notification carries details such as the card brand and the last four digits, we do not keep them. We never ask for your Telegram password. The only password we keep is the app password you create in Bluesky for cross-posting: it is stored encrypted and deleted when you disconnect that account. Of the posts in your channels, we keep only two kinds: posts that go through AdminHub (the ones you write, import or schedule here, including those an AI agent creates) and, while cross-posting is on for a channel, copies of its new posts, kept for 30 days so they can be sent on to the networks you chose. In a channel's discussion group, we also keep the first 500 characters of a message that a moderation rule catches or that someone reports with /report, along with the Telegram ID of the author (and of the reporter, for a report); the text is deleted after 30 days, the rest of the record after 12 months. Telegram Stars and card payments flow through Telegram and the payment provider — from them we only receive the payment status. In the browser version, a card payment to AdminHub itself goes through Whop: you enter the card on Whop's payment page, and from the payment we keep identifiers, amounts, status, dates and a few technical marks, but no card data (see “What we collect”).

How we use data

The data is used for: (1) running the service — showing your channels and settings, (2) security — protecting against abuse, (3) support — investigating incidents, (4) measuring our own advertising — whether an ad led to a sign-up or a purchase (see “Cookies and analytics”). We never sell your data or use your workspace data to target ads. Besides Telegram itself, we share it only with services that run AdminHub on our behalf, such as hosting, AI models, product analytics, error tracking, advertising measurement and payment processing (in the browser version, Whop receives the data needed to process a card payment and handles it under its own privacy policy, https://whop.com/privacy/), and with services you connect yourself, such as an AI agent (see “AI agents (MCP)”) or Bluesky and Mastodon for cross-posting.

Where data is stored

Data is stored on cloud servers in EU/US regions. Production database access is limited to platform engineers via secure channels. Backups are encrypted.

Your rights

You can request an export or deletion of your data at any time. To delete — disconnect the bot from all channels and message us via Telegram. We'll remove the data within 30 days, except for what we're legally required to retain.

Cookies and analytics

The landing page runs product analytics and advertising tags from Google and Whop. They use cookies and localStorage (the Whop tag also uses a browser fingerprint) to tell new visits from returning ones and to measure how our ads perform. The Google tag is also used for remarketing: Google can add visitors to audience lists, so that our ads can be shown to them again. The Whop tag is set not to pick up names, emails or phone numbers from form fields or the address bar. Google and Whop handle what their tags collect under their own privacy policies; we do not sell this data. To limit this, turn off ad personalisation in your Google account's ad settings, or block cookies, local storage and trackers in your browser.

The landing page may also set a cookie of its own, ah_entry. While we split visitors between the browser version and the Telegram Mini App, it records which of the two the buttons on the page that open the app lead you to — web for the browser version, tg for the Telegram Mini App — so you see the same buttons on every visit. The cookie applies to adminhub.tools and all its subdomains and lasts 90 days from your latest visit, and the page keeps a copy of the same value in your browser's local storage. It is set only while some, but not all, visitors are being sent to the browser version. The landing page's analytics events also carry this choice.

If you reach the site through an ad or another tagged link — one with a click ID (gclid, wbraid or gbraid) or campaign tags (utm_…) — the page sends them to our server as soon as it loads, together with the page you landed on, the page you came from and your browser's User-Agent (browser and device type). The page stores a random key for this record in your browser and reuses it for 30 days. When you open the bot or the Mini App with one of the buttons on the landing page, we save the click ID and tags with your Telegram account and in your profile in our analytics service, to see which ads lead to sign-ups. If a click ID was saved, then when you connect a bot or pay for Pro, we report it to Google Ads through the analytics service — the click ID, the time and a monetary value — so that Google can credit the ad. These records are kept until your data is deleted at your request (see “Your rights”).

In the Mini App we also collect product analytics and session recordings — which screens were opened and what was tapped — to find the places where the interface gets in the way. For workspace owners and their team members this data is linked to their Telegram ID. Recordings hide the contents of input fields, including the post editor, as well as the names, contacts and messages of your buyers and subscribers in orders, bookings, requests, the “People” section and support chats. The analytics and recordings are processed by an external service on our behalf; they are never sold and never shared with third parties for their own advertising. Telegram's sign-in data (initData) is stripped on your device before any analytics is sent.

AI agents (MCP)

You can connect an AI agent — an assistant or app that supports the Model Context Protocol (MCP) — to your workspace, with a Telegram sign-in or with a key from Settings → AI agents (MCP). From the agent we receive its calls to AdminHub's tools and their parameters, such as a post's text, the channel, the publishing time or a link to an image. Your conversation with the agent itself does not reach us.

In reply, the agent gets what it asks for: your workspace, channels, posts and their statistics, and your subscribers' names, usernames, Telegram IDs and subscription details. How much a subscriber has paid is included only when the agent explicitly asks for it. We send this data only to the agent you connected; from then on, it is handled by the company that provides the agent, under its own privacy policy — so connect only agents you trust.

Posts an agent creates or edits are stored in your workspace just like the ones you write yourself. To attach an image, AdminHub downloads it from the link the agent provides, sends it once to your private chat with your bot so that Telegram issues a file ID, and then deletes that message: we keep the file ID and the link, not the image itself. For each connection we store its name, permissions, and the dates it was created and last used; a key or a long-lived sign-in token is stored only as a one-way hash, so it cannot be shown again. Product analytics counts the agent's actions, such as “post created”, without their content.

To revoke access, open Settings → AI agents (MCP) and remove the connection or delete the key — access stops immediately. Posts the agent created stay in your workspace until they are deleted, and published ones also stay in your channels; connection records are kept until your data is deleted at your request (see “Your rights”). Like any request, the agent's requests pass through our server logs and error reports, which are kept for a limited time.

Changes to this policy

If the policy changes materially, we'll notify you inside the Mini App. The last-updated date is shown at the top of this page.