Your originals stay put.
The app reads the source you choose. Its backup operation does not move or erase source files, and it has no mirror-delete mode.
TRUST IS EARNED
A safe copy starts
with clear promises.
Preserve your originals. Keep earlier backup contents. Say clearly what has—and has not—been verified.
Earlier copies stay available.
Matching content can be reused. Changed bytes are stored separately, with manifests that record original filenames. Existing destination content is preserved.
Verification has a meaning.
Checksums compare bytes. For a mounted cloud folder, local verification alone does not prove remote upload. The interface keeps that uncertainty visible.
Account access belongs to you.
Direct Box and Dropbox connectors use official authorization. The app stores tokens in macOS Keychain and does not ask for your cloud account password. Production sign-in remains unconfigured.
PRIVACY, IN PLAIN LANGUAGE
What goes where.
On your Mac
Saved plans, folder permissions, staging data, run receipts and recovery manifests are stored locally. Records may include the folder names and paths needed to identify a backup.
At your chosen destination
Backup bytes and their manifests go to the supported storage you select. Its access controls, service terms and retention policies apply.
At the sign-in service
The planned Box broker handles short-lived authorization data and token exchange. Backup files do not pass through it. Hosting and operational controls must be validated before launch.
On this preview
No analytics, advertising trackers, payment processing or data-submission forms are included in the website code. The hosting service handles page requests and access authentication.
This is a development disclosure, not a final privacy policy.
Publisher contact information, service operators, retention details, support handling and final privacy and license documents must be completed before public release. An independent security review remains outstanding.
Recovery matters,
even when nothing moves.
If a source drive is lost or damaged, a backup needs to yield usable files. The app’s recovery command creates a new folder and checks copied bytes; it refuses to replace an existing folder.
Controlled local and simulated cloud checks have passed. Real cloud recovery and clean-Mac validation are still required. Keep your established backup process until those release gates are met.
See completed and remaining checks →