Telelog Privacy policy
Revision date: 16 November 2026.
1. About the service
Telelog is a conversation archive service provided through a Telegram bot and Mini App. The service is administered by the Telelog team. For data processing questions and support, contact @jsonic.
This policy explains what information Telelog receives, why it needs it, who can access it and how to request deletion.
2. Data we process
When you use the service, the following data may be processed:
- Telegram ID, profile name, username, selected language, bot connection details and permissions granted to it;
- messages from conversations authorized by the user: text, captions, sender information, chat and message identifiers, dates, replies, received message revisions and deletion events;
- attachment information available through Telegram and, where technically possible, local copies of photos, videos, documents, audio and other attachments;
- profile photos accessible to the bot for display in the interface;
- technical information needed to handle requests, protect access and diagnose faults;
- support requests, subscription status, manual subscription grants and payment information once payment functionality is enabled.
The service receives only the data Telegram sends to the bot within the granted permissions. It does not receive history that existed before connection unless that history is separately obtained through a supported feature.
3. Why we use data
Information is used to save and display conversations, notify users of edits and deletions, provide search, exports and files, manage access, handle support requests and protect against abuse. Once payments are launched, payment information is also used to confirm purchases, renewals and refunds.
Permissions granted to the bot are controlled by Telegram settings. Connecting the bot does not replace separate consent where applicable law requires it. Users must consider the rights of other participants when archiving and subsequently using conversations.
4. Access and interaction with other services
An owner's archive is accessible after Telegram authorization has been verified. Other ordinary users of the service are not given access to that archive.
Authorized administrators have the technical ability to view archives through the administration interface. This access is intended for maintenance, support and investigation of faults and abuse. Telelog does not provide archive encryption that prevents administrators from accessing it.
Telegram participates in message transmission, authorization and notification delivery. Server infrastructure is used to host the service. Once Platega is connected, the payment provider receives information needed to process and match payments, including the amount, currency, order number and buyer identifier. Conversations are not sent to Platega for payment processing.
Data may also be disclosed where necessary to comply with applicable mandatory requirements. Conversation content is not sold to advertisers or made publicly available by the service.
5. Storage and deletion
Message archives are retained to provide the service until deleted by the user or processing is ended following an appropriate request or another applicable basis. Subscription expiry does not by itself delete the archive. Revoking permissions in Telegram stops receipt of new data within the revoked access but does not automatically delete data already received.
Media are stored in a limited cache. Technical availability depends on Telegram, retention periods, quotas and the condition of the local copy. A message being present in the archive does not guarantee that its attachment will remain available indefinitely.
Users can delete an individual conversation through its menu. To delete an account and remaining data, or ask about processing procedures, contact @jsonic. After account deletion, a minimal Telegram ID record may be retained to prevent data collection from restarting while the bot remains connected; this record contains no conversation content.
After the working copy is deleted, residual data may remain in limited technical backups until their scheduled replacement. Support can provide details about the handling of a specific request. Payment and other mandatory records may be retained separately where there is a lawful basis.
6. Protection and requests
The service uses authorization checks, separation of owners' access, restrictions on administrative privileges and technical safeguards. Absolute protection against every failure or third-party action is not promised. This provision does not release the administration from obligations imposed by applicable law.
For access, correction, deletion or withdrawal of consent, contact @jsonic. To protect the archive, proof of ownership of the Telegram account may be required; support does not need your passwords, login codes or payment secrets.
7. Changes
The current dated version is published at the service's permanent link. Users are informed of material changes to processing, and additional consent is requested where required.