Elegant Vault copies your folders to a drive of your own and proves, file by file, that the copy arrived whole — and you watch it happen. And when the new drive arrives, the Move carries everything across, verifies it by reading the destination back, and hands you the receipt. A backup that runs in the background is a backup that fails in the background. The disk fills up, a folder loses permission, a file is in use, the cable falls out at three in the morning — and the program keeps saying "all good" until the day you need it. This product's rival is not the other backup program: it is silent incompleteness. Elegant Vault is the opposite of that. It shows the numbers before writing the first byte, it writes while you watch, and it ends with a seal that cannot be broken in half. WHAT IT DOES • A 1:1 mirror, readable without this program. The same relative paths, ordinary files, opened by any PC with File Explorer. There is no proprietary format, no container, no database in the middle. If this program disappeared tomorrow, your files would still be there. • Proof, not a promise. The SHA-256 fingerprint of every file is computed in the same pass as the write and recorded in a text manifest. Verifying means re-reading the bytes in the vault and comparing. The LEIA-ME.txt written at the root of the drive shows how to check by hand, with the certutil that already ships with Windows. • The mirror never deletes and never overwrites anything of yours. In the folders it mirrors, the program only reads. A file left over in the vault becomes a report line, never a deletion — and restoring brings the file back beside what is already there, with a suffix, never on top of it. • The numbers before the first byte. How many files go in, how many bytes, how long — and, with the same prominence, the list of what was left out, split into two buckets: refused on purpose, with the reason, and failed. Without that split, the denominator lies. • The seal is indivisible. At the end: "1,204 copied · 1,204 of 1,204 verified · 0 mismatches · 25 refused on purpose · 12 failed". The five numbers on the same line, always. A lone "0 mismatches" does not exist in this interface. • The 40-second rehearsal. The button that answers the question almost nobody asks in time: does your backup actually work? It draws files from the vault, brings them back into a temporary folder, checks the fingerprints, shows the result — and deletes only what it created itself. • A yanked cable is not a disaster. Every file is born with a temporary name, is pushed to the actual disk (not to the cache) and only then gets its final name. The manifest is always a prefix of reality: it never promises a file that did not arrive. Unplugging the drive mid-run is a pause, not an error. • Verify the whole vault, whenever you want. It is the gesture that finds silent media decay, and the estimated time is said before, not after. No scheduler and no resident process. • The vault's identity lives on the drive, not in the settings. A different drive letter, another dock, another PC, Windows reinstalled: the vault is still the vault. THE MOVE — THE OTHER MODE, FOR THE DAY THE NEW DRIVE ARRIVES • The Move has one verb more — yours. When you change drives, Vault copies, verifies by reading the destination back off the device rather than out of Windows' cache, closes the seal and hands you the receipt. Only then, if you ask for it, does it offer to release the source. It is not a ticked box, it is not a step along the way, and it does not run on its own: it is a screen that opens only after the seal. • And it only offers what it has proven three times, file by file. (1) it is in the seal, clean — copied and verified, with no mismatch; (2) the destination was read back off the drive and matched the manifest; (3) the source is still identical to what was read, checked in the second of the gesture. Failed one of the three? It stays, and it shows up named, with the reason. "412 of 415 can be released; 3 stay, and here is why." • Where there is a Recycle Bin, that is where it goes — and the number stays on screen. "The Recycle Bin lives on the SOURCE drive (D:). These 312 GB only come free once you empty it." Where there is none — a memory stick, an external drive, a memory card — the screen says out loud "there is no Recycle Bin here: this is permanent", shows the numbers, and requires you to type the word. In the permanent case the proof goes up a step: the source is read again and re-checked against the manifest before anything is let go. • The receipt sits on both sides, and neither side is hostage to the other. The full record of the move lives on your PC; next to the destination you get a copy of the CSV receipt and a LEIA-ME.txt that explains what they are — deleting both breaks nothing. WHAT IT DOES NOT DO (on purpose) It sends nothing to anyone's cloud. It asks for no account, no sign-up and no card to try it. It does not run in the background and it does not copy on its own: plugging in the drive with the program open opens the simulation, and copying waits for your click. This version also does not keep older versions of files, has no schedule and does not write to network drives (NAS): all three are still promised, still free, and are now the 2.x line — the Move went first because it has a date, and that date is the day the new drive arrives. The Move has no schedule either, and it never copies on its own. THE PRICE US$ 24.99 once — US$ 12.99 at launch. No subscription, no renewal and no feature that disappears when a monthly fee lapses. Fifteen days of trial, no card. And most important: restoring and verifying NEVER expire. When the trial ends without a purchase, the program keeps bringing your files back, forever. A backup that holds hostage the files of someone who did not pay is indefensible, and this one does not do that. Releasing a Move that is already sealed never expires either: a source held forever would be the same disease. Bought 1.0? 2.0 is yours, without paying again. It is the same one-time purchase. Native C#/.NET. Portuguese, English and Spanish, switched on the spot. Light, dark or automatic; classic or modern. Windows text scaling and "reduce motion" respected. KNOWN LIMITS (we prefer to say it first) Verification proves that the vault equals what was read — it does not prove that the read was correct. If the memory or the cable at the source was already corrupting the data, Vault faithfully copies and verifies a corrupted copy. Detecting media decay is also not repairing it: the program says which files diverged and leaves the decision to you. A single copy, kept next to the source, does not protect against fire, theft or a lightning strike — keep more than one, in more than one place. Files in use, without permission, that exist only in the cloud, or whose name is impossible on the destination file system are left out, and they show up named, one by one, in the two lists. And there is no automation that copies on its own: neither scheduled nor from a command line. In the Move, what leaves the source goes to the Recycle Bin of the SOURCE drive when it has one — and whatever does not fit its quota, Windows deletes for good, which the receipt records. A source on a network drive stays untouched: the release is done on the server. And verification reads off the device, not out of Windows' memory — what no program reaches is the cache inside your own USB enclosure's firmware.