Your saves, explained.

This describes the current Remmly implementation. Updated September 20, 2026.

What Remmly stores

Your phone keeps captures and downloaded copies in local app storage. When you sign in and sync, your connected backend stores your email, profile, saved content, attachments, collections, reminders and Ask history. Each account can access its own library.

Who processes it

Remmly Cloud uses Cloudflare for the API, database and private file storage. ZeptoMail's India endpoint sends sign-in codes. The configured AI provider receives saved text or media for analysis and relevant excerpts for answers. The default provider is Google Gemini. Supported public video links can go through the shared AWS Lambda media processor; resulting media is stored in Cloudflare R2.

Shared media job records, including the source link and processing result, expire after 24 hours and are removed by scheduled cleanup. Processing failure categories are kept in infrastructure logs for one week without source links or user content. Your backend and chosen processors can access content they handle. Remmly does not provide end-to-end encryption. Self-hosting lets you choose your backend, AI provider and optional media processor.

Permissions and sharing

Microphone access is used when you record a voice note. Notifications are optional and used for reminders. Remmly receives content you explicitly share through your phone share menu or add in the app or workspace. It does not read your WhatsApp conversations or sign in to your social accounts.

Removing and exporting content

You can delete saved items and clear Ask history in the app. Deleting a save also removes its linked reminders and clears saved answer history on that backend. Other devices need to sync to remove cached copies. Settings includes a JSON export of notes and metadata; it is not an archive of attachment bytes.

Settings includes account deletion, confirmed with a fresh email code. It revokes access and removes your account, saved content and files. Storage cleanup runs in the background and retries if unavailable. A deletion marker remains for 30 days to reject late writes, and longer if cleanup needs to retry. Copies on another offline device need to be removed there. Uninstalling alone does not delete a server account. For deletion help, contact rahul@datahase.com; self-hosted users should contact their backend operator.

Passkeys and shared saves

A passkey stores a public credential on the backend. Your biometric data and private credential stay with your device or credential provider. Shared links make the selected title, note, summary, source link and any explicitly included files accessible to anyone with the link. Revoking a link prevents further access through Remmly, but cannot remove copies already downloaded.

Location and requests

Remmly uses global Cloudflare infrastructure, ZeptoMail India and the configured AI provider. Data may be processed outside your country, including outside the EEA. Contact rahul@datahase.com about access, correction, deletion or privacy concerns. This page describes the product; it does not assert EU data residency or a completed legal compliance assessment.

The website and workspace

The interactive library on this site uses fictional examples stored in the page. It does not submit your questions or connect to your personal library. The web workspace at app.remmly.link uses essential session cookies for sign-in and temporary browser storage to restore a shared-link journey. No advertising or analytics scripts are included.