Mnemo is designed around a private archive first. Settings should help you protect that archive, tune how it behaves, and decide how much continuity you want.

Control surface

Use this area to control access, preferences, notifications, archive handling, and any cloud-account options available in your build.

Protection

Local access controls

Depending on your build, Mnemo can expose local sign-in, passcode, biometrics, or relock behavior after the app leaves the foreground.

Preferences

Experience tuning

Appearance, language, playback, link handling, and notification choices help the archive feel personal and manageable.

Archive

Privacy and data controls

Export, import, local storage expectations, and archive handling remain central even when continuity is enabled.

Protect access

Depending on the build, Mnemo can include protection features such as:

  • local sign-in or profile setup
  • passcode or biometric lock
  • protected access after backgrounding

These controls matter because Mnemo is meant to hold a private archive, not disposable content.

Preferences

Available settings may include:

  • appearance and theme
  • language
  • playback preferences
  • link opening behavior
  • notification preferences

Archive controls

Archive controls are especially important when you care about ownership and recovery.

What to look for:

  • local storage expectations
  • export and import where available
  • what stays on device by default
  • how continuity behaves once enabled

Cloud account management

If your build includes cloud continuity, settings may also include:

  • sign-in
  • account creation
  • email verification
  • password reset
  • account deletion
  • supported provider sign-in

Notifications and reminders

Notification settings shape how Mnemo resurfaces memory over time. If reminders matter to your workflow, check both device-level permissions and in-app options.

Continuity note

Cloud continuity is available, but some builds may still require an explicit unlock step or a manual retry before recent changes appear elsewhere. Keep browser-based use in the category of available with caveats rather than assumed parity in every scenario.


Back to top

© 2026 Mnemo. Public docs and project updates.

This site uses Just the Docs, a documentation theme for Jekyll.