Elegant Vault copies, verifies and restores files locally. Your files, paths, manifests and SHA-256 fingerprints stay on your devices and are never sent to ElegantFE.
Elegant Vault copies your files from a folder of yours to a drive of yours, and none of it passes through us: there is no server, no cloud, no account, and the app has no network client inside it.
That sentence is not a marketing promise — it is verifiable. The product's code contains no HttpClient, WebClient, Socket or TcpClient anywhere, and an automated test fails the build for anyone who adds one. The only network trip that exists is the Microsoft Store one, performed by Windows itself, and it is described below.
Elegant Vault has two modes, and the difference between them is as much a privacy matter as a functional one. The verified mirror reads the folders you chose as sources and writes a 1:1 copy to the destination drive. The Move is the crossing you make on the day you change drives: it copies, verifies by reading the destination back, closes the seal, hands you the receipt — and only then, and only if you ask, offers to release the source folders.
Elegantvault.json (the vault's identity), LEIA-ME.txt (trilingual, with four instructions for recovering the files without the app), and the JSONL manifest, carrying the relative path, size, date and SHA-256 fingerprint of every copied file.LEIA-ME.txt explains how to check them by hand.We do not collect, do not receive and have no way to see:
There is no analytics. No ads. No trackers. No user profile. No sign-up. There is no "send diagnostic data" — neither on nor off, because the feature does not exist.
The app is sold through the Microsoft Store, and the Store needs to know whether you bought it. Those queries are made by Windows, through the Windows.Services.Store API, and are the only connections related to the product:
| When | What happens | What travels | |---|---|---| | On opening the app | License and trial period query | The product's Store identifier and your Microsoft account, handled by Windows | | On opening the purchase screen | Windows opens the Store purchase sheet | Payment data, handled by Microsoft — the app never sees it | | If you accept the rating invitation | Windows opens the rating dialog | Your rating, handled by Microsoft | | Updates | The Store updates the app | Nothing of your content |
None of them transmits content, names, paths or metadata of your files. The app does not choose what to send because it is not the app that sends: it asks Windows "does this person have a license?" and receives yes or no.
And the error always favours the person using it. If the Store does not answer, if this Windows has no Store app installed (LTSC editions, N editions, corporate images) or if the license file is unreadable, Elegant Vault unlocks access instead of locking it. A licensing problem must never become a backup that does not happen or a file that does not come back.
There are also two https addresses the app may hand to Windows to open in your default browser: the product page on the Store and the rating invitation, and only when you click. The app does not fetch those pages — in that case, what talks to the internet is the browser you chose.
Everything below lives on your disk, under your user account, and can be deleted by you at any time. Deleting any of these files loses no file in the vault.
Application data folder — %AppData%\ElegantVault
| File | What it is | Personal data? | |---|---|---| | settings.json | Preferences: language, theme (light/dark/auto), shape (classic/modern), text scale, reduce motion, whether the simulation opens when the drive is plugged in, and a hint of the last vault opened | Contains the path of the last vault and a random identifier for this installation (a GUID). Both stay on your PC and are never sent | | catalog.db | A disposable SQLite cache of your vaults, so the desk can show them with the drive unplugged: root names, counts, dates. Fully rebuildable from the destination itself | Contains paths and counts. Never leaves the PC. Deleting it costs a re-read, never a file | | app.log | Local technical diagnostic journal | May contain file paths and Windows error messages. It stays on your PC; it is not sent anywhere and is never read by us | | spill\<run>\ | Temporary enumeration files of a run in progress, deleted by the app itself when it ends | Paths, temporarily | | mudancas\<session>\ | NEW in 2.0 — the durable record of every Move. Three files: ledger.jsonl (what was copied and verified, line by line), recibo.csv (the same thing as a spreadsheet) and a LEIA-ME.txt. When you release the source, a recibo-liberacao.csv joins them: what left, where it went and the date | Contains paths of files of yours, sizes and SHA-256 fingerprints, and the date of the release. It stays on your PC, forever until you delete it, and is never sent. Deleting it undoes nothing and breaks nothing — it is a record, not an index |
Why the Move's record is durable, said before anyone discovers it. Releasing the source is the only irreversible thing this product does, and an irreversible verb without a record is a verb with no witness. The record is what answers, on any future day, "what exactly left this drive, and when" — which is why it does not delete itself after N days. It is yours: it lives on your computer, it is readable text, and you delete it whenever you like.
Shared Elegant suite folder — %LOCALAPPDATA%\Publishers\<publisher>\ElegantSuite\vault\v1
The Elegant suite apps (Explorer, Paper, Photo, Vault) share a local folder — provided by Windows itself, on your computer — so they can recognise each other without needing a network. Elegant Vault writes two files there:
coverage.jsonl: which roots of a vault are protected, with the date of the last verification, so that a sibling app may one day show that information.That folder is local, it never leaves the computer, and it is removed when you uninstall the apps. No suite app needs the others: if no sibling is installed, the feature simply does not appear.
On the vault drive, the app writes the copy of your files and the three artefacts already described (vault.json, LEIA-ME.txt and the manifest). They are yours, they are readable text and they have nothing of ours inside.
At the destination of a Move, it writes a derived copy of the record: that session's manifest, a recibo.csv and a LEIA-ME.txt. That receipt contains the list of your files' paths, and it stays in that folder after the program closes — that is a privacy fact, and it is written here before anyone finds it. The folder is yours: deleting both files breaks nothing, and the authoritative record stays on your PC.
Apart from the folders above and the destination drive you chose, the app writes in one other place only: the folder you point to as the target of a restore — and even there it never overwrites. By default the restored file is born beside the existing one, with a suffix, or in a new folder.
They remain yours and entirely under your control. In the mirror, the app reads the source and never writes to it. In a Move, and only after you confirm on a screen that opens after the seal, it may send to the source drive's Recycle Bin the files it has proven to be whole at the destination — with the date of that recorded in the receipt kept on your PC. We have no access, no copy, and no way to recover or hand to third parties something that never leaves your computer.
The app is not directed at children and collects no data from anyone — of any age.
Since we do not collect, store or process any personal data of yours, there is no database of ours from which to request access, correction, portability or erasure. Purchase and account data stay with Microsoft, under Microsoft's own privacy policy, and requests about them should be directed there. Everything the app writes is on your computer and you delete it whenever you want.
Substantial changes will be published on the product's Store page and in this file, which ships with the app, always with the version date. The rule that does not change: if the product ever starts sending anything anywhere, that will be said here, first, and before it happens.
contact@elegantfe.com — or the support channel on the product page on the Microsoft Store.