Protect the device
Use a strong Android screen lock, keep Android and Remem updated and do not leave an unlocked phone with someone you do not trust.
Plain-English guide
Remem stores its core memory data locally on your Android device. An account is optional for core local use. Some optional actions involve outside services, so “local-first” does not mean that every possible action stays on the phone.
Where information goes
| Activity | Current behaviour | User choice or limit |
|---|---|---|
| Core capture and finding | Memory data is stored locally by the Android app. | No Remem account is required for core local use. |
| Optional account sign-in | Clerk provides Remem’s account sign-in service. | Signing in does not upload your local memories. |
| Purchases and entitlement | The relevant app store and RevenueCat handle purchase status. Remem does not receive card or bank details. | Only applies when you choose an eligible purchase. |
| Remote place-name lookup | For eligible Premium use, a Remem service may send a Clerk bearer token and coordinates rounded to four decimal places to OpenCage. Rounded coordinates are still precise location data. | Native address lookup is attempted first; the remote lookup applies only when its conditions are met. |
| Encrypted cloud backup | Disabled in the current release. | No pins, text, locations, photos or recordings are uploaded through this feature. |
| Exports | Android saves or shares the file to the destination you choose. | After export, security depends on that destination and who can access it. |
Practical protection
No inflated claims
No software or mobile device can promise absolute security. Local data is affected by the security of the phone, Android, installed apps, account services and any place to which a file is exported.
Remem does not describe the disabled backup feature as end-to-end encrypted or zero knowledge. Those terms are not claims about the current release.
Full documents