Back to Security Insights

Opening the same note on multiple devices without sync hell

No account means no “sync.” So how do you use the same note from your phone and laptop?

Inkrypt · Security Insights

We don’t have a “sync” feature in the cloud sense. The note lives at one URL; whoever has that URL and the password can open it. So “multiple devices” just means: open the same URL on each device and enter the same password. The server has one canonical version (the latest ciphertext we received).

Avoid editing in two places at once

If you have the note open on your phone and your laptop and you save from both, the last write wins. We do conflict detection: if the version we have is newer than what your tab had, we show a warning and let you overwrite or discard. So the workflow we recommend: edit on one device, save, then open on the other. No merge logic—just one source of truth.

Bookmark the note URL (or use Share to copy it). Use the same password on every device. That’s the whole model. No “sign in on this device”—just the link and the password.

FAQ: Same encrypted note on multiple devices

Q1. How do I open the same encrypted note on my phone and laptop?

Use the same note URL and password on each device. There’s no account or sync layer—just a single encrypted document reachable from multiple places.

Q2. What happens if I edit the note on two devices at once?

Last write wins. If the server has a newer version than your tab, Inkrypt will warn you and let you choose whether to overwrite or discard changes, but there’s no complex merge.

Q3. Do you store device-specific copies of the note?

No. There’s one canonical ciphertext on the server. Each device decrypts that same ciphertext with the password you provide.

Q4. Is this less safe than account-based sync?

It’s just different. You trade account-level convenience for a simpler, URL + password model with strict zero-knowledge properties and no global identity to attack.

Q5. How should I share a note across devices securely?

Bookmark or otherwise store the URL, and keep the password in a password manager. Don’t bundle the URL and password in the same, easily-forwarded message.

Where to go next

To see how this fits into the overall design: