Cloud Sync
Cloud sync is currently experimental for v1. The encrypted sync engine and sync server exist, but Notidian should not be described as fully shippable sync until the manual two-client QA pass in #647 is complete.
If you use sync now, keep an independent backup of your vault.
Public-beta access and storage
During the public beta, available Pro features are free for everyone. There is no checkout, paid sync entitlement, or trial in the client, and beta access does not change because of a build, date, version, or sign-in state.
Managed Sync is separate from Pro and is intended to be available to Free or Pro customers: €12/year for 10 GB total or €24/year for 100 GB total. Pro includes no hosted storage, and neither future Sync plan is provisioned for beta. The server’s current fallback quota is 1 GiB, with active per-account overrides; Settings → Sync is the source of truth for the limit on an account. See Plans & Public Beta.
Cancelling future Sync must not revoke purchased Pro or affect local files, free local editing, and basic export. Cloud-data retention, download grace, and deletion rules are not settled yet and must be defined before paid launch; cloud retention will not be infinite.
Current status
Notidian’s current sync path is the Notidian encrypted sync server, not Google Drive/iCloud/OneDrive direct sync.
| Area | Current v1 status |
|---|---|
| Private vault sync | Implemented as encrypted single-account, multi-device sync |
| Encryption | Master key derived locally; server stores encrypted manifests and blobs |
| Manual sync | Available from Settings → Account / Sync engine → Sync now |
| Automatic triggers | Save/local-change events, auth unlock, and focus regain can request a sync pass |
| Conflict handling | Newest settings file wins; other unresolved edits keep a conflict copy |
| Polished conflict UI | Not implemented yet |
| Manual QA | Pending #647 before final v1 decision |
| Sharing/collaboration | Not part of this sync surface |
How sync works
- You sign in to a Notidian sync account.
- The app unlocks your local encryption key material on this device.
- A sync pass compares the local vault with the encrypted server manifest.
- Changed files are encrypted locally and uploaded as ciphertext blobs.
- Missing remote files are downloaded, decrypted locally, and written to the vault.
- Deletes are tracked with tombstones so another device can remove the same file safely.
The server should not be able to read note contents or paths.
Conflict handling
When workspace settings (settings.json) or keyboard shortcuts (keybindings.json) are edited on both devices, the file with the newer modification time replaces the whole older file. On a tie, the synced version wins. Notidian does not merge individual settings or create a conflict copy. Old settings conflict copies are hidden in File Explorer, not deleted.
For other unresolved same-path edits:
- Notidian keeps the local file at its original path.
- The remote version is downloaded and written beside it as a
name.conflict-<timestamp>.extfile. - Settings shows a conflict count.
- You must manually compare, merge, rename, or delete the conflict file.
There is no in-app diff/merge/resolve workflow yet. That is the biggest UX limitation before sync can be called stable.
What still needs manual QA
The v1 decision depends on #647 covering realistic app flows, especially:
- Sign-in, sign-out, expired session, and understandable auth failure states
- Two different accounts proving data isolation
- First sync from an existing local vault
- Fresh client download/rehydration from existing server data
- Two-client create/edit/delete/rename flows
- Attachments/blobs and larger vaults
- Offline edits followed by reconnect
- Same-note conflicts and delete-vs-edit conflicts
- Server outage or partial upload/download failures
- Recovery without duplicated or erased local data
Possible v1 decisions
After #647, sync should be explicitly labelled as one of:
- Experimental beta — if manual QA finds no release-blocking safety issues
- Hidden/opt-in — if core flows work but the UX/recovery story is not ready by default
- Deferred/post-v1 — if there are data-loss, account-isolation, auth, or unrecoverable failure concerns
See docs/V1-SYNC-DECISION.md in the repo for the release-note wording options and decision brief.