Telegram RegisterThe public register of Telegram
Telegram profile photo for Б-152: защита персональных данных

Channel

Б-152: защита персональных данных

@b152privacy

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Telegram's recommendations · Cite this entry

8,806subscribers

+229 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001557264977
TypeChannel
Username@b152privacy
Created13 January 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live27 September 2026
Measurements held15
Confirmed unchanged1 time, most recently 27 September 2026
On Telegramt.me/b152privacy

Topic

Job listings — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 11 September 2026 and assigned it the closest of 31 fixed categories, at 90% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

8,5738,8068,689.56 August 2026 — 8,577 subscribers6 August 2026 — 8,577 subscribers7 August 2026 — 8,573 subscribers9 August 2026 — 8,575 subscribers12 August 2026 — 8,577 subscribers19 August 2026 — 8,586 subscribers23 August 2026 — 8,608 subscribers25 August 2026 — 8,684 subscribers29 August 2026 — 8,729 subscribers1 September 2026 — 8,739 subscribers5 September 2026 — 8,755 subscribers10 September 2026 — 8,778 subscribers13 September 2026 — 8,795 subscribers18 September 2026 — 8,797 subscribers27 September 2026 — 8,806 subscribers6 August 202627 September 2026
15 measurements spanning 52 days, net +229. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 8,538–8,841 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
27 Sept 2026, 02:168,806+9
18 Sept 2026, 06:188,797+2
13 Sept 2026, 18:218,795+17
10 Sept 2026, 07:208,778+23
5 Sept 2026, 00:188,755+16
1 Sept 2026, 09:268,739+10
29 Aug 2026, 03:038,729+45
25 Aug 2026, 16:138,684+76
23 Aug 2026, 02:348,608+22
19 Aug 2026, 14:568,586+9
12 Aug 2026, 22:148,577+2
9 Aug 2026, 22:238,575+2
7 Aug 2026, 06:308,573-4
6 Aug 2026, 10:188,577no change
6 Aug 2026, 09:598,577first reading

Engagement

56 posts held, back to 24 July 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 26 pages of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 56 posts for this entry, the most recent from 28 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
10s
Average length
10s

Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.

Reaction mix

568 reactions across 52 posts, in 10 distinct kinds. The most used accounts for 30.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤17330.5%
custom 522194744179584017616128.3%
custom 54386246678185391139516.7%
👏8214.4%
🤔264.58%
custom 5438539112070002676172.99%
😱81.41%
👎40.704%
💯10.176%
😁10.176%

Custom emoji. 3 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 52 of the 56 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 568 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 56 most recent posts we hold, published 24 July 2026 to 28 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

28 Aug 2026, 14:45 UTC268 views2 reactionsread 28 August 2026
Photo

Новая подборка вакансий уже здесь. Без громких обещаний, просто интересные предложения от компаний нашей отрасли: 🔃 Специалист по работе с персональными данными (DPO) в Группа Компаний Мечел 🔃 Специалист по внутреннему контролю за обработкой персональных данных в ASKONA 🔃 Руководитель направления по информационной безопасности и защите персональных данных в JENTY 🔃 Юрист по защите данных (DPO) в ООО Октафарма-Фармим…

custom 52219474417958401762

28 Aug 2026, 09:31 UTC486 views2 reactionsread 28 August 2026
Photo

✅ Спасибо всем, кто был с нами сегодня! Запись пришлем всем зарегистрированным. За годы аудитов в Б-152 мы видим одни и те же ошибки у ответственных за персональные данные. Независимо от отрасли и размера компании. 1️⃣Переход к продвинутым практикам без базового аудита Компания уходит с согласия на законный интерес, ставит амбициозные цели по зрелости процессов, а базовой диагностики того, что происходит на самом д…

custom 52219474417958401762

28 Aug 2026, 07:05 UTC616 views2 reactionsread 28 August 2026

🚨 Встречаемся сегодня в 11:00 Почему бизнес боится проверок РКН больше утечек, и во сколько это обходится? На вебинаре разберем реальные кейсы проверок и судебную практику: где компании ошибаются, какие вопросы возникают у регулятора и как подготовиться к профвизиту и контролю сайта. 👉 Подключайтесь в 11:00: https://us02web.zoom.us/j/83596377576 Запись будет отправлена всем зарегистрированным участникам. Поддер…

custom 52219474417958401762

27 Aug 2026, 13:02 UTC883 views5 reactionsread 28 August 2026
File

⚡️ФСТЭК разъяснила переход на новые требования защиты ПДн: внеплановая оценка потребуется не всем Мы получили официальный ответ ФСТЭК России на вопросы о переходе с действующего приказа № 21 на новый состав организационных и технических мер по обеспечению безопасности персональных данных. В нем сразу несколько важных разъяснений для операторов ПДн. 1️⃣Есть действующий документ об оценке эффективности, внепланово п…

👏4custom 52219474417958401761

27 Aug 2026, 10:27 UTC919 views23 reactionsread 28 August 2026

Коллеги, приносим извинения за доставленные неудобства. Мы приняли решение провести завтра вебинар повторно. 28 августа (пятница) в 11:00 Тема и спикер остаются прежними. Ссылку пришлем в канал за 1 час до мероприятия!

custom 522194744179584017610❤5🤔5custom 54386246678185391133

27 Aug 2026, 08:00 UTC932 views7 reactionsread 28 August 2026

🚨 Встречаемся сегодня в 12:00! Почему бизнес боится проверок РКН больше утечек, и во сколько это обходится? На вебинаре расскажем про реальные кейсы проверок и судебной практики 2026: где компании ошибаются, какие вопросы возникают у регулятора и сколько в итоге это стоит бизнесу 👉Подключайтесь в 12.00: https://my.mts-link.ru/j/b152/23437017241 Поддержка Запись будет отправлена! 😎

custom 52219474417958401763🤔2👏1custom 54386246678185391131

26 Aug 2026, 11:18 UTC882 views6 reactionsread 28 August 2026
Photo

С КАКОГО ЭТАПА НАЧИНАТЬ ИМЕННО НАМ? Главный вопрос после вебинара по приказу №117 📄 На вебинаре по приказу №117 и изменениям порядка аттестации этот вопрос звучал чаще других. И это закономерно: у организаций совершенно разные исходные точки. У кого-то еще не определено, на какие информационные системы распространяются требования. У кого-то меры защиты уже внедрены, но не хватает подтверждений их реализации. Кто-то…

custom 54386246678185391133❤2🤔1

26 Aug 2026, 06:48 UTC816 views8 reactionsread 28 August 2026
Video

Уже завтра! Вебинар «Почему бизнес боится проверок РКН больше утечек и во сколько это обходится»🔥 «Документы в персональных данных это только верхушка айсберга» — Максим Лагутин, СЕО Б-152 и член рабочих групп Роскомнадзора по ЦАО и ГРЧЦ, объясняет, почему компании с полным пакетом документов все равно получают претензии на проверках. Разберем: ➡️как изменился подход РКН к проверкам в 2026 году: от контроля доку…

👏4custom 52219474417958401762❤1🤔1

25 Aug 2026, 11:51 UTC875 views9 reactionsread 28 August 2026

Posted without readable text

🤔4custom 52219474417958401763❤1😱1

25 Aug 2026, 08:03 UTC923 views9 reactionsread 28 August 2026

Сегодня вебинар по приказу ФСТЭК №117 📄 Начинаем в 12:00 МСК. За полтора часа разберем путь от определения применимости требований до аттестационных испытаний и последующего контроля. Будет полезно и тем, кто только начинает подготовку, и тем, у кого часть мер уже реализована или аттестат получен. Отдельно обсудим изменения порядка аттестации с 1 сентября. Регистрация еще открыта 🔥 😎

custom 52219474417958401764❤1👎1👏1🤔1custom 54386246678185391131

25 Aug 2026, 06:34 UTC937 views16 reactionsread 28 August 2026
File

Конспект второй части Дня открытых дверей. Первая часть тут https://t.me/b152privacy/2688 Описали все ответы регулятора на вопросы, которые были заданы перед началом мероприятия, а также во время него. Распределили по темам, чтобы все ответы и комментарии были в одном месте сразу. 😎

❤5👏5custom 52219474417958401763custom 54385391120700026763

Showing the 12 most recent of 56 posts we hold for @b152privacy. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

Posts edited after publishing

@b152privacy edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
24 August 2026
Most recent edit
24 August 2026

Mentions

Named by 3 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

Names

Channels on the register whose handles appear in this channel's posts.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

Privacy Advocates
@prv_adv · 21,918
Telegram ranks this channel #4 of 98 here — alongside 97 others — read 22 September 2026
РоскомнадZор
@rkn_tg · 63,811
Telegram ranks this channel #9 of 96 here — alongside 95 others — read 21 August 2026
Клуб правообладателей
@bchlaw · 27,259
Telegram ranks this channel #30 of 91 here — alongside 90 others — read 13 September 2026
Об ЭП и УЦ
@ep_uc · 21,240
Telegram ranks this channel #32 of 97 here — alongside 96 others — read 24 September 2026
СУДЕБНАЯ ПРАКТИКА IP и IT
@sudpraktik_IPIT_demo · 22,966
Telegram ranks this channel #44 of 89 here — alongside 88 others — read 19 September 2026

This channel appears in 5 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

Cite this entry

A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 27 September 2026 — this entry's latest reading, not the date you are reading this.

“Б-152: защита персональных данных” (@b152privacy), 8,806 subscribers as measured 27 September 2026. Telegram Register, tgregister.com/channel/b152privacy.

Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.