Secure the phone
Use a screen lock, keep the operating system updated and take care when allowing anyone else to use the device.
Current release status
The honest question behind this page is what happens if you lose the phone. On Remem Web, Android and iOS, every real pin belongs from creation to one exact Remem account and saves locally first. Signed-in Free and Premium use the same encrypted Sync with the account key handled internally by Remem. Signing out hides personal content and stops active Sync without silently deleting the retained account collection. Account deletion and local-data removal are separate explicit actions.
Account and Sync
Signing in creates or connects your exact Remem account. Every real pin belongs to that account from creation; an email address is not the ownership key.
Signing in does not grant Premium or start a charge. It reveals only that exact account’s collection, and account collections never merge.
A signed-in Free or Premium account receives encrypted Sync. Remem recovers or provisions the account Sync key through its authenticated service and encrypts eligible content on the device before upload.
Sign in to the same Remem account on another eligible device and Sync starts there automatically. On Android and iOS, a genuine pin conflict automatically preserves both versions as separate pins in the same account collection. On Remem Web, conflicting data remains unchanged until the customer makes an explicit choice.
Remem Web, Android and iOS start Sync automatically for the signed-in Free or Premium account and use its internally recovered key. Eligible pins, note text, saved precise locations, recordings, eligible photos and deletions can then synchronise between enabled devices. A deliberate eligible-pin deletion on one enabled device can therefore remove that pin from another enabled device after the revision and conflict checks are applied.
Only five portable locale settings are included: language, region, date format, time format and week start. Other app or device settings are not synchronised.
Changes made offline are kept in a durable queue. Remem sends them when the app is open, in the foreground and connected; operating systems may not run or deliver sync while the app is in the background.
Compare-and-set (CAS) server revisions and deletion tombstones identify competing edits and removals. A conflict never silently overwrites either side. Android and iOS automatically preserve both pin versions; Remem Web asks the user to choose Keep this device or Use other device.
Sync is subject to the service limits in force for the signed-in account; this page does not promise a fixed storage quota or retention window. Premium ending preserves and synchronises every existing pin and photo and allows them to be managed. It blocks only another admission at the applicable Free boundary until the count falls below that boundary. A deliberate pin deletion can still synchronise between enabled devices.
Protect local data
Your pins, recordings and photos are local app data. Removing the app, clearing its storage, losing the device or suffering device failure may remove that local copy. Encrypted Sync can make eligible synced pins available on another connected device after the same Remem account is verified, but it is not a guaranteed backup or recovery service. Remem disables Android device backup. Backup behaviour on Apple devices is controlled by the operating system and may vary. Do not assume either platform will recover Remem data automatically.
Different kinds of copy
| Option | Current purpose | Can it populate Remem? |
|---|---|---|
| CSV export | Use selected unarchived pin details in a spreadsheet. | No |
| GPX export | Use unarchived located pins in compatible mapping tools. | No |
| Technical local-data download | Obtain a technical copy of local data. | No |
| Encrypted continuous sync | Synchronise eligible content, deletions and five portable locale settings. Sync starts automatically on Remem Web, Android and iOS for the signed-in Free or Premium account. | Yes, with the same eligible account. Sync runs while Remem is open, in the foreground and connected. Phone pin conflicts preserve both versions automatically; Remem Web conflicts require an explicit user choice. |
Accurate security language
On Remem Web, Android and iOS, the authenticated Remem service provisions or recovers the signed-in account’s Sync key internally. Eligible content receives authenticated encryption on the device before upload, and Supabase stores only authenticated server-wrapped key escrow rather than the plaintext account Sync key. Supabase also stores encrypted copies plus limited account, storage, object-path, size, usage, revision, operation, deletion and timestamp metadata needed to operate and protect the service. Remem does not call the feature “zero knowledge” or make an absolute-security promise.
Read the privacy and security guideCommon questions
On Remem Web, Android and iOS, Sync starts automatically for the exact signed-in Free or Premium account.
No. Sync depends on account access, service availability and the applicable service limits. Keep an appropriate independent copy of important information.
Server revisions and deletion tombstones detect the conflict. Android and iOS automatically preserve both pin versions as separate pins in the same account collection. Remem Web leaves the conflicting data unchanged until the customer chooses Keep this device or Use other device.
Eligible changes made offline stay queued. Remem synchronises them while the app is open, in the foreground and connected. It does not promise background delivery by the operating system.
Every real pin belongs from creation to one exact Remem account. Signing in reveals only that account’s collection; collections never merge. Free and Premium use the same local-first encrypted Sync.
No. Those files are exports or technical copies and cannot be imported into the app.