VaultSync 2.0.2

[2.0.2] — 2026-08-27

Privacy

• The Privacy Policy now describes optional Controlled Diagnostics as available in VaultSync 2.0.0 and later (#149) — the correction keeps pairing and checks explicit, confirms that ordinary or background sync does not start them, and preserves the existing retention and physical-device evidence limits.

Fixed

• Cloud Relay no longer continues from malformed saved Relay device IDs (#161) — VaultSync reports that Cloud Relay provisioning did not complete and sends no provisioning request, without rewriting or deleting the stored value. Valid existing JSON and legacy records remain unchanged.
• Push and Cloud Relay registration details now survive failed secure-storage updates (#148) — VaultSync keeps the last valid value when a replacement cannot be saved and reports the failure instead of continuing as if registration succeeded.
• Folder access now stays intact when reconnecting or syncing in the background (#147) — reselecting the same Obsidian folder no longer accumulates access claims. Switching folders takes effect only after the new location is readable, scanned, and its permission is saved; any failure keeps the previous folder connected. Background runs release only their own access on completion, restart, or cancellation.
• Background sync no longer reports unfinished work as completed (#146) — continued processing now reports success only after every expected vault is confirmed fully idle. If the sync engine stops, vault status cannot be read, a vault reports an error, the run expires or is cancelled, or the app returns to the foreground, the background run reports failure instead; conflict checks happen only after idle is proven.
• Conflicting Obsidian settings now wait for your decision (#145) — VaultSync no longer automatically deletes, replaces, or promotes .obsidian conflict copies by modification time. The legacy preference stays stored but cannot re-enable the retired behavior, and detected conflicts remain visible for manual review. Syncthing's separate conflict-copy retention is not guaranteed.
• Keep Both no longer overwrites an existing conflict copy (#144) — when the intended copy name is already occupied, VaultSync leaves all existing files untouched instead of replacing previously saved bytes.
• Manual conflict resolution preserves unrelated temporary files (#143) — choosing the conflicting version no longer reuses or overwrites a pre-existing temporary file next to the note.

Security

• Updated the Go runtime used by the sync engine and self-hosted helper — Go 1.26.5 → 1.26.6 incorporates the latest standard-library security fixes. Future iOS archives and helper releases are built with the patched runtime.