Plain-English guide

Privacy and security at Remem

Your pins, itineraries and saved Places belong to your Remem account. They save locally first, then encrypted Sync carries your changes between your phone and Remem Web. Search, maps, navigation and sharing use the information needed for the action you choose. Here is where that information goes and how you control it.

Where information goes

How each feature uses your information

Activity Current behaviour User choice or limit
Signed-out use Home and List show bundled, immutable example pins. Creating or owning a real pin requires sign-in.
Account sign-in Clerk provides Remem’s account sign-in service. Sign-in identifies the exact account that owns every real pin from creation; email is not the owner key.
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, the app authenticates with Remem’s service. That service can send coordinates rounded to four decimal places to OpenCage to find an address. Your sign-in token is not sent 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.
Place search and route planning Place search sends your search words through Remem’s authenticated service to OpenCage. Route requests send the start, destination, travel mode and route preferences through Remem’s service to Apple, Google or TomTom. Pin notes, photos and recordings are not sent to calculate a route or look up an address. Choosing a search result does not save a pin until you save it.
Location and phone navigation When location is on and available, Remem saves it automatically with a new captured pin. A journey you start uses location updates for directions and can continue with spoken guidance while the screen is locked. You choose when to start and end navigation. Your phone’s location permissions control the access Remem receives.
Shared location link When you choose to share a located pin, only its precise coordinates are sent to Remem’s service to create the link. The coordinates are encrypted, and only hashes of the public and revocation tokens are stored. Every sent link expires 30 days after creation. If sharing is cancelled before sending, Remem may invalidate the unused link. The current app does not provide a control to stop sharing a link after it has been sent. The pin identifier, transcript, Notes field, photos and audio are not uploaded to create the link. Anyone with the link can open, copy or forward the precise location. No maps provider is contacted until the recipient chooses one. An expired or invalidated record is normally deleted automatically after it has been inactive for seven days; a temporary service delay may postpone deletion.
Encrypted continuous sync On Remem Web, Android and iOS, starts automatically for the signed-in Free or Premium account using that account’s Sync key handled internally by Remem. Pins and their eligible media, itineraries, saved Places, saved pin order, deletions and five portable locale settings receive authenticated encryption on the device before upload. Offline changes queue durably and sync while Remem is open, in the foreground and connected. Android and iOS automatically preserve both versions of a conflicting pin. Remem Web requires a Keep this device or Use other device choice.
Exports Your device saves or shares the file to the destination you choose. After export, security depends on that destination and who can access it.
Public website analytics Seven product and marketing pages on the canonical tryremem.com hostname load Google Analytics (GA4) automatically so Remem can measure page use. Preview and local hostnames, legal, support, accessibility, account-deletion and private location-share pages do not load the tag. There is no separate analytics opt-in on the website. Full detail is in the privacy notice.

Practical protection

Steps that reduce avoidable risk

Protect the device

Use a strong screen lock, keep the operating system and Remem updated, and do not leave an unlocked phone with someone you do not trust.

Review permissions

Your operating system controls access to capabilities such as location, microphone, photos and notifications. Review these permissions in device settings if your needs change.

Protect exported files

CSV and GPX files may expose dates, text and precise locations. Check the destination and recipient before saving or sharing.

Control who receives a location link

Anyone with the link can open, copy or forward the precise location. Send it only to the intended recipient. The current app does not provide a control to stop sharing the link after it has been sent.

Secure the email account used to sign in

Anyone who can access that email account may be able to use a sign-in code. Protect the mailbox and its recovery options.

Remove data deliberately

Check local data before uninstalling the app or clearing its storage. Those actions may remove saved pins from the device.

Report a concern

If you think a Remem account or service has been misused, contact support with the time, device and action involved. Do not send passwords or private pin content unless needed.

Contact Remem support

Your account and devices

How protection works

No software or mobile device can promise absolute security. Local data is affected by the security of the phone, its operating system, installed apps, account services and any place to which a file is exported.

On Remem Web, Android and iOS, Remem’s authenticated service provisions or recovers the signed-in account’s Sync key internally. Eligible content is encrypted on the device before upload, and Supabase stores only authenticated server-wrapped key escrow rather than the plaintext account Sync key. Remem makes no absolute-security, zero-knowledge or guaranteed background-delivery claim.

Your account across devices

  • Remem on Apple, Android and the web
  • Signed-out Home and List show immutable examples
  • Real creation requires sign-in to the owning account
  • Automatic encrypted Sync for signed-in Free and Premium
  • The same account-key flow on web, Android and iOS
  • Account-key handling remains internal to Remem
  • Sync runs while Remem is open, foregrounded and connected

Full documents

Read the policy and control your account