Your recordings, transcripts, and summaries are stored on your device — not on a Memorly server, because Memorly doesn't run one.
No advertising IDs, no analytics trackers, no data brokers. What little leaves your device is described in full below.
Memorly ("the app," "we," "our") is a voice-memo app that records what you say, transcribes it, and summarizes it so you can find it again later. This policy explains, plainly, what information the app touches, where it goes, and what control you have over it.
By using Memorly, you agree to the practices described here. If anything below is unclear, the fastest fix is to email us — see Contact.
When you record a memory, the audio file is saved in your device's app storage, and the resulting transcript and AI-generated summary are saved in a local database on your device (using Hive, an on-device storage library). None of this is uploaded to, or stored on, a server we control — we don't have one for this data.
To turn speech into text and text into a summary, your recording's audio and transcript are sent over an encrypted connection to Groq, Inc., the AI provider Memorly uses for transcription and summarization. Groq processes this content to return a result and is bound by its own privacy policy, which governs how it retains and handles that data on its end.
Semantic search works differently: query matching runs entirely on your device using a local AI model, so search terms are never sent anywhere.
Memorly works fully without ever signing in. If you choose to, Profile offers an optional phone-number sign-in — its only purpose is to let a Memorly Pro purchase follow you if you switch devices. Signing in sends your phone number to Firebase Authentication (a Google service) to verify a one-time SMS code; Firebase then gives us a stable, anonymous identifier (not the phone number itself) that we associate with your subscription status via RevenueCat. We do not use this number for marketing, and nothing about your recordings is tied to it.
If you subscribe to Memorly Pro, purchase handling is managed by RevenueCat together with the Google Play billing system. They process what's needed to validate and maintain your subscription status (such as a purchase token and entitlement state). Memorly never sees or stores your payment card details — Google Play handles that directly.
| Permission | Why Memorly asks for it |
|---|---|
| Microphone | Required to record a memory. Only active while you're actively recording. |
| Notifications | Used for reminders you can turn on in Profile — a nudge after a call ends, a daily reminder, a weekly recap, or a reminder about a meeting you mentioned. All scheduled and shown entirely on your device. |
| Phone state (optional) | Only used if you opt in to the "call reminder" feature. Memorly reads only the call state (idle, ringing, ended) — never call audio, never who you spoke to, never call content. |
We do not use anything you record for advertising, profiling, or training purposes on our end.
Everything Memorly creates — audio files, transcripts, summaries, your settings — lives in local storage on your device for as long as you keep it there.
The only exception is the brief, in-transit processing described above (Groq for transcription/summarization, Firebase for optional sign-in, RevenueCat/Google Play for purchases) — each governed by that provider's own retention practices, not ours.
Sign-in is entirely optional and can be turned off at any time from Profile — signing out stops any future association between your phone number and your subscription. Since your recordings never touch an account in the first place, deleting the app's data (via the app itself or your device's app settings) or uninstalling the app is a complete, immediate removal of everything else.
Memorly is not directed at children under 13, and we do not knowingly collect information from them. If you believe a child has used the app and this policy needs updating as a result, contact us and we'll address it.
Data in transit to Groq, Firebase, or RevenueCat is sent over encrypted HTTPS connections. Because the overwhelming majority of your data never leaves your device, your exposure is largely tied to your own device's security — using a device lock screen is the single best protection for the memories stored there.
If Memorly's data practices change — for example, adding a new third-party service — this page will be updated and the "last updated" date at the top will change accordingly. Meaningful changes will also be surfaced in the app itself where practical.