Your data and your choices

Privacy notice

Remem is local-first. This notice explains what stays on your device, what is processed when you choose online features, and what those choices mean.

Effective 31 July 2026

1. Scope

This notice covers the Remem mobile app, its optional online services and Remem's published public pages. It does not replace the privacy terms of your device platform, app store, sign-in provider or other services you choose to use.

The short version Saved pins, notes and recordings are local. Speech recognition may use your device’s Apple or Google speech service. An account is optional. Signing in alone does not upload your pins, note text or recordings. Encrypted cloud backup and restore are not enabled in this version, and nothing uploads through that feature.

2. Data stored locally

Remem stores pin details, note text, recordings, saved locations, address labels and app settings on your device. These remain available for local and offline use, subject to the device and app continuing to hold the files.

Microphone permission is used when you record. Foreground location permission is used when you choose features that attach a location, show your position or resolve a place. Remem does not require continuous background location access for these features.

Remem keeps the saved recording on your device. Depending on device, language and availability, speech recognition may run on the device or speech audio may be processed online by Apple’s or Google’s speech service. Remem does not send the saved recording to its own server for transcription.

Local data may be lost if you delete it, clear the app’s storage, uninstall the app or lose the device. Do not assume an operating-system backup includes Remem data; Android device backup is disabled for Remem. CSV and GPX exports do not include recordings and are not a complete backup.

3. Optional accounts and purchases

Sign-in

You can use Remem’s local features without a Remem account. If you choose to sign in, Clerk processes the sign-in identity and session information needed to authenticate you. The details Clerk receives depend on the sign-in method you select.

Purchase identity

Remem sends an opaque Clerk user identifier to RevenueCat when linking an eligible signed-in account to its purchase identity. RevenueCat and the relevant app store process product, entitlement and transaction-status information. Pins, note text and recordings are not sent to RevenueCat for purchase linking.

Remem does not receive or store your card or bank details. The relevant app store and its payment providers handle payment.

4. Encrypted backup availability

Encrypted cloud backup and restore are not enabled in this version. There is no cloud-backup or cloud-restore action in this release, and Remem does not upload pins, note text, locations or recordings through that feature.

Remem’s release-disabled design is manual rather than continuous synchronisation and encrypts backup content on the device before any upload. Signing in alone does not start that process.

If encrypted backup is enabled in a future release, the app and this notice will identify its availability, eligibility, retention and storage limits before it can be used. The current release creates no remote backup through this feature.

5. Location and address lookup

Remem first tries the phone’s native address service using coordinates rounded to 4 decimal places. If that does not return a useful result, the app can still show a local Plus Code or rounded-coordinate fallback.

For a signed-in, purchase-linked user with locally resolved Premium, Remem may ask its Vercel service for a remote place name. The app sends a Clerk bearer token and the location rounded to 4 decimal places. Four decimal places is roughly 11 metres at the equator and remains precise location data. The service verifies the account and exact live Premium entitlement before passing the rounded location to OpenCage. Audio, note text and the unrounded GPS point are not sent for that lookup.

If the account, entitlement, connection or remote service cannot be verified, remote lookup fails closed and Remem keeps the native/local fallback. Local pin saving and recording are not blocked.

6. This website and support email

These static public pages contain no Remem-managed analytics, advertising scripts, account forms or payment forms. Vercel hosts the pages and may process standard request information, such as an IP address, browser or device information, requested path and timestamps, to deliver and protect the site.

If you email support, Remem processes the email address, message and attachments you choose to send so that the request can be reviewed and answered. Do not send an access token, full recording or other information that is not needed for support.

7. Service providers

  • Clerk: optional account authentication.
  • RevenueCat: purchase identity and Premium entitlement status.
  • Google Play or Apple’s App Store: purchase and payment processing on the relevant platform.
  • Apple or Google speech services: speech recognition provided by the device, which may process speech audio online when on-device recognition is unavailable.
  • Supabase: hosts release-disabled encrypted- backup infrastructure. This app version does not upload backup content to it.
  • Vercel: the cloud-access API and these public pages.
  • OpenCage: remote address lookup for an eligible linked Premium account, using a 4-decimal-place rounded location.

Each provider processes data under its own terms and privacy notice. Service providers may process data in countries other than your own, subject to their safeguards and applicable law.

8. Retention and deletion

  • Local data: remains on the device until you or the device removes it. Delete account keeps local pins and recordings; the separate Delete account and all local memories choice removes them from that device after account deletion completes.
  • Encrypted cloud backup: is disabled in this version, which creates no remote backup through that feature. Any future enabled version will state its retention terms before use.
  • Account and purchase records: a completed Remem account-deletion hand-off deletes the Clerk account and the linked RevenueCat customer profile. The relevant app store keeps its own transaction and subscription records under its legal, security and operational requirements.
  • Deletion-suppression records: during an account deletion attempt, Remem keeps a one-way pseudonymous cloud-write fence with creation and expiry timestamps so stale signed-in sessions cannot recreate cloud data. A separate RevenueCat erasure retry guard retains the opaque Clerk user identifier previously used as the RevenueCat app-user identifier, together with expiry, erasure-basis and retry-attempt metadata. This identifier is needed to find and re-delete a purchase profile recreated by a stale device; it is not an email address or profile name. Both safety windows are renewed in bounded periods while deletion is incomplete, retained for 30 days after completion and then automatically deleted. Neither record contains note content, locations or recordings.
  • Website request logs and support email: are retained by the relevant hosting and email services under their policies. Remem keeps deletion-request correspondence only as long as needed to verify ownership, fulfil and document the request, keep the process secure, and meet any legitimate legal obligation. It is deleted when no longer needed for those purposes.

User-initiated account deletion

When you choose Delete account in the app, Remem first asks its deletion service to prepare a durable, account-bound cleanup job. It then asks Clerk to delete the sign-in account and attempts to reset the on-device RevenueCat purchase identity before completing the prepared cleanup. If the app closes at that point, the deletion service can independently confirm that Clerk no longer has the account and resume the deletion. It fences new cloud writes, revokes access, removes associated cloud records, verifies that the cloud data is empty and deletes the linked RevenueCat customer profile. The pseudonymous cloud-write fence and opaque-identifier RevenueCat retry guard are retained as described above to catch stale-session recreation. The production deletion service is not currently configured, so online account deletion cannot yet complete. This version does not create a Remem encrypted cloud backup. Local data remains on the device unless you instead choose Delete account and all local memories. An external deletion request cannot erase local-only data from a device. RevenueCat customer deletion does not cancel a store subscription or delete the app store’s transaction records. If you cannot access the app, use the dedicated Remem account-deletion request page to start a request without reinstalling Remem. Ownership must be verified before provider data is changed, and a submitted request is not described as complete until the relevant outcomes are confirmed.

9. Security and your choices

Remem uses authenticated requests and server-side entitlement checks for eligible online features. No system can guarantee absolute security. Keep your device, store account and sign-in account secure.

You can choose to:

  • use local features without signing in;
  • deny or change device permissions in system settings;
  • delete individual local content in the app; or
  • start account deletion in the app; or
  • use the external deletion page to request deletion of the account and associated data without the app.

10. Changes and contact

This notice may change as Remem’s implemented features or legal obligations change. A revised notice will show a new effective date.

For privacy questions or an account-deletion concern, email support@tryremem.com. Include only the information needed to identify and investigate the request.