Web Companion

Last updated 2026-10-12

Memlore Web (web.memlore.app) is an optional in-browser companion to the Memlore desktop app. It allows you to open, search and edit your existing journal from any modern web browser without sending your journal content, passwords, or encryption keys to any application server.

How to sign in

Memlore Web opens an existing vault that has already been created on your desktop and synced to Google Drive.

  1. Open web.memlore.app in any modern browser (Chrome, Safari, Firefox, Edge).
  2. Click Sign in with Google and authorize access to your Google Drive application data folder.
  3. Enter the 24-word recovery phrase you saved when you set up Memlore on your desktop.
  4. Set a local web password. This password encrypts your session credentials in your browser's local storage so you do not need to re-enter the 24 words on every visit.
  • Zero-knowledge keysYour 24-word recovery phrase and master keys are unpacked in WebAssembly memory and are never sent across the network.
  • Direct cloud connectionYour browser communicates directly with Google Drive APIs over HTTPS. There is no Memlore intermediate server.

What works and what is desktop-only

You can read, search and write in your journal on the web. Most other features stay on the desktop app. See Web vs desktop for the full feature-by-feature table.

For security invariants and technical design, see the Privacy Policy and Sync documentation.

How a web edit reaches your desktop

How a web edit reaches your desktop You edit an entry on the web. The browser saves a sealed draft and uploads it to the web outbox, a folder in your Google Drive app data that holds one file per entry. When the desktop app syncs, it reads the outbox, merges the edit into your journal, and writes a receipt for each edit. On its next sync it uploads the merged entry. When the web refreshes, it shows the desktop copy and drops its draft. The outbox file stays on Drive and is overwritten by the next edit of that entry. Text from both sides is kept. For the title, mood, journal, date, favorite, and tags, the desktop wins if it changed them too. This browser Your Google Drive Desktop app 1 · You edit Sealed draft saved Web outbox One file per entry Kept, overwritten by the next edit 2 · Desktop syncs Merges the edit 3 · Next sync Uploads the result Desktop files Merged entry Receipt for each edit (step 2) 4 · Web refreshes Shows desktop copy Text from both sides is kept. Title, mood, journal, date, favorite, tags: the desktop wins if it changed them too. How a web edit reaches your desktop You edit an entry on the web. The browser saves a sealed draft and uploads it to the web outbox, a folder in your Google Drive app data that holds one file per entry. When the desktop app syncs, it reads the outbox, merges the edit into your journal, and writes a receipt for each edit. On its next sync it uploads the merged entry. When the web refreshes, it shows the desktop copy and drops its draft. The outbox file stays on Drive and is overwritten by the next edit of that entry. Text from both sides is kept. For the title, mood, journal, date, favorite, and tags, the desktop wins if it changed them too. 1 · You edit In this browser: sealed draft Web outbox On Drive: one file per entry 2 · Desktop syncs Merges, writes a receipt 3 · Next desktop sync Uploads the result Desktop files On Drive: entry and receipt 4 · Web refreshes Shows the desktop copy Text from both sides is kept. Title, mood, journal, date, favorite, tags: the desktop wins if it changed them too.
  • Your text is never lostText written on the web and on the desktop is merged, so both sides stay in the entry.
  • The desktop decides the restFor the title, mood, journal, date, favorite, and tags, your edit applies only if the desktop has not changed that field since the web last saw the entry. Otherwise the web tells you which edit was replaced.
  • The draft stays until it is safeThe browser keeps your draft until the desktop's copy shows the edit. The outbox file on Drive is never deleted; your next edit of that entry overwrites it.

Safety and the outbox model

Your desktop vault is always the primary authority. To guarantee that a browser session can never corrupt your journal database:

  • Web never writes sync protocol files directly. Instead, the web companion creates sealed write intents in a private `outbox/` folder.
  • Desktop imports and verifies all edits. When your desktop app syncs, it reads the outbox, merges text changes using CRDTs (so concurrent typing is preserved), and saves the result to your local encrypted database.
  • Deletes go to the desktop Trash. Deleting on the web moves the entry to the Trash on your desktop, where you can restore it for 30 days. The browser only hides the entry until your desktop applies the move, so a web delete erases nothing. Deleting forever or emptying the Trash from the web does erase entries for good, on your desktop too, so it asks you to type DELETE first. Anyone with your unlocked web session can queue a delete, so lock or sign out on a shared computer.
  • Instant revocation. You can cut off web access at any time from your desktop app: open Settings → Security → Security actions → Connected devices and remove the web companion. At its next sync the web tab drops its cached entries and locks; its unsent edits stay sealed in the browser until you re-connect or clear the site data.

Caching and privacy on shared computers

  • Encrypted local storage: Memlore Web caches downloaded entry files in your browser's IndexedDB strictly as AES-256-GCM ciphertexts. Unencrypted text is never stored on disk.
  • In-memory keys: Encryption keys live in volatile WebAssembly memory. When you click Lock or close the browser tab, the keys in memory are erased immediately.
  • Refresh without retyping: So that reloading the page does not ask for your password again, the open tab keeps a sealed copy of the master key in its session storage, with the one-time key that opens it. The app uses it only when you reload that same tab; a new tab asks for your password. It is deleted when you click Lock or the tab auto-locks, and the app stops using it at the auto-lock time (sooner while the tab is in the background); a reload does not count as activity (the key press of a keyboard reload does). Closing the tab does not delete it right away: the browser may keep the tab's session storage on disk for tab restore. These time limits are checks in the app, not in the encryption: anyone who copies this browser profile could open your journal with the stored copy, so click Lock before you leave a shared computer.
  • Leaving a shared device: Clear cache in Memlore Web settings removes cached photos and videos only. To remove everything Memlore Web stored in that browser (cached entries, unsent edits and the password-wrapped key), clear the site data for web.memlore.app in the browser's settings before leaving.