This public ledger backs the sections added by packet W5-P2 on
Add and manage accounts: “I forgot my two-step verification password” and
“How do I back up all my chats and media?”. Luckgram source links are pinned to the revisions reviewed on
October 10 (iOS f42e2ad, Android 235be7c); Telegram Desktop links are pinned to upstream
tdesktop 4e5f92b. A string in public source shows what a client can display; it does not prove that a
given installed release shows it.
| Page | Statement | Evidence |
|---|---|---|
| getting-started/accounts.md | Bought through Account Shop or imported as a session: contact support before trying anything | SCR-011 · accounts.md § I lost my phone or SIM card (same routing) · help/app-problems.md (“Accounts bought through Telegram Sessions or imported as a session … Contact support first”) |
| Forgot password: tap Forgot password? on the password screen | iOS strings:1397 · AuthorizationSequencePasswordEntryControllerNode.swift:87 (sign-in screen) · TwoStepVerificationUnlockController.swift:231 (settings screen) · Android strings:3529 · LoginActivity.java:5536 · TwoStepVerificationActivity.java:529 | |
| With a recovery email: a 6-digit code is emailed; entering it removes the password, then a new one can be set | Telegram FAQ: 2-Step Verification (“a recovery email address that will help regain access, should you forget your password”) · Two-factor authentication: Email recovery (logged-in sessions, and at sign-in once the login code is accepted; the code deletes the current password, then a new one is set) · iOS strings:1418 · iOS strings:3849 · Android strings:3513-3515 | |
| No recovery email or no access to it, but another session: Settings → Privacy and Security → Two-Step Verification → Forgot password? (with a recovery email, then Can’t access your email?) and confirm; after 7 days return to that screen and tap Reset Password; until then it shows the time left | Two-factor authentication: Password reset (logged-in sessions only; 7-day server-side timer) · account.resetPassword · Telegram FAQ: 2-Step Verification (settings path) · iOS strings:953 · iOS strings:1367 · iOS strings:6757-6765 (RecoveryEmailResetText 6759, ResetPendingText “You can reset your password in %@.” 6761, ResetAction “Reset Password” 6763, RecoveryEmailResetNoAccess “Can’t access your email?” 6765; the reset is a second account.resetPassword call once the wait has passed) · ResetPasswordController.swift:142 · Android strings:3425 · Android strings:3593 · Android strings:3507-3512 |
|
| Cancelling the reset means a new request waits another 7 days | Two-factor authentication: Password reset (account.resetPasswordFailedWait) · iOS strings:6764 · Android strings:3483 · Android strings:3521 |
|
| Neither: Reset account cannot be undone; messages, media, contacts and groups are deleted; signing up again gives an empty account | Two-factor authentication: Account deletion · Telegram FAQ: what happens if I delete my account (“irreversible. If you sign up again, you will appear as a new user and will not get your history, contacts or groups back”) · iOS strings:1411-1414 · Android strings:57 · Android strings:3505 · Android strings:3522-3525 | |
| Telegram may delay the reset by a week if the account was recently active; the app says so | Account deletion (only when the 2FA password was modified more than 7 days ago and the account was active in the last 7 days: deletion delayed 7 days, and a service message with a confirmation link lets a signed-in user cancel; otherwise deletion is immediate) · iOS strings:2142-2146 · Android strings:58-60 | |
| Neither Telegram nor Luckgram support can tell you the password; never share it or a recovery code, even with someone claiming to be support | Two-factor authentication: Password recovery (the only options are reset, email recovery and account deletion) · Telegram FAQ: phone stolen · help/README.md (“Never send a login code or recovery secret to support”) · dataroom facts no-private-help, account-compromise |
|
| Lost the phone too: link to “I lost my phone or SIM card” | accounts.md § I lost my phone or SIM card · help-troubleshooting-2026-10-13.md | |
| Cloud messages stay on Telegram’s servers and come back on any device, even after losing the phone | Telegram FAQ: why not make all chats secret (“stored encrypted in the Telegram Cloud … accessible from any of your devices – even if you lose your device altogether”) · Telegram FAQ: which devices (“your cloud chats will sync instantly”) · Telegram FAQ: GDPR (cloud chats accessible “without using third-party backups”) | |
| Secret chats stay only on the device where they started, cannot be exported or backed up, and are lost on logout or with the device | Telegram FAQ: how are secret chats different (“device-specific and are not part of the Telegram cloud”) · iOS strings:839 (“logging out kills all your Secret Chats”) · Telegram FAQ: how do I start a secret chat (“this chat will only be available on that device. If you log out, you will lose all your secret chats”), so an export run on a computer cannot reach them | |
| Telegram Desktop is Telegram’s computer app (on a Mac, the one from desktop.telegram.org, not Luckgram or another Telegram app); sign in with the same number | Telegram Desktop · Telegram FAQ: which devices (desktop app for Windows, macOS and Linux; “use your main mobile phone number to log in everywhere”) | |
| Everything: Settings → Advanced → Export Telegram data | Telegram blog: Chat Export Tool (Telegram Desktop, “Export Telegram data”) · settings_advanced.cpp:1182-1192 · settings_advanced.cpp:1289 (the export button is built in the Advanced section) · tdesktop lang.strings:859 · tdesktop lang.strings:1309 | |
| What can be ticked: profile information, contacts, story archive, personal and bot chats, groups, channels, media kinds, files up to a size limit | Telegram blog: Chat Export Tool (“some (or all) of your chats, including photos and other media”) · tdesktop lang.strings:7249-7279 | |
| HTML to read, JSON for programs, or both; a folder, Downloads by default; keep Telegram Desktop running until it finishes | Telegram blog: Chat Export Tool (“JSON-format or … HTML”) · tdesktop lang.strings:7280-7286 · export_view_settings.cpp:304-306 (default path shown as Downloads/…) · tdesktop lang.strings:7298 (“Please don’t quit Telegram until the data export is completed”) |
|
| One conversation: ⋯ → Export chat history | Telegram blog: Chat Export Tool (“opening the … menu in any chat and choosing Export chat history”) · window_peer_menu.cpp:1039-1041 · tdesktop lang.strings:1890 | |
| Export chat history is not offered for chats where copying is turned off (the full export is not claimed either way) | data_peer.cpp:789-791 (canExportChatHistory is false when !allowsForwarding()) |
|
| A newly signed-in computer may have to wait before the export starts; repeat the request there when told | tdesktop lang.strings:7308 (lng_export_delay: “For security reasons, you will be able to begin downloading your data in {hours} … repeat the request using the same device”) |
|
| The result is files on the computer; messages the other person later deletes for both sides stay in a copy saved before | Telegram blog: Chat Export Tool (“save conversations on your disk … accessible offline”) · Telegram FAQ: can I delete my messages (either side can delete messages for both sides). The second half follows from the first two: deletion acts on Telegram’s cloud and the apps, not on files already saved to a disk | |
| Luckgram’s own chat export: link to “Export messages instead of sessions” (no new Luckgram claim) | accounts.md § Export messages instead of sessions · Product review |
Fetched on 2026-10-13: telegram.org/faq, telegram.org/blog/export-and-more, desktop.telegram.org,
core.telegram.org/api/srp, core.telegram.org/method/account.resetPassword and core.telegram.org/api/account-deletion;
tdesktop files at 4e5f92b from raw.githubusercontent.com.
W5-P2 drafted this section for Media and call tools and held it back: the data agent’s golden row g-06 sat at coverage 0.596 against a floor of 0.6, and any new public section naming Telegram Premium pushed g-06 over the floor with a wrong answer. The data agent’s premium-2fa round (agent PR #49: price words count only next to Premium/subscription/plan, “Telegram Premium” is its own topic) fixed that in ranking, not in this text. PR #49 was open at Wiki 0d1ba21; this section merges only after it is deployed.
| Statement | Evidence |
|---|---|
| Stories are a Telegram feature; Luckgram adds nothing of its own to posting; contacts see a story at the top of their chat list; you choose who can see it | Telegram blog: Stories (“displayed in an expandable section at the top of your screen”, “you’ll see stories from all your contacts”) · features/README.md (Stories not listed as a Luckgram feature) · no story code in Luckgram-only modules (iOS Luckgram/ at f42e2ad, Android luckgram-features/ at 235be7c) |
| Steps are for iPhone, iPad and Android; Luckgram Desktop shows stories but cannot post them | luckgram.cc/download (Luckgram Desktop for macOS) · tdesktop 4e5f92b (the Luckgram Desktop base): stories are loaded and viewed, no stories.sendStory call outside api.tl, no string for posting |
| Take a photo or video, or pick one from the gallery; add text, stickers and a caption | Telegram blog: Stories (“add text, drawings, stickers … captions”) |
| Luckgram Premium is a separate plan and doesn’t include these | plans-and-rewards.md (“Luckgram Premium is separate from Telegram Premium”) |
| Tap My Story at the top of the chat list | iOS strings:9486 · StoryPeerListItemComponent.swift:959 · Android strings:6519 · DialogStoriesCell.java:630 |
| Who sees it: Everyone, Contacts, Close Friends, Selected Contacts; exclude people; Allow Screenshots; Keep on My Page; Post Story | Telegram blog: Stories (“4 privacy settings … include or exclude any users”; disable screenshots) · Telegram Stories API: posting · iOS strings:9727-9729 · iOS strings:9753-9756 · iOS strings:9774 · Android strings:6596-6605 · Android strings:6737 · Android strings:6744 · StoryPrivacyBottomSheet.java:1205-1209 |
| A story lasts 24 hours; Telegram Premium adds 6, 12 and 48 hours, more active stories, links and formatting in captions, Stealth Mode | stories.sendStory and Stories API: posting (period 6/12/24/48 h for Premium, 24 h otherwise) · Client configuration (story_expiring_limit_premium, stories_entities) · Stories API: stealth mode · iOS strings:9689 · Android strings:6689-6690 · Android strings:6846 |
| Who may post and the weekly or monthly limits are set by Telegram; when posting needs Premium the app says so | Client configuration: stories_posting (enabled / premium / disabled) · Stories API: posting (PREMIUM_ACCOUNT_REQUIRED, weekly and monthly limits) · Android strings:6823 |
Luckgram adds no limit of its own: an account that can post in the official Telegram app can post in Luckgram for iPhone, iPad and Android; Luckgram Premium does not unlock posting (added 2026-10-23, asked by luckgramappbot, Fabric board finding 3c32ef70) |
re-read at the current releases: no story code in Luckgram-only modules at iOS 2.6.4 f75b666 (git grep -i story finds only replyToStoryId: nil in NGCallRecorder) and Android 1.62.1 56701eb (none in luckgram-features/); in the Telegram stories screens Luckgram only swaps a logo (DialogStoriesCell.java:338) and keeps an unused import (StoriesUtilities.java:35); whether an account may post is the server’s stories_posting (Client configuration) · Luckgram Premium is separate from Telegram Premium (plans-and-rewards.md) |
| Channels and groups post stories once boosted, through an admin with the right; on iPhone and iPad no posting during a call or a video chat | Stories API: posting (post_stories admin right, BOOSTS_REQUIRED); the call block is iOS only (ChatListController.swift:3186, strings 9483), Android 235be7c has no such check · iOS strings:9483-9484 |