Mnemo is built around a private archive first, with cloud continuity available on top when you want the archive to travel across devices.
Continuity
Use this page to understand what cloud continuity adds, what stays local-first, and where some environments still need more careful expectations.
Baseline
Your archive still starts with you
Mnemo does not stop being a private archive when continuity is available. Local use remains a valid and supported way to use the product.
Added layer
Cloud helps the archive follow you
Sign-in, account recovery, and sync behavior help another device pick up where you left off when continuity matters.
Reality check
Some environments still need caveats
Browser-based use and a few continuity flows can still need manual retry, unlock steps, or more cautious expectations than native local use.
What cloud continuity adds
- cross-device access to the same archive
- account-related recovery and sign-in flows
- continuity for archive content and related media
- a way to keep work moving when you switch devices
What does not change
- Mnemo is still meant to feel like a private archive
- local-first use is still a valid default
- export and import still matter for backup and portability
- privacy and access controls still matter even when continuity is enabled
When to enable it
Cloud continuity is most useful when:
- you use more than one device
- you want the archive available after reinstalling or replacing a device
- you want less manual movement of data between environments
When to stay conservative
Stay conservative about expectations when:
- you are depending on browser-based use
- another device does not update immediately
- your build still exposes explicit unlock or manual sync steps
If that happens, use Troubleshooting and keep export or local fallback paths in mind.