What happens to data

This page describes what the tgadsmcp.com site collects, and what happens to the data of people who sign in to the dashboard. Revision of 2026-10-12.

What the site collects

An access log on our server: the address a request came from, the time, the page requested, the browser type, and the referring page when the browser sends one. It goes to the server's system journal and lives by its rotation.

A lang cookie - it remembers the page language you chose, for a year, so the next visit does not have to guess it again.

Two traffic counters: Yandex Metrica and Google Analytics. They count how many people arrive, where from, and what they read: which pages were opened, how far they scrolled, which links they clicked. Each sets its own cookies - Metrica's start with _ym_, Google's with _ga - and uses them to tell a returning visitor from a new one. Google keeps event data for 14 months and then deletes it; Metrica keeps it under its own terms.

What the site does not do

It does not record what you do on the page. Metrica's session replay - mouse movement, clicks, field entry - is switched off, and that is visible in the counter code on any page.

It carries no advertising pixels and builds no advertising audiences. Only analytics is connected on Google's side; advertising features are not enabled, and no ad-network domains appear on the pages. We do not sell data, do not hand it to advertising systems and do not profile anyone with it.

And nothing beyond the named reaches the pages. That is a check rather than a promise: the build enumerates every external address the browser is sent to and knows exactly two - the counters. A third fails the build instead of passing unnoticed.

What the dashboard takes

Signing in goes through Telegram, and from it we receive the account identifier and the display name. Separately you give an email address - it is there so access does not vanish with your Telegram account and so there is somewhere to write about payment. The third thing is your ad account's API key: you issue it yourself in Telegram Ads and connect it here. It never leaves Telegram Ads - no messages, no contacts, no Telegram sign-in. An ordinary key opens the account it was issued in; an agency key reaches the accounts that agency opened, which is why you pick the accounts yourself in the dashboard.

The key is revoked in Telegram Ads with one button, and that button does not ask us: after a revocation we stop answering for that account, and neither we nor you can bring the access back - a new key is issued on the same screen.

Who else is involved

Requests to the site pass through Cloudflare, which holds the connection and the protection, and reach our server. Sign-in goes through Telegram. You choose the plan in the dashboard and connect your Telegram Ads accounts there, and the payment itself is made on OxaPay's page - the payment details stay with them: we hold no wallet or card numbers. Each of the three sees exactly what its part needs, under its own terms.

How to ask, and how to demand

Write to us on Telegram - that is our contact channel. Deleting dashboard data, taking a copy of it, or withdrawing consent starts there too.

How this page changes

It carries a revision date, and the date moves with the text. If we start collecting anything else - a counter, a form, another payment route - it appears here in the same release as the build itself: the page's revision comes from the same source as the sitemap, so the two cannot drift apart.