Privacy

Updated 2026-10-29. Keep is operated by ROLIA GROUP LIMITED, West Wing 2/F, 822 Lai Chi Kok Road, Cheung Sha Wan, Kowloon, Hong Kong. Contact apps@rolia.ee.

Android: server backup

When connecting, your phone number, login code and two-step verification password pass through our server to Telegram. Keep does not log login codes or passwords. Our server retains an authorized Telegram session and uses it to collect your selected chats, including while the app is closed.

We process account and selected-chat names and identifiers, message text, received revisions, deletion markers, available profile photos and enabled media. Archives use AES-256-GCM encryption at rest and HTTPS in transit. Encryption is server-side, not end-to-end: the service operator can technically decrypt archives.

iPhone: bot archive and local imports

The beta companion reads your Keep bot archive after sign-in with a single-use Keep code. It does not receive Telegram user-session keys. The bot processes messages and available media delivered by Telegram from the chats you connect after consent, including quoted and disappearing media that may remain in the saved copy. Bot storage, retention and deletion follow the Keep bot privacy notice; the Android encryption and 14-day recovery-backup terms on this page do not describe the bot service.

Imported JSON and ZIP files stay in the app container and are not uploaded to Keep. Your iOS device backup settings may include them.

Additional data

If activity history is enabled, the server retains Telegram-provided statuses for selected contacts for up to 30 days. Missing observations do not mean offline. Notifications use a device token, language and event type; they do not contain chat text. IP addresses support request limiting and country suggestions for phone entry.

Android can send technical crash data to Firebase Crashlytics. Google Play and RevenueCat process subscription status; Keep does not receive card details. Operational measurements must not contain message content, phone numbers or counterpart names. On Android, we record app and screen opens, connection and backup steps, trials, verified subscription access and error codes. A random installation identifier is linked to a pseudonymous account identifier after sign-in to distinguish repeat actions and measure returns. These events are stored on the Keep server for up to 90 days; account-linked analytics is removed when the account is deleted.

Data about other people

Your archive contains messages, names, profile photos and, if you enable activity history, statuses of the people you chat with. We process this data only on your instructions, to keep your own copy of your conversations, and we never contact them. Use your archive for personal purposes and in line with the law; do not use Keep to monitor other people. Anyone who believes their data is processed unlawfully can contact us at the address below.

Legal bases

Contract: to create, store and deliver your copy and manage your subscription. Legitimate interests: security, request limiting, crash reports and disaster-recovery backups. Consent: activity history and notifications; you can withdraw it in settings at any time. Legal obligations: payment records.

Where data is stored

Keep’s production server and archives are located in Singapore. Some providers process data in the United States and other countries: Google (Firebase, Google Play, Google Drive for encrypted disaster-recovery backups), Cloudflare (HTTPS delivery) and RevenueCat (subscription status). Transfers from the EU and UK to countries without an adequacy decision rely on the European Commission’s Standard Contractual Clauses (with the UK Addendum) and, for certified US providers, the EU-US Data Privacy Framework. You can request a copy of the relevant safeguards at the address below.

Providers

Telegram supplies authentication and message access; Cloudflare delivers HTTPS; hosting runs the server; Firebase supplies push and crash reporting; Google Play and RevenueCat handle subscriptions; the operator’s private Google Drive stores encrypted disaster-recovery backups. We do not sell archive content or use it for advertising.

Automatic media rotation

When your plan’s media storage is full, Keep makes room by automatically deleting the media files of your oldest saved messages. Message text stays. Media of deleted messages and of messages with saved edits is never removed this way. To keep older files, export a ZIP or choose a larger plan.

Moving an account

If you sign in to the same Telegram account from a different Keep account, for example after reinstalling, Keep asks you to confirm a move. Once confirmed, that Telegram account’s archive and subscription move to the new Keep account and the previous one loses access. Signing in with the Telegram code proves you control that account.

Retention and deletion

Archives remain until you delete them, subject to media rotation above. Pausing stops new capture but retains the archive and session. Disconnecting Telegram stops the connection while keeping saved content. Deleting your Keep account removes archives, files, tokens and push registrations. When Telegram is unavailable, session revocation is retried; the credentials needed for that retry are removed after completion.

An encrypted disaster-recovery backup is created daily and retained for 14 days. Data deleted from the live service may remain in these backups until scheduled expiry. These copies are not used for ordinary archive access.

Deleting a local iPhone archive does not change its original export or server data. See deletion instructions.

Your rights

You can ask to access and receive a copy of your data, correct it, delete it, restrict processing, receive it in a machine-readable format, object to processing based on legitimate interests and withdraw consent. Most of this is available in the app: browse, export to PDF/CSV/ZIP, pause and delete. Otherwise email apps@rolia.ee. We respond within one month; for complex requests we may extend this by two further months and will tell you so. To protect your archive, we may ask you to confirm you own the account.

You have the right to lodge a complaint with the data protection supervisory authority in the country where you live, work or where an alleged infringement took place.

Children

Keep is intended for people aged 18 and over. We do not knowingly process children’s data. If you believe a child is using Keep, contact us and we will delete the account.

Changes

We will announce material changes to this policy in the app or on this page before they take effect.