Skip to content

Legal

Privacy policy

We explain clearly what data we process when you visit tghub.co, create an account and run campaigns — why we process it, how long we keep it and how you can exercise your rights.

Effective date: September 29, 2026Reading time: about 12 min
Contents
  1. At a glance
  2. 1.Scope and data controller
  3. 2.Data we collect
  4. 3.Why we process your data and on what legal basis
  5. 4.Cookies and browser storage
  6. 5.Who we share data with
  7. 6.Who can access the data
  8. 7.Retention periods
  9. 8.Security
  10. 9.Your rights
  11. 10.Children's privacy
  12. 11.Changes to this policy
  13. 12.Contact

At a glance

  • We do not use third-party analytics tools, advertising pixels or fingerprinting; visit statistics are kept only in our own database.
  • Visit records are deleted automatically after 180 days, password reset requests after 90 days and support messages after 2 years.
  • Your password is stored only as an irreversible hash; we will never ask you for it.
  • We do not sell your personal data or use it for third-party advertising.
  • The names, links and IDs of the groups in our network are never published on the site; only aggregate figures are shown.

1.Scope and data controller

This policy applies to the public pages of tghub.co (all language versions), the member dashboard and the support form. In this policy, “tghub”, “we”, “us” and “our” refer to the party that operates the tghub.co website and member dashboard, and “you” and “your” refer to any person who visits the site or uses the service.

tghub is the data controller for your personal data. To contact us or request information about the business, please use the Support page.

Cryptomus, which you use for payments, and Telegram, where your posts are forwarded, are governed by their own privacy policies with respect to their services.

2.Data we collect

We collect only the data we need to provide, secure and improve the service. The list below is the complete set of data our system actually records today.

2.1Visit information (all visitors)

We keep one record for each page view on our public pages and in the member dashboard:

InformationDetails
Visitor IDA randomly generated ID that is not derived from your device, stored in the tghub_vid cookie.
Time and pageWhen the page was viewed and its address (without the query string; record IDs in the member dashboard are masked).
IP address and countryYour country is taken from the country code that our content delivery provider, Cloudflare, adds to the request.
Device and browserDevice type (mobile, tablet, desktop), browser and operating system family, and your browser's identification string (User-Agent, up to 400 characters).
Language and screenThe site language shown and your screen size (for example, 390×844).
Referral sourceThe address of the external site that referred you (recorded only on the first page of a visit; search terms are not stored) and the campaign tags in the link (utm_source, utm_medium, utm_campaign).
Automated traffic flagRecords identified as coming from search engine bots or other automated tools are flagged and excluded from statistics.
Account linkYour account, if you are logged in. When you sign up, your earlier visits from the same browser are also linked to your account.

Admin pages and background requests are not included in these records.

2.2Account information

  • What you provide: email address, username, password (stored only as an irreversible bcrypt hash), optional Telegram username and full name, and the time you accepted the Terms of use and this Privacy policy.
  • Recorded automatically at sign-up: IP address, country, device, browser and operating system, browser identification string, site language and visitor ID, plus the referral source, the first page you opened and the campaign tags from your first visit.
  • On each login: login time, IP address, country and site language. While you use the site, your last-seen time is updated at most once every 5 minutes.
  • Optional short survey (you can skip it): what you want to promote, your monthly budget range and how you heard about us.
  • Preferred language: the site language you signed up or last logged in with, or the language you last chose in the member dashboard, is saved to your account so that the dashboard is shown in your language.

2.3Balance, payment and campaign information

  • Your balance (USD) and every balance transaction: type, amount, resulting balance and description.
  • Payment records: amount, status, the provider's transaction ID, the payment page link and the notification data Cryptomus sends to confirm the payment (for example, the amount and cryptocurrency paid, the network, the sending wallet address and the blockchain transaction ID).
  • Your campaigns: post link (and backup post link, if any), post title, package and duration, price breakdown, network size and estimates at the start, status and dates.
  • A summary of your post's content: content type, whether it has a link preview, text length, and the number of links, hashtags and emoji. We use this summary to determine which groups your post can be forwarded to.
  • The Telegram view counts of the posts you check and of your campaign posts (at the time of the check and every day during the campaign).
  • The extra group links you add, and forwarding logs showing which groups your post was forwarded to each day, the result and, where applicable, the reason for any error.
  • Groups you add that are not in our network are added to our group catalog along with their publicly visible Telegram information (such as name, link, member count and group permissions); this information is not linked to your account.
  • Orders for other packages offered in the dashboard: package name, price, quantity, target (if any) and order status.

2.4Support messages

  • What you provide: name, email address, optional Telegram username, topic and message (up to 4,000 characters).
  • Recorded automatically: IP address, country, site language, the time the message was sent and, if you are logged in, your account.
  • Added by our team: the message's status (new, read, done), an internal note, and which admin handled it and when.

2.5Password reset requests

  • The account the request belongs to, the time of the request, IP address and language; who created the link (you or our support team), its expiry and when it was used.
  • The reset link itself is not stored; only an irreversible hash of it (SHA-256) is kept. Each link can be used only once, and a new link invalidates any older ones.
  • Our site does not send automatic emails: your request is reviewed by our support team, and once your identity has been verified, the link is sent through your registered contact channel (for example, Telegram).

3.Why we process your data and on what legal basis

We process your personal data only for the purposes below and on the stated legal bases (Article 6 of the EU General Data Protection Regulation (GDPR), where it applies, and the equivalent provisions of other applicable data protection laws):

PurposeDataLegal basis
Providing your account and the service: login, campaigns, balance, responding to support requestsAccount, campaign and payment information; support messagesEntering into and performing a contract
Security and abuse prevention: detecting multiple or abusive accounts, rate limits, payment disputes, account recoveryIP address, country, device information, visitor ID, login information, reset requestsLegitimate interests (security of the service and of other users)
Understanding and improving the site: which pages, languages and devices are used, and where sign-ups come fromVisit information, sign-up source, survey answersLegitimate interests (first-party, pseudonymous and aggregated statistics only)
Proving acceptance of our termsThe time you accepted the termsLegal obligation and legitimate interests
Accounting and legal obligationsPayment and balance recordsLegal obligation

We do not sell your personal data or use it for third-party advertising, and we do not make automated decisions about you that produce legal effects.

4.Cookies and browser storage

We use only the first-party cookies listed below. We do not set third-party cookies, and we use no advertising or tracking cookies.

CookiePurposeDurationType
tgp_sessionRecognizes your login session (signed; cannot be read by scripts in the browser).7 daysStrictly necessary
tghub_vidRandom visitor ID: first-party visit statistics and sign-up source (cannot be read by scripts in the browser).1 yearStatistics (first-party)
tghub_localeThe language you chose in the site or member dashboard language switcher.1 yearPreference
tghub_tzYour device's time zone, so that dates in the member dashboard are shown in your local time.1 yearPreference
tghub_lang_hintRemembers that you dismissed the language suggestion bar.1 yearPreference
tgl-themeThe light or dark theme of the member dashboard.1 yearPreference

In the member dashboard, some interface information (for example, when you last viewed your notifications) is kept only in your browser's local storage (localStorage) and is not sent to our server.

You can delete or block cookies in your browser settings. Without the session cookie, you cannot log in; if other cookies are blocked, the site will keep working but will not remember your preferences.

5.Who we share data with

We share your data only in the following cases, where this is necessary to provide the service, and only to the extent required:

  • Cloudflare (content delivery and security network): all traffic to the site, including your IP address, passes through Cloudflare for content delivery and protection against attacks. We take your country from the country code Cloudflare adds to the request; we do not send your IP address to any other service for location lookups.
  • Cryptomus (payments): your top-ups are processed by Cryptomus. To create an invoice, the top-up amount and a transaction ID are sent to Cryptomus; the details you enter on the payment page are processed by Cryptomus.
  • Telegram: your campaign post is forwarded to groups on Telegram and is visible to their members; post and group checks are carried out through Telegram. When you open a post preview in the member dashboard, it loads from Telegram's embedded view (t.me) and your browser connects to Telegram directly.
  • Competent authorities: when there is a binding request that complies with applicable law, and only to the extent required.

Your data is stored in a database on our own server. Cloudflare and Cryptomus may process data outside your country. The site has no advertising pixels, third-party analytics tools or social media trackers; fonts are served from our own server.

6.Who can access the data

  • Only tghub administrators can access your data, through the admin panel and only as their duties require (support, security, statistics); administrative actions require an administrator session.
  • The public site shows only aggregate network figures (groups, members, online) and anonymized examples. No visitor's data is published, and neither are group names, links or IDs.

7.Retention periods

DataRetention period
Visit records180 days, then deleted automatically.
Password reset requests90 days, then deleted automatically.
Support messages2 years (730 days), then deleted automatically. You can ask us to delete them sooner.
Account, campaign and order informationFor as long as your account exists; deleted when your account is deleted.
Payment and balance recordsFor as long as accounting and tax laws require.
Post checks not tied to a campaignThe link to the post you checked, its view count and the time of the check are kept separately and are not deleted automatically with your account; we delete them on request.

8.Security

  • Passwords are stored as bcrypt hashes; reset links are kept only as hashes.
  • The session cookie is signed, and your account permissions are verified against our database on every request.
  • Failed login attempts, sign-ups and form submissions are subject to time-based rate limits.
  • Payment confirmations are verified with the payment provider's signature before anything is added to your balance; the same payment cannot be credited twice.
  • The connection between the site and your browser is encrypted with HTTPS.

No system is entirely risk-free. If we become aware of a security breach affecting your data, we will make the notifications required by applicable law.

9.Your rights

Under this policy and applicable data protection laws, including the GDPR where it applies, you have the right to:

  • find out whether we process your data and request a copy of it;
  • request the correction of inaccurate or incomplete data;
  • request the deletion of your data or the restriction of its processing;
  • object to processing based on legitimate interests (for example, visit statistics);
  • receive your data in a portable format, where applicable;
  • lodge a complaint with a data protection authority, in particular the one in the country where you live.

9.1How to exercise your rights

  • In the member dashboard, you can view and update your profile information, change your password and review your balance, order and campaign records.
  • For any other request, use the form on the Support page, preferably with the email address registered to your account. We may ask for additional information to confirm that the request is yours.
  • We respond to requests within a reasonable time and in any case within 30 days.
  • There is no self-service account deletion button in the dashboard; deletion requests are handled manually by our support team. When your account is deleted, your password reset requests are deleted; your visit records and support messages are unlinked from your account and deleted at the end of the retention periods above.

10.Children's privacy

Our service is not intended for anyone under 18, and we do not knowingly collect personal data from children. If we become aware of such data, we delete it.

11.Changes to this policy

We update this policy as our service or the way we process data changes. The current version takes effect as soon as it is published on this page; the effective date is shown at the top of the page.

12.Contact

For privacy questions and requests, use the form on the Support page and choose “Privacy & data request” as the topic.

Back to topEffective date: September 29, 2026

Have a question?

If you have any questions or requests about this document, you can use the form on our support page.

Go to the support page