Telegram
Messaging Privacyby Telegram Official Team

How to Set Up Telegram Auto-Delete Timer for Private Chats?

Learn how to set up a Telegram auto-delete timer for private chats, with per-chat and global paths, platform steps, and data retention caveats.

#Auto-Delete Timer#Privacy Settings#Chat Security#Message Management#Telegram Configuration
how to set up Telegram auto-delete timer, Telegram auto-delete timer private chats, Telegram auto-delete timer not working, change Telegram auto-delete timer duration, Telegram disappearing messages setup, does Telegram auto-delete timer work in groups, disable Telegram auto-delete timer, Telegram privacy settings guide, Telegram secret chat timer

How to Set Up Telegram Auto-Delete Timer for Private Chats

Setting up a Telegram auto-delete timer for private chats means attaching a retention clock to a one-to-one conversation, so that each message disappears a fixed interval after it was sent. In the cloud-based chats that most people actually use day to day, that clock lives on Telegram's side: you switch it on from the chat's profile screen, and the resulting removal is mirrored to both participants and to every device where the account is signed in. It is a retention control, not a confidentiality control, and the entire value of the feature depends on whether you understand that distinction before you turn it on. That is why this guide is written from a compliance and data-retention angle rather than as a tap-by-tap walkthrough: what the timer can prove, what it cannot prove, where it leaks, and when you should deliberately leave the timer off.

What the Telegram Auto-Delete Timer Really Controls

The timer is a per-chat setting. Telegram stores it alongside the conversation, which is why it survives logging out, reinstalling the app, and moving to a new phone: when you sign back in, the chat shows up with its timer still counting. Internally, clients send this preference through Telegram's own API — the MTProto method messages.setHistoryTTL is documented in Telegram's public API reference for exactly this purpose, so if you want to confirm that the behaviour is server-side rather than device-local, that reference is the place to check. The practical consequence is worth stating plainly: an auto-delete chat is not a private vault, but a normal cloud conversation with a scheduled clean-up rule attached to it.

Because the rule is attached to the chat rather than to a device, both sides see the timer. Telegram's client shows the auto-delete setting inside the chat's information screen, which is a genuinely useful auditability property: in a dispute about whether a conversation was ephemeral by design or by accident, the setting is visible to the other participant in normal clients, rather than being an invisible unilateral action. Compare that with the far more common pattern of a person manually deleting individual messages after the fact, an action that leaves no visible trace of intent. If your goal is a defensible retention story, the timer is the stronger of the two, even though it deletes more.

The limit of the feature appears the moment you ask what the recipient did during the window. Auto-delete removes the message from the conversation record once the interval elapses; it does not and cannot recall what was already delivered. Screenshots, forward-to-Saved-Messages, an export taken before expiry, a third-party client that logs locally, and the operating system's own notification archive all sit outside Telegram's reach. Any retention design that treats the timer as a guarantee of non-persistence is therefore built on sand. Treat it as you would a document shredder: useful for reducing the volume of residual data, useless against a party who already photographed the page.

What the Telegram Auto-Delete Timer Really Controls
What the Telegram Auto-Delete Timer Really Controls

Three Neighbouring Features People Confuse With It

The first is Delete for everyone, the manual per-message action. Telegram does not impose the very short recall window that some other messengers use — in everyday testing, messages sent long ago can typically still be removed for both sides, though you should confirm current behaviour in your own client rather than relying on a blog post. The important difference is intent and traceability: manual deletion is a one-off action with no standing rule, and an auditor cannot tell whether it was applied consistently across a conversation. The second is Clear history, which wipes a conversation in a single act and is therefore a termination step rather than a policy. The third is the self-destruct timer in Secret Chats, which is end-to-end encrypted, device-bound, and measured in seconds rather than days. Confusing these three is the single most common source of disappointment with the retention feature, so the next section separates them properly.

A Comparison Table: Choosing the Right Retention Mechanism

Before touching any setting, decide which of the four mechanisms actually matches the risk you are managing. The table below summarises the practical differences as they appear in current clients; exact preset lists and wording vary by platform and by release, so treat the duration column as indicative and verify in your own app.

Mechanism Scope Where it is set Typical durations Visible to the other party Recoverable afterwards
Auto-delete timer (cloud private chat) Whole chat, all new messages Chat info screen, or global default in Privacy and Security Presets beginning at one day and extending into weeks; a custom value is usually offered Yes, shown in chat info No, once expired on both sides
Secret chat self-destruct timer One secret chat, one device pair Secret chat menu, or at creation Short intervals from seconds up to about a week Yes, with a countdown in the header No
Delete for everyone Individual message Message context menu Manual, no standing schedule The message simply disappears No, but the act is inconsistent
Clear history Whole conversation, one time Chat menu Immediate Often indicated by a service message No
Desktop export Snapshot of whatever still exists Desktop client settings On demand Not directly, but the result is a file Yes — that is the point of it

Read the last two columns together and the trade-off becomes obvious. Auto-delete and the secret chat timer are the only mechanisms that reduce future storage automatically, but both are observable to the counterparty, and both are silent about copies already taken. Export is the only mechanism that produces evidence you can hand to an auditor, which is precisely why it cannot coexist with a short retention window: whatever the export captured before the clock ran out is a permanent record, and no later deletion touches it. In a compliance context this is the sentence that matters — a retention timer governs the chat, not the derivatives of the chat.

A concrete illustration makes the point sharper. Imagine a two-person design studio that regularly sends client API tokens to a contract developer. If those tokens are pasted into a normal private chat with a one-day timer, the thread cleans itself up overnight, which feels tidy. But the token still exists in the developer's downloaded-files folder, in their Android notification history or iOS Notification Center entry, in any local cache the desktop client maintains, and in any copy they made deliberately. The correct control for a credential is rotation, not deletion; the timer merely narrows the window in which an unattended device leaks it.

The Decision Tree: Should This Chat Have a Timer at All?

Most instructions jump straight into menu paths. That is a mistake in a retention context, because the cost of a wrong timer is asymmetric: a timer that is too short destroys something you later need, and a timer that is too long keeps something you would rather not store. Walk the branches below in order, and stop at the first one that matches.

  1. Is there any chance this conversation will be needed as evidence — a contract dispute, an HR matter, a legal hold, a safety incident? If yes, stop. Do not enable a timer. Move the substance of the conversation to a channel that your organisation retains deliberately, and keep Telegram for coordination only.
  2. Does the information have a natural expiry that is shorter than your retention obligation? One-time codes, addresses for a single delivery, a Wi-Fi password for a visitor: a timer is appropriate, and the shortest useful preset is usually right.
  3. Does the counterparty need to search or quote this history later? If yes, a timer will produce broken quotes and gaps in the timeline. Prefer no timer, or a long one, and tell the other person what you chose.
  4. Is the actual risk interception rather than retention? If you are protecting content in transit and on the server, the correct tool is a Secret Chat with a self-destruct timer, not the cloud auto-delete row. The auto-delete timer operates on messages that Telegram can still read.
  5. Is this a personal, disposable conversation with someone who also expects it to be disposable? Then a global default is defensible, provided you accept that it will occasionally destroy something you wanted.

The branch that people skip is the first one, and it is the one a compliance reviewer will ask about. A timer is a policy decision, and policy decisions belong in a document, not only in a settings screen. If a retention rule exists nowhere except inside one employee's Telegram account, then when that employee leaves, the rule leaves with them and nobody can reconstruct why certain records vanished. Keep the reasoning outside the app — a short written rule, a review date, and a named owner are enough. Example: a one-time login code that will be rotated within the hour belongs in the second branch, while a negotiated statement of work belongs in the first, and no amount of tidiness in the chat screen changes that.

Boundary warning: If your organisation is subject to a litigation hold or a sector retention rule, deleting records that are covered by that obligation may itself be a compliance problem. This article describes how the Telegram setting behaves; it does not constitute legal advice. Confirm with your counsel or records officer before enabling automated deletion on business conversations.

Setting the Global Default (Android, iOS, Desktop, Web)

Telegram offers two levels of control. The global setting is a default applied to chats you start after you change it; the per-chat setting overrides it for one conversation. Start with the global one only if the majority of your conversations are genuinely disposable — otherwise you will spend your time turning timers off rather than setting them.

Android. Open the app and use the menu in the top-left corner, then go to Settings → Privacy and Security → Auto-Delete Messages. Choose a preset, or pick the custom option and enter a value. The shortest preset is generally one day, and the range extends out to a year, but the exact list is client-dependent — check what your build offers before assuming.

iOS. The path is effectively the same but the entry point differs: tap Settings at the bottom of the chat list, then Privacy and Security → Auto-Delete Messages, then select a duration. On iPhone the same screen can also be reached by searching Settings for the words “auto-delete” in some builds, which is faster when the row is buried below the fold.

Desktop (Windows, macOS, Linux). In the desktop client, open the hamburger menu in the top-left, choose Settings → Privacy and Security, and find Auto-Delete Messages. A dropdown is usually presented rather than a slider, and the desktop client is frequently the most complete place to review these options, so if a toggle is missing on your phone it is worth checking here before concluding the feature does not exist.

Web. Telegram Web exposes a comparable Privacy and Security screen, though the available rows have historically lagged behind the native clients. If you cannot find the option in the browser version, that is a client-coverage gap rather than a sign that your account lacks the capability.

Practical tip: After changing the global default, open a chat that existed before the change, tap its name, and look at the auto-delete row. If it still shows the old value or “Off”, you have confirmed the intended behaviour: the global setting seeds new chats and does not retroactively rewrite existing ones.

Setting the Timer Inside One Private Chat (Shortest Paths by Platform)

Per-chat control is where the feature becomes genuinely useful, because retention is usually a property of a relationship rather than of an account. The shortest path on every platform starts from the same place — the chat's own information screen.

Android. Open the conversation with the person, tap their name or avatar in the top bar, and look for the Auto-Delete row in the resulting list, typically placed near notification settings. Tap it and choose a duration. An alternative entry point in many builds is the overflow menu inside the chat itself, where the same option appears under the chat's settings.

iOS. Open the conversation and tap the contact's name at the top of the screen; the info sheet that slides up contains Auto-Delete. Selecting it opens a duration picker. On both mobile platforms the wording may read as “Auto-delete messages” or as a sentence about deleting after a period — the row position is the more reliable signal than the exact string.

Desktop. Click the chat's name in the header of the message pane to open the info panel, then click Auto-Delete and pick a value from the dropdown. Right-clicking the chat in the sidebar and choosing the info option reaches the same panel.

Fallback when the row is missing. Three causes are worth checking in order. First, your client may predate the feature — update it from the official store for your platform. Second, you may be looking at a Secret Chat, which uses the separate self-destruct timer instead. Third, some chat types do not expose the setting to all participants; in groups and channels, permissions govern who may change it. If none of these applies, verify with a second device signed into the same account: if the row is present there, the problem is local to the client you are holding.

One nuance deserves a warning label rather than a footnote. When you enable a timer in a chat that already contains history, the countdown is tied to each message's send time, and the clients generally present the timer as applying going forward. Whether previously delivered messages are purged retroactively has been a source of confusion across releases. Treat the honest answer as “verify it yourself”: the two-account protocol later in this article takes a few minutes to set up and removes the guesswork permanently.

Secret Chats: The Self-Destruct Timer Is a Different Tool

Secret Chats are end-to-end encrypted, exist only on the two devices that created them, do not appear in your other sessions, and cannot be forwarded. Their timer is therefore an entirely separate mechanism with its own path: open the Secret Chat, tap the contact's name at the top, and select Set self-destruct timer from the menu. Some clients let you choose the interval when the secret chat is first created; on desktop the timer sits in the chat's own menu.

The differences that matter for retention planning are structural rather than cosmetic. A secret chat has no cloud copy, so there is nothing on the server to delete later and nothing to export from another device. Its timer can be far shorter than the cloud auto-delete minimum — seconds rather than days — which makes it the right instrument for a password spoken once. The cost is operational: lose the device and the conversation is gone, and you cannot continue it from a laptop. That is a feature in a threat model built around device seizure, and an obstacle in a workflow built around switching between phone and desktop.

The compliance reading of this is straightforward. Secret Chats are a poor fit for anything that must be producible later, because by design there is no reliable place to produce it from. They are a good fit for source protection, one-time credentials, and personal matters where the residual risk of the chat record outweighs the residual value of retaining it. If you find yourself wanting to export a secret chat, you have chosen the wrong tool for that conversation.

What Happens When the Clock Expires (Observable Behaviour)

Understanding the failure modes of expiry requires looking at three different layers: the conversation record, the file system, and the notification system. They behave differently, and only the first is under Telegram's control.

Inside the conversation, expired messages are removed from the thread and the timeline closes the gap, so a chat left alone for a week and then reopened can show a visible jump in dates. Messages that quoted a deleted message may render with a placeholder rather than cleanly. Pinned messages are an edge case worth testing rather than assuming: if the pinned message is itself subject to the timer, the pin may end up pointing at nothing. These are empirical observations from normal client use and they vary by build, which is exactly why the verification protocol below exists.

On the file system the picture is less tidy. Media that the recipient downloaded before expiry lives on their device independently of Telegram's servers. Deleting the message does not delete the downloaded file, and the file will remain in the gallery, downloads folder, or desktop cache until the operating system or the user removes it. Anyone designing a retention rule should therefore separate “the chat no longer shows this” from “this no longer exists anywhere,” because only the first is guaranteed.

Notifications are the third and most commonly overlooked layer. A push notification that has already been delivered is not recalled when the underlying message expires. On Android, notification history can retain dismissed alerts; on iOS, Notification Center keeps recent items; on macOS the same is true of Notification Center. A message with a one-minute effective life can persist in an operating-system tray for hours. This is a genuine retention leak in any environment where devices are shared, inspected, or backed up, and it is not something a Telegram setting can close — only device-level policy and user habit can.

Exceptions, Trade-Offs, and the Compliance Gap

Every retention control has exceptions, and listing them explicitly is what separates a policy from a preference. Start with counterparty behaviour, which is the largest exception: a recipient can screenshot, photograph the screen with another camera, forward to Saved Messages, or copy text before the timer fires. In cloud private chats, forwarding is normally permitted unless content protection is enabled and supported for that chat type; the availability of that protection varies between chat types and clients, so check the chat's info screen rather than assuming it is present.

The second exception is the client itself. Telegram publishes official clients, but unofficial and modified clients exist, and a modified client can log every incoming message to local storage regardless of what the timer says. A retention promise is only as strong as the weakest client in the conversation, and you generally cannot verify which one the other person is running. This is not a reason to avoid the feature; it is a reason not to describe it as a guarantee in writing.

The third exception is the audit trail. Consumer Telegram does not present an administrator console that records who changed which retention setting and when; the visibility you get is the timer shown in chat info, which is per-conversation and manual. Working hypothesis, open to your own testing: for organisations that need centralised retention evidence, Telegram's consumer clients are the wrong layer, and the answer is either a platform with administrative eDiscovery tooling or an internal policy that keeps regulated conversations off the platform entirely. Verify what your own client exposes before committing to either position.

Finally, consider the cost of over-deletion. A timer that is too aggressive destroys context that people rely on: the address you will need next month, the name of the person who approved a change, the error message nobody wrote down. Teams routinely discover this only when a chat that should have contained the answer is a column of date gaps. The mitigation is not to abandon timers but to tier them — short timers for credentials and logistics, no timer for decisions and agreements, and an explicit note in the conversation when something needs to survive.

A Reproducible Verification Protocol (Two Accounts, Three Tests)

Claims about deletion behaviour should be testable on your own devices. The protocol below needs two Telegram accounts on two devices — a spare account on an old phone is sufficient — and it produces observable results rather than opinions. Run it once when you first enable the feature and again after any major client update.

Test 1, timer visibility and scope. From account A, open the chat with account B, tap the header to reach chat info, and set the auto-delete timer to the shortest available preset. Send a test message. On account B, open the same chat's info screen and confirm that the timer is shown there too. This establishes the observability property: the other party can see that a retention rule is in force. Then check whether messages sent before the change are affected, by looking at the top of the thread. Record what you see, because this is the point on which documentation and reality most often diverge.

Test 2, media persistence. From A, send a photo. On B, download it and note where it lands — the gallery album on mobile, or the downloads directory the desktop client uses, which varies by installation and operating system. Wait for the timer to expire. Then check two things independently: whether the chat still shows the image, and whether the file is still present on the device. Expect the first to be yes-deleted and the second to be yes-present. That asymmetry is the core of the retention caveat in this article, and seeing it once is more persuasive than reading it five times.

Test 3, notification persistence. Put device B in the background with notifications enabled, and send a message from A whose content is easy to identify in text form. Do not open the notification. Once the message has expired in the chat, inspect the operating system's own notification record — Android's notification history in system settings, or Notification Center on iOS and macOS — and observe whether the text survives there. Interpretation matters here: if it survives, the leak is in the operating system layer, and the only fixes are device-level settings that clear or disable notification history.

For a same-day check of the underlying mechanics, use a Secret Chat instead of a cloud chat. Its timer can be set to a very short interval, so you can watch a message disappear within a minute and observe the countdown in the header. The behaviour you learn there applies to secret chats, not to the cloud auto-delete row, and conflating the two is the most frequent error in guides on this topic.

Bots, Archives, and Least Privilege

A recurring question in retention discussions is whether a bot can manage or bypass the timer. The short answer is no, and the mechanics explain why. Telegram's Bot API delivers updates to a bot only for chats the bot is part of, and only for events that occur while it is present; it does not expose a general-purpose method for reading someone's private conversations or their message history. A one-to-one chat between two people is not a place where you can add a third-party bot, because that chat type has no membership list to add it to. Bots live in their own chats with you, or in groups and channels.

This has a direct consequence for the “archiving bot” pattern. If you add an archiving bot to a group to preserve messages for later review, the bot collects only what is posted while it is a member — it cannot retrieve the history that predates its arrival, and it cannot reach into your private chats at all. In practice such a bot is a counterforce to deletion: it creates a durable copy in a third-party system, which is the opposite of what an auto-delete timer is trying to achieve. Before adopting one, be explicit with the group about which goal takes priority, because keeping both simultaneously is contradictory.

Where a bot genuinely helps is administration rather than retention: notifying you that a retention rule should be reviewed, or maintaining an external log of your written policy. Apply least privilege in the ordinary way — a dedicated group rather than an existing working group, minimal permissions, a clear owner, and a periodic review of whether the bot still needs to exist. If a third-party service asks for your Telegram login code or your phone number to “manage your privacy settings,” treat it as an account-takeover attempt. Session credentials are the account; sharing them hands over everything the timer is trying to protect.

Do not trust bots that claim to set your auto-delete timer. The timer is a chat-level setting exposed in the client's own interface. No official bot command exists for changing it, and any service advertising that capability is either misleading you or attempting to obtain session access.

Troubleshooting: Symptom, Cause, Verification, Fix

Retention settings fail in quiet ways, which makes a structured approach more useful than a checklist of guesses. Work through the table, then re-run the relevant part of the verification protocol to confirm the fix.

Symptom Likely cause How to verify Resolution
No auto-delete row in chat info Outdated client, or you are inside a Secret Chat, which uses the self-destruct timer Open the same account on a second device and compare Update the app from the official store; use the secret chat menu for secret chats
Timer set, messages still visible Timer applies to messages sent after it was enabled; or the client has not refreshed Check chat info, close and reopen the app, compare on the other device Wait for the interval to elapse on new messages; confirm the setting is truly saved
Other party does not see the timer Their client is older, or they are viewing a different chat Ask them to open chat info and read the row back to you Have them update; otherwise treat the timer as unverified for that relationship
Downloaded photos still on the device Expected behaviour — the message and the file are separate objects Test 2 in the protocol above Delete the file manually; manage device storage separately from chat retention
Exported archive contains later-deleted messages An export is a snapshot taken at the moment it ran Compare the export timestamp with the timer interval Treat exports as retained records and secure them accordingly
Global default did not affect old chats It seeds new chats; existing chats keep their own setting Open an old chat's info screen before and after the change Set the timer per chat where you need it
Timer appears to reset after clearing history Possibly sync lag between clients, or the chat object was recreated Capture the chat info screen before and after, on two devices Re-apply the timer and confirm it persists after a restart

Two rows in that table are worth internalising because they account for most confusion. The retroactivity question — whether enabling a timer purges existing history — is the one to test rather than argue about, since behaviour has shifted across releases and the answer may differ between your phone and your desktop. The export row is the one that matters most in a compliance context, because an export is the exact artefact that survives every deletion mechanism you have, and it usually lives on an unmanaged laptop.

Troubleshooting: Symptom, Cause, Verification, Fix
Troubleshooting: Symptom, Cause, Verification, Fix

Applicable and Non-Applicable Scenarios

Clear admission criteria prevent the slow drift into using a timer everywhere because it feels tidy. The feature fits situations where the value of the information decays faster than the risk of holding it, and it fits poorly where the opposite is true.

Use the auto-delete timer for: one-time access codes and delivery addresses; short-lived credentials that will be rotated anyway; personal logistics with family members who also prefer a clean thread; freelancer relationships where both parties have agreed in writing that the chat is not a record of the engagement; and shared-device households where the phone may be handed to someone else. It also suits notifications-heavy chats where history is noise rather than context.

Do not use it for: anything under litigation hold or sector retention rules; contract negotiation where the written terms will matter; HR or disciplinary conversations; incident records; support workflows where history is the product being delivered; community or channel content that members expect to search later; and any conversation where the other person may reasonably need to quote you in six months. In those cases the correct action is to move the substance to a channel your organisation retains deliberately, and keep Telegram for logistics.

Two ambiguous categories are worth calling out. Journalistic or source-protection conversations benefit from the short timers available in Secret Chats, but the cloud auto-delete timer is a weaker instrument because the messages pass through Telegram's servers and the timer only governs the conversation record. Small teams using private chats as informal project threads sit in between: a long timer, or none at all, plus an explicit rule that decisions get copied into a shared document, is usually the honest arrangement.

Best Practices: Operating Rules for Retention in Telegram

Rules beat settings, because settings are per-device and rules survive a new phone. The following eight are ordered by how much trouble they prevent, and they are written to be copied into a team handbook with minimal editing.

  1. Choose per-chat timers rather than a global default, unless nearly all of your conversations are genuinely disposable. A global default is convenient and forgetful in equal measure.
  2. Match the interval to the shortest life of the information, not to how sensitive it feels. A Wi-Fi password for tomorrow's visit does not need a month.
  3. Announce the timer in the conversation when it is first enabled, so the other party is not surprised by a gap in the thread.
  4. Never rely on deletion for secrets. Rotate the credential; treat the timer as a supplementary reduction in exposure.
  5. Assume anything sent can be copied before expiry, and decide whether that changes what you are willing to send.
  6. Keep an external record of your retention decisions — which chat categories carry which intervals, and why.
  7. Review the rules on a schedule, and after any client update that touches privacy settings.
  8. Remember that exports, notification archives, and downloaded files sit outside the timer, and manage those layers separately.

The fourth rule carries more weight than its brevity suggests. A large share of real-world disclosure incidents involving messaging apps come from stale credentials, not from chat history, and an expired token in a thread that has been cleaned up is still an expired token in the recipient's password manager. Similarly, the sixth rule is what makes the whole arrangement auditable: without a written statement of intent, an external reviewer sees only that messages vanished and cannot distinguish a deliberate policy from an accident.

A Retention Decision Record You Can Keep Outside Telegram

Because Telegram does not provide a central retention console for personal accounts, the record has to live somewhere else. A short structured file per chat category is enough, and it takes a few minutes per year to maintain. The template below is deliberately generic — it is a documentation pattern, not a Telegram feature, and no Telegram setting reads it.

{
  "retention_rule_id": "privacy-tier-b-short",
  "chat_category": "contractor credential handoffs",
  "platform": "Telegram private chat",
  "auto_delete_interval": "shortest available preset",
  "rationale": "credentials are rotated after use; history has no residual value",
  "known_exceptions": ["recipient-downloaded media", "notification archives", "prior exports"],
  "owner": "name or role",
  "last_reviewed": "year-month",
  "next_review": "year-month plus one quarter",
  "approved_by": "name or role"
}

The value of writing this down is that it forces the two questions people avoid: who decided this, and when does the decision get revisited. It also makes the boundaries explicit, which is the part auditors care about most — knowing that downloaded media and prior exports sit outside the rule is a sign of a considered policy rather than an optimistic one. Store the file where your other records live, not inside Telegram itself.

Version Differences and Migration Notes

Feature placement in Telegram has moved between releases, and any guide that quotes a fixed build number is out of date almost immediately. The reliable way to check what your client supports is to open Settings → Privacy and Security and read the rows that are actually there, then compare with the chat info screen in a conversation. When a setting exists in the desktop client but not on your phone, that is a coverage gap rather than a missing capability, and the setting you change from the desktop applies to the account as a whole.

Migration has three practical dimensions. Moving to a new phone preserves cloud chats and their timers, because the setting is account-level; secret chats do not migrate, and their content is gone with the old device. Switching platforms may expose additional options, particularly on desktop. And restoring a device from a full backup may resurrect locally stored copies that the chat layer no longer shows, which is the single most common way a well-intentioned retention rule fails quietly. After any migration, re-run the media and notification tests rather than assuming continuity.

Because this area is still moving, the durable habit is to verify rather than to memorise: the menu path you learned last year may be correct today and rearranged tomorrow, while the underlying behaviour — a chat-level rule, visible to both sides, blind to copies already taken — has proven far more stable than the interface around it.

Frequently Asked Questions

Does the Telegram auto-delete timer delete messages on the other person's device too?

In a regular cloud private chat, yes. The timer is a chat-level setting stored with the conversation, so when the interval elapses the message is removed from the thread on both sides and on all your own signed-in devices. What it cannot do is recall copies that already left the chat — screenshots, downloads to device storage, forwards, exports, and operating-system notification entries all survive.

Can I use the standard auto-delete timer inside a Secret Chat?

No. Secret Chats use their own self-destruct timer, set from the secret chat's menu by tapping the contact's name, or chosen when the secret chat is created. That timer supports much shorter intervals than the cloud setting and applies only to that device pair, because secret chats are not stored in the cloud and do not appear on your other sessions.

What is the shortest auto-delete interval available?

In the cloud auto-delete setting, presets generally begin at one day and extend into weeks, with a custom value often offered as well. Secret chat self-destruct timers go down to seconds. Preset lists have changed between releases and differ slightly by platform, so check the picker in your own client rather than relying on a published list.

Does a global auto-delete default apply to chats I already have?

The global option acts as a default for chats you start after changing it; conversations that already exist keep their own setting. The quick way to confirm this on your account is to open an older chat's information screen before and after the change and compare the auto-delete row. If you need a timer on an existing chat, set it inside that chat.

Can a bot read my private chats or change my auto-delete timer?

No. Bots receive updates only for chats they are members of, and only for messages sent while they are present; a one-to-one chat has no membership to add a bot to, and there is no official bot command for changing the timer. Any service that offers to manage your auto-delete settings, or that asks for your login code, should be treated as a security risk rather than a convenience.

Closing: The Next Three Actions

The Telegram auto-delete timer is a solid retention control and a poor confidentiality control, and the whole skill lies in keeping those two ideas apart. It removes messages from a conversation on both sides after an interval you choose, it is visible to the counterparty in chat info, and it applies going forward rather than rewriting the past. It does nothing about downloaded files, exports, notification archives, third-party clients, or the recipient's memory, and none of those layers are within Telegram's reach. Read the feature as a housekeeping rule with an audit trail, not as a shredder that guarantees destruction.

Three actions follow from that. First, run the two-account verification protocol once, so your own client's behaviour is established by observation rather than by assumption — the notification and media tests are the ones that most often change someone's mind. Second, decide the placement of the timer deliberately: per chat for sensitive relationships, a global default only if your conversations are genuinely disposable, and no timer at all where a record may be needed later. Third, write the decision down outside Telegram, including the exceptions you are accepting, so that the rule can be reviewed by someone other than the person who set it.

If a conversation needs secrecy rather than tidiness, the right instrument is a Secret Chat with a self-destruct timer; if it needs to be producible later, the right instrument is no timer plus a deliberate export into managed storage. The timer is at its best in the middle of those two extremes, quietly closing conversations that nobody needs to reopen.