FAQ

Frequently asked questions

VaultCopy is intentionally narrow: make a verified local backup of a Mac vault, keep a copy on iPhone, and restore through a guarded path.

Is VaultCopy a sync product?

No. VaultCopy creates verified backup snapshots from Mac to iPhone. It does not edit notes on iPhone, merge changes, or mirror iPhone-side edits back to the Mac.

How is it different from sync, full-machine backup, or manual exports?

Sync tools keep files current. Full-machine backup protects a computer. Manual exports depend on your own routine. VaultCopy is for a different job: creating an intentional vault snapshot, verifying it, storing a local off-Mac copy on iPhone, and restoring it only into a new or empty folder.

Is VaultCopy affiliated with Obsidian or any sync provider?

No. VaultCopy is an independent product for local Markdown and Obsidian-style vault folders. Product names are used only to describe compatibility and user workflows.

Do I need a VaultCopy account?

No account is required for the local Mac-to-iPhone backup path.

Why does VaultCopy need a Mac Agent?

The iPhone cannot directly read arbitrary Mac folders. The Mac Agent has access to the vault folder you choose, creates the archive, verifies the snapshot, and pairs with your iPhone on the local network.

Does VaultCopy upload my notes?

No. VaultCopy does not upload your notes, backup archives, passphrases, pairing tokens, or restore packages to VaultCopy servers.

Can backups be encrypted?

Yes. Encryption is optional for new backups. If you enable it, keep the passphrase safe because old encrypted archives require the original passphrase.

What happens if I forget the backup passphrase?

VaultCopy cannot recover old encrypted snapshots without the original passphrase. Resetting encryption only affects future backups; it does not unlock old encrypted archives.

Will restore overwrite my current vault?

No. VaultCopy verifies the package first and restores only into a new or empty folder. This is deliberate: recovery should not destroy the working copy you are trying to protect.

How are Mac Agent updates delivered?

The Agent uses Sparkle 2 with the static appcast at `/appcast.xml` and the DMG at `/downloads/VaultCopy-Agent.dmg`.