How to store notes, passwords, and files in Saved Messages++

Start with the Saved Messages++ project page: its header links to the bot and web app. The bot opens the Mini App; you work with records inside the application. The interface is currently in English, so the action names below match the actual UI.

Open the right vault

Open the app from Telegram and wait for the account check. Create makes a new vault; Restore recovers access to an existing one using its recovery phrase. If you have already saved records, creating a new independent identity will not transfer them automatically: the earlier data still requires its original access.

When reopening, use the unlock method configured on that device. PIN unlock needs a server connection. Protected storage and biometrics are available where the Telegram client actually supplies the required capabilities. Do not treat a PIN as a universal way to open data without a network.

In an ordinary browser without verified Telegram context, you can try Demo. These are temporary records in the current tab: they do not become a personal vault, are not sent to the server, and disappear when the tab closes. Demo is sufficient for exploring the editor, but not for persistent storage.

Create and save your first record

1. Choose the type. Use Notes for ordinary text, Passwords for a credential card, and Files for a small attachment. A short, unimportant note is a useful first record for seeing the complete save flow.
2. Fill in the relevant fields. A note has a title and body; check Markdown through Preview. A password card stores the login, password, and address separately. Attachments are selected from the device and retain their filenames.
3. Add useful tags. A few consistent names help you find records later. There is no need to turn every word in the text into a separate tag.
4. Press Save and read the status. Saved on this device means local saving, Waiting to sync means the upload is pending, and Synced means synchronization has completed. These are different states, particularly when a record needs to appear on another device.

Unsaved editor changes can remain as an encrypted local draft. Draft kept on this device refers to that draft, not completed server synchronization of the record. Use Save for an intentional save and check the resulting status.

Find records and return to earlier versions

After unlocking, search covers titles, text, logins, addresses, and tags. The secret in the password field is excluded: failing to find a card by the password itself is expected. Try its title, login, or a relevant tag instead.

You can pin frequently used records. Archive suits a record you no longer need in the main list but may want later; it is different from permanent deletion. If an edit damaged the text, open Version history. It offers the current version and up to 32 previous server revisions. Restoring creates a new version; if a newer edit conflicts with it, resolve those changes first.

If the connection drops

Changes already saved locally remain in the outgoing queue. Restore connectivity and check whether the status changes to Synced. Retry sync is available when a retryable synchronization error is shown. Do not clear browser data or create a new vault simply to dismiss a warning: that can lose local work that has not yet reached the server.

Offline opening is possible when the application shell and encrypted records have been prepared on the device, and an available unlock method supports it. A first launch without a cache needs connectivity. A browser can remove local data, so offline access does not replace synchronization or backing up access.

If the app offers to restore a draft, check which record it belongs to. When the underlying version has changed, Restore as a new note keeps a separate copy rather than silently overwriting it. The latest characters before a forced app termination may not have been saved; an acknowledged draft-save status matters more than assuming the editor captured everything.

Prepare recovery before losing the device

In Settings, open Recovery backup and follow the available backup flow. Its 24 words are tied to your vault. Enter them only in the application’s appropriate recovery interface; never send them to anyone, including the bot, an AI agent, support, or the server operator.

Keep a copy separately from the only device with access. Exporting the phrase creates an unencrypted file, so downloading it does not itself mean it is stored safely. Mark I saved my recovery phrase only after actually retaining a copy. Hide backup notice dismisses the reminder without acknowledging that a backup exists.

Frequently asked questions

Can I just forward a message to the bot?

Not yet. The bot is an entry point; forwarded messages are not saved as notes. The current workflow is to create a record inside the Mini App.

What if I lose the recovery phrase?

If a device still opens your records, do not reset its data; check whether Recovery backup is available. Unlocking an ordinary device does not always mean it can display the original phrase. Without a copy of the phrase or suitable retained access, do not expect an administrator to recover it.

Can I upload large videos and audio files?

The current interface does not accept them. Combined attachments in one record are limited to 512,000 bytes, roughly 500 KB. The account’s shared budget is 10 MB; creating an additional vault does not increase it.

How can I tell Demo from a real account?

Demo displays Temporary demo, and its data exists only in the tab. Before using the app for persistent storage, return to normal entry through Telegram and make sure you are working in the intended personal vault.