Linking Another Device
Add a second device that decrypts and syncs the same vault.
Linking needs a sync plan. Without one, Link new device explains the plan instead of showing a code, because a linked device would open an empty vault of its own. On a free account, sign in on the new device with your recovery phrase instead.
How Linking Works
When you link a new device:
- The new device generates a fresh Ed25519 keypair
- The existing device approves the link (you confirm a fingerprint match)
- The vault key is sealed for the new device's public key
- The new device pulls every encrypted item and decrypts locally
The new device never sees your passphrase. The existing device never exposes the unsealed vault key.
On the Existing Device
- Open Settings → Account → Devices
- Choose Link new device
- memrynote shows a QR code and a linking code — a long text string carrying the pairing data, meant to be copied, not typed by hand
- Keep this screen open
Only the newest code is live. Choosing Link new device again cancels any code you generated before it, so a device still holding an older QR code or linking string is told the session was cancelled and has to scan the new one.
On the New Device
- Sign in to the same email
- memrynote asks how to set up: Link to an existing vault vs Create a new vault
- Choose Link
- Either:
- Scan the QR code with your camera (if available)
- Paste the linking code (copied from the existing device)
If the Sign-In Times Out
The sign-in on the new device is only valid for a few minutes. If linking takes longer than that, memrynote tells you the sign-in timed out and asks you to sign in again and scan the code once more. Nothing is lost — generate a fresh code on the existing device and repeat the steps above.
If the Network Changes Mid-Link
Switching networks between scanning the code and finishing the link — Wi-Fi to cellular, or a network that hands out a new address on its own — does not interrupt linking. The link is proven by the scanned code itself, not by the network you scanned from. Older sync servers rejected the final step after a network change and required a fresh code.
Approval
The existing device shows an approval prompt:
- New device's name (auto-generated, editable)
- Public key fingerprint (visual hash)
- Platform (macOS / Windows / Linux)
Compare the fingerprint with what the new device shows. If they match, approve. The vault key is sealed for the new device and the new device starts pulling.
If something looks wrong, deny and start over.
Choosing What to Pull
If the account holds two or more vaults, the new device asks which ones to pull before it finishes linking:
- Pick a parent folder — each vault is created as its own folder inside it
- Check the vaults you want on this device
- Choose Pull selected
The first checked vault is the primary: memrynote creates its folder, opens it, and starts syncing right away. The rest stay cloud-only and show up under In your account in the vault switcher, where you can download them on demand.
If the pull fails — an unwritable folder, for example — the reason appears under the list and the choice stays available, so you can pick a different folder and try again without redoing the link.
Accounts with a single vault skip this step entirely.
Signing In Without Linking
You can also set up a second machine with just your email code and recovery phrase, without a linking code from the first device. The folder open on that machine then joins the vault your account already syncs — memrynote binds it to the account vault instead of registering the folder as a new one, so notes from both sides merge into one vault and sync starts immediately.
This matters on plans with a one vault limit: a second vault would be refused by the server, and sync would keep failing until the vault was switched by hand.
If your account holds several vaults, this path picks the largest one. Use the vault switcher (In your account) to download or open a different vault afterwards, and see Settings → Vault to check which vault the open folder belongs to.
Creating an additional vault stays a deliberate action from the vault switcher — signing in never creates one.
Signing In Again on the Same Device
A device that was already linked signs in again with just the email code (or Google), with no recovery phrase and no linking code. memrynote checks that the device still holds its keys, that the vault key on it still matches your account, and that your account still lists the device. The device keeps its place in the device list and picks up sync where it left off.
If any of that does not hold, for example after you revoked the device from another machine or after the app's data was wiped, memrynote asks for the recovery phrase or a linking code as before.
Losing the network does not sign you out. After sleep, on a flight or while DNS is still waking up, memrynote keeps you signed in and retries once the sync server can be reached. A keychain read that fails for a moment, or a refusal the server may still take back, is retried the same way and never asks you to sign in. That includes opening the app while the keychain is still locked: the sync icon keeps showing your last sync instead of "Sync disabled" until the keychain answers. You are signed out only when the server rejects the device's session for good.
Initial Sync Progress
After approval, the new device shows a sync progress screen:
- Notes downloading
- Tasks downloading
- Inbox items downloading
- Attachments downloading
For large vaults this can take minutes. The new device is usable as soon as the metadata pull finishes — attachments stream in the background.
Listing Devices
Settings → Account → Devices shows every linked device:
- Name (rename inline)
- Last seen
- Platform
- Public key fingerprint
When signed in, memrynote refreshes this list from the sync server so newly linked or revoked devices appear without waiting for another sync item to pull their keys. If the server is unreachable, the local cached device list remains available.
The iPhone app tells an iPad from an iPhone and draws each with its own icon. That works for an iPad or iPhone that signed in with a version that reports the device type. One that signed in earlier keeps the phone icon, and so does every iPad in the desktop app's list.
Revoking a Device
From the device list, click Revoke. Effects:
- The device's sealed vault key is removed from the server
- Future pulls from that device fail with auth errors
- The local data on that device is untouched (it's still readable until you wipe it)
Revoke when you no longer use a device. Revoke immediately if you suspect compromise — and follow up with a key rotation.
Revoking is not permanent for that machine: signing in again from it registers the same device anew and restores its access. To lock someone out for good, revoke and rotate your keys.
Lost Device
You cannot revoke from a device you don't have. Use any other linked device:
- Devices list → Revoke the lost device
- Recommended: Rotate keys to invalidate any sealed key copies that may have been exfiltrated
If you have only the lost device, restore on a new machine using your recovery phrase (see Recovery Key & Rotation).
Renaming Devices
Click a device's name in the list to rename. The name is local convenience — it doesn't affect security or sync.
Limits
An account can have up to 50 active devices. Setting up a 51st is refused until you revoke one: on a device that is signed in, open the Devices list and click Revoke on one you no longer use, then start setting up the new device again.
Large numbers of linked devices also increase the time to seal the vault key during rotation. Practically: keep your active devices and revoke the rest.