Product feature

Preserve evidence before supported deletions

With Tracker running, supported Telegram deletion confirmations are blocked while evidence is collected and acknowledged by Backend.

Why deletion evidence matters

A support conversation may contain the details needed to resolve a complaint or review an agent reply. Deleting messages before collecting that evidence can leave a manager without the context required for a fair review.

How the supported workflow behaves

Tracker detects supported Telegram deletion confirmations and covers the Delete button while collecting evidence. After Backend acknowledges the record, the block can be released so the user can decide whether to continue. Clicking Cancel closes the confirmation and removes the block. Tracker does not click Delete for the user.

Selected messages and whole-chat attempts

Supported selected-message capture includes ordinary text and supported media or media captions. Whole-chat deletion collection uses the authorised Telegram history channel and the configured scope, currently limited to the current month in this workflow. This is not a promise to preserve every historical message or every original media file.

An attempt is different from a completed deletion

Opening a confirmation establishes a deletion attempt. Backend receiving evidence establishes successful collection. Neither event alone proves that Telegram later completed a deletion. Keep those distinctions clear when reviewing the archive.

Retention and practical limits

Covered conversation and deletion records have one-year retention, with separate limits for image previews. Supported archives can be exported as readable HTML or JSON for longer storage. Live protection requires Tracker to run and the account and workspace to be verified; it does not protect activity performed while Tracker is closed.

Keep exploring