Sync behavior

GitVault is local-first. You can use the vault locally, and sync uploads encrypted changes to GitHub when enabled.

What sync moves

• Vault items Passwords, notes, TOTP entries, and SSH credentials are encrypted before upload.
• Device registry Trusted devices and device alerts are synced so web and Android see the same trust state.
• Recovery records Recovery requests and approvals are stored as encrypted coordination data.

When sync runs

1. 1
   Manual sync.

   Use Settings when you want an immediate check after important edits.

2. 2
   Auto-sync.

   When enabled, GitVault periodically checks for local and remote changes at the configured interval.

3. 3
   App open checks.

   GitVault can check device trust when the app opens so removed devices clear local sync access quickly.

Conflict handling

GitVault uses smart sync with last-write-wins behavior. If the same item is edited on two devices before either device syncs, the newest synced item version wins.

Deletes

Deleted records are tracked with tombstones so a deletion can propagate to other devices instead of being recreated by an older local copy.

Device trust checks

If a device is removed from Connected Devices, it is no longer trusted after the change syncs. When that removed device next opens or performs a trust check, GitVault clears local sync access and requires Link New Device or recovery before it can access synced data again.

Performance habits

• Keep tokens narrow One small private repository is faster to scan and safer to authorize.
• Use reasonable intervals Very frequent sync checks can cost battery and GitHub API quota on mobile.
• Sync after large edits Manual sync after bulk changes reduces surprise on other devices.