Customer leads in Telegram: a convenient chat full of personal data

A form on the site sends a lead to Telegram because it is faster than mail. Then the group lives its own life: a manager was added, then a contractor, then a person "just to look". The history is not erased on the day someone leaves. The customer's phone, sometimes a passport or a delivery address, sits in a thread the company no longer fully controls.

For the personal-data law this is not a trifle and not "a messenger outside the site". The lead was collected by a form. Who the operator is, who else sees the message, how long it is kept, whether it can be pulled off someone else's phone. We do not replace the legal text, but the technical picture is usually worse than the paragraph in the policy: the bot sits on a developer's personal account, the token is written in the page code, the group is open by a link.

How to keep Telegram without handing out the database

• The bot and the group on a work contour, not on the personal number of whoever built the site.
• The chat gets the minimum: name and phone. A passport and the thread are not copied there.
• The bot token does not sit in a script a visitor can see.
• Remove the person from the group on the day they leave. The history they already downloaded is still a risk.

Lexora looks at this together: the form, where it actually writes, and who has access. It is often one site audit plus personal-data protection, not two unrelated projects. The basic audit is free for new clients. If the token was already exposed or an extra person could read the group, the secret is rotated immediately, not after a "big policy".