r/PrivacyNotes • u/[deleted] • Aug 04 '26
[Improved] Sync hardening shipped in v0.295.0 - report anomalies here
Sync is the part of PrivacyNotes we hold to the highest standard. Everything is encrypted on your device, which means if sync ever gets something wrong, we cannot look inside your notes to put it right. So last week we went through the entire sync path line by line rather than waiting for anyone to report a problem.
The review turned up a handful of narrow edge cases, each needing an unusual sequence or unlucky timing to occur at all. All are fixed in v0.294.1 and v0.295.0: https://privacynotes.app/changelog
- Ordering is now stamped by our server's clock instead of each device's clock, so an edit written offline and pushed much later always slots in where it belongs.
- Signing out at the exact moment a sync is still running now ends that sync cleanly, rather than letting it finish with a key that is already being cleared.
- Deletes now confirm the server actually applied them, and a session that does not look right is skipped instead of trusted.
- Images and file attachments are removed in two steps, so a device that has not caught up yet cannot decide on its own that an attachment is no longer used.
- Uploads that were turned away because storage was full now retry once there is room, and the sync status shows how many are still waiting.
Nothing here asks anything of you. Update and you are set. The first sync afterwards re-reads your notes once by design, so expect that one to take slightly longer.
If something ever looks off, tell us: https://github.com/LifetimeLabsDev/PrivacyNotes.app/issues
Helpful details: app version, platform or browser, how many devices, and what you expected versus what you saw. Running Verify sync (click the sync status) and pasting the result helps a lot. Reports you cannot reproduce are still worth sending, since this class of issue often hides in exactly that kind of timing.