Privacy notice
2026-10-04.3Who controls the data
The service operator identified below handles personal data for the purposes described here. The connected account owner chooses the chats to back up; we operate hosting, access, payment and support. This does not remove the rights of other people whose messages are stored. Anyone, including people who do not use Keep, can send access, correction or deletion requests to the support address below.
What we process
We process: your Telegram account ID, name, language and settings; connected chat and sender identifiers; new message text, captions, available attachments and timestamps; snapshots for deleted/edited-message alerts; referral attribution, access grants, payment and order identifiers, plan, amount, currency and payment status; and a record of your policy acceptance. Available attachments can include quoted and disappearing media; saved copies may remain after the original disappears. Web infrastructure may process connection data such as IP address and user agent for delivery and security. Before acceptance we process only the account, connection, language and invitation data needed to show the notice and answer your requests. Declining pauses core functions and new capture; help and privacy controls remain available. Account and connection identifiers are necessary for backup, and payment references for paid access. We never ask for your Telegram password or login code; do not send them, or the website sign-in code, to support.
Purposes and recipients
We use this data to provide backups and alerts, authenticate you, deliver paid access and referral rewards, prevent misuse, handle support and meet legal obligations. Telegram delivers bot events and messages and processes Stars invoices, payment identifiers and refunds. Stripe hosts the external checkout and processes payment details; card details are not entered on our server. Hosting providers store the service database and files; a cloud storage provider may hold an encrypted media archive. When analytics is enabled, an analytics provider receives usage events and your Telegram account ID, name and language, but not message contents or chat partners’ identifiers. These providers may process data outside your country under their own policies and safeguards. Saved content and alerts are made available to the connected account owner, who may keep or share copies and exports outside Keep; we cannot recall those.
Storage and retention
Saved message text remains until you clear it. Local attachment files may be moved to an encrypted archive after 14 days. Archived media is kept for no more than 12 months from the archive date. Recovery backups follow a rolling schedule and may retain deleted data for up to 12 months. Payment, referral and acceptance records are kept only for the period required for access, disputes and applicable record-keeping law.
Deletion and control
Pause backup or disconnect the bot to stop new collection. Clearing saved data removes active database records, alert snapshots and local files not shared by another record immediately. To remove linked archive copies, send a deletion request to support; after verification, we complete it within 30 days. Recovery backups are used only for recovery, and deletion is reapplied after restoration. We cannot delete copies already sent through Telegram, downloaded exports or data held independently by payment or analytics providers. Requests do not require paid access or acceptance of new terms.
Cookies and security
The billing site uses a strictly necessary session cookie to keep you signed in. Keep app sign-in codes and session credentials are stored hashed. Codes expire after 5 minutes and app sessions after 30 days; signing out revokes the current session. HTTPS protects data in transit, access to saved data is scoped to the signed-in Telegram account, and the external media archive is encrypted. Saved data is stored on the service’s servers. No system can guarantee absolute security.
Changes and contact
The version date appears below. Updated notices are published here. Contact support with privacy questions, including about messages involving you.