Your privacy matters.

This page explains the data used in the directory and what happens when a community connects the bot.

Your account data

When you create an account, you provide a name, email address and password. The password is stored as a hash, not as plain text. A session identifies your access so you can save favorites, register communities and manage authorized features.

Public community information

The directory stores the username, when available, name, description, category, tags, language, optional location and rules supplied with the registration. Approved registrations are available on the web and may appear in search engines.

For private communities, activation by a verified administrator authorizes publication of the name, photo, description, member count, invitation and compatible new messages. The group stays private on Telegram and the bot's invitation requires approval to join. The AdultTelegramGroup page is public and may be indexed by search engines. Private community invitations are not published without this authorization.

Telegram connection

When you add the bot as an administrator or send /ativar in the group, it checks your Telegram permissions. This action authorizes registration and display of new messages on the site. For private communities, it also authorizes publication of the invitation and requires Invite users permission. We store the identifiers needed to verify administration, record authorization and operate the integration, together with its status and collected member counts. If the permissions of the person who added the bot cannot be confirmed, automatic publication stays disabled.

Linking a site account is optional for managing the community through the dashboard. Verification associates a Telegram identity with the account and checks its current permissions. Registration through the bot requires authorization from a verified administrator.

After activation, compatible new messages and media received by the bot may be stored and displayed publicly. Administrators must inform group participants about this republication before activation. The identity of group message authors is hidden by default, but a message's text may contain personal information included by its author.

Protected content is not republished. The directory does not create public message links for private groups or display the Telegram identifiers of the people who authorized the integration.

Optional Telegram account connection

You can connect an account you control to also receive messages sent by other bots. Access requires a Telegram login and individual authorization for each community you administer. Collection starts with new messages after authorization, follows the publication filters and does not track later edits or deletions through this connection.

The access session is encrypted on the server. Login codes and two-step verification passwords are not stored. We keep your Telegram identity, masked phone number, authorizations and operational records needed for the connection. Photos and videos published through this integration are stored in the database and may be included in service backups.

Disconnecting deletes the saved session and stops collection. You can also revoke the session under Settings → Devices in Telegram. Disconnecting does not remove posts already received; use the dashboard or request a review through the contact channel to remove them.

Posts, edits and removal

The integration cannot freely import history from before the connection. Edits may be updated when the bot receives them. Telegram does not provide a general deletion event for ordinary messages, so deleting a message in the app does not guarantee its removal from the directory. The responsible administrator can remove it through the dashboard, and anyone can submit a report on the community page.

Directory metrics

We record visits and clicks per community to provide statistics. The service uses a derived identifier to reduce repeated counts on the same day. These are site metrics: they do not identify Telegram members or confirm that someone joined a group.

Cookies, preferences and advertising

The site uses a session cookie for authentication and a cookie to remember the selected language. A theme preference may be stored in the browser. Account, favorites and administration features need these resources to operate. Advertising spaces may display identified banners or third-party code isolated in frames. Those providers may process data when their content loads; the operator must assess their practices before enabling them and provide any disclosures or choices required for the installation.

How information is used and accessed

Data is used to maintain accounts, organize the directory, verify permissions, synchronize authorized content, prevent abuse and support moderation. Service administrators have operational access to the information needed for these tasks. The integration communicates with Telegram's API; opening an external link takes you to another service with its own rules.

Requests about your data

You may request clarification, corrections, content removal or a review of data deletion through the contact channel. Identify the resource or account concerned, without sending passwords or login codes. You may need to demonstrate your relationship to the data so the request can be handled correctly.

Records required for security, moderation or applicable obligations may need to be retained. The operator should explain the retention criteria and periods when responding to your request.

Availability in this version

Features that depend on a database or Telegram connection only process registrations and messages when those services are active. Demonstration examples are labeled and do not represent verified accounts or communities.