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 is a local file-copying and verification app. It reads folders you choose and writes copies to a destination drive you also choose.
ElegantFE does not receive your files, operate servers that store them, provide cloud storage, require an account, use advertising or behavioral analytics, or automatically receive crash reports or diagnostics. The app has no network client of its own. Internet-related operations are performed by Windows or external apps, mainly for Microsoft Store licensing, purchase, rating and updates. Automated project checks also prevent common network clients from being introduced into the app.
To work, Elegant Vault locally accesses and processes:
This processing happens on your device. ElegantFE does not receive this data or have remote access to it. The vault contains the copied files and local documents such as vault.json, LEIA-ME.txt and manifests recording relative paths, sizes, dates and fingerprints.
Elegant Vault does not send ElegantFE files or file fragments; names, paths or drive letters; fingerprints or manifest contents; the number or contents of vaults; copy, verification or restoration history; IP address or location; advertising identifiers; contacts, photos, audio or video; browsing data; usage telemetry or session statistics; automatic crash reports; or profiling information.
There are no ads, analytics tools, trackers or proprietary account mechanisms in Elegant Vault.
App data is normally stored in %AppData%\ElegantVault. If unavailable, a corresponding folder in %TEMP% may be used temporarily.
Elegantsettings.json — language, theme, visual style, text scale, reduced-motion preference, known-drive simulation preference, a random installation identifier, the last vault identifier and path hint, and Elegant suite integration preferences. These remain on the computer.license.dat — local trial and licence state, such as first-use date and purchase indication.catalog.db — a disposable local SQLite catalog of known vaults, which may include identifiers, paths, root names, counts, dates and technical states. It contains no copy of file contents and can be rebuilt from the vault.Technical logs. %AppData%\ElegantVault\logs\app.log may contain date and time, error type, Windows or app messages, technical context, stack traces and sometimes paths involved in a failed operation. It deliberately excludes file contents, is size-rotated and is never sent automatically. Review it before manually sharing it with support because operating-system messages may include paths, user names or file names.
Temporary files and local receipts. Enumerations, simulations and checks may create work files, segments, receipts or run records containing paths and metadata needed to finish, resume or document an operation. They stay on the device.
Manual reader. The integrated WebView2 component may create cache and technical data in %LOCALAPPDATA%\ElegantVault\webview2. The manual is embedded in the app; its internal address is fictitious, is not resolved online, and external navigation is blocked.
At your chosen destination, Elegant Vault may write file copies, the vault's local identity, recovery instructions, manifests, relative paths, sizes, dates, SHA-256 fingerprints, run records and receipts, requested reports, and temporary files needed for safe writes.
This data belongs to you and remains where you put it. ElegantFE neither receives, hosts nor controls the vault. Uninstalling the app does not delete vaults; those files remain until you remove them.
When you request a restore, Elegant Vault reads the vault and writes files to your chosen restoration folder. Rules prevent silent overwriting; with your approval a file may receive an alternate name or suffix, or be restored to a new folder. Restored files are never sent to ElegantFE.
Elegant Vault may share limited local information with other Elegant apps from the same publisher through a Windows-managed folder similar to %LOCALAPPDATA%\Publishers\<publisher>\ElegantSuite\vault\v1.
It may publish a presence stamp (app name, version, product identifier, compatible protocol and update date) and coverage.jsonl, a local projection of protected roots and their coverage or verification information. This lets compatible suite apps recognize Vault locally. The folder is available only to packages under the same publisher identity and is not a cloud service. Nothing is sent to ElegantFE, and the integration is not required for Vault's core operation.
The Store version uses Windows.Services.Store APIs to query licence and trial state, price and purchase availability and, when requested, to start a purchase or rating. Microsoft may process the Microsoft account, product identifier, licence state, Store country or region, currency and local price, purchase and payment information, your rating, and information needed to download and update the app.
Microsoft processes this data under its own terms and privacy statement. Elegant Vault does not receive full payment details, only operational results such as licence state, displayed price or purchase-request result. Store calls occur only with package identity. If the Store is unavailable or a licence query fails, Vault uses a fail-open policy rather than blocking access because of an unknown state.
For purchase, rating, update or product-page requests, Vault may ask Windows to open Microsoft Store or, as a fallback, your default browser on Vault's Store page. Vault only hands the address to Windows; the Store or browser then operates under its own privacy policy and settings. Vault may also open File Explorer or a compatible Elegant app for a local operation.
This policy is also published at elegantfe.com/privacy-vault. This section is about the WEBSITE only — the app itself still has no telemetry whatsoever.
The website is a static presentation page hosted by a third-party hosting provider. It uses Google Analytics to measure audience in aggregate (which pages are visited and where visits come from), which may involve Google cookies and identifiers — see Google's privacy policy for details. We do not use this data to identify you, we do not sell data, and there are no other third-party pixels. Your browser also stores your language preference (in localStorage), which stays on your device, and the hosting provider keeps its own access logs, as any web server does, under its own privacy policy. When you arrive, a discreet notice lets you accept measurement or stick to the essentials, and you can change your choice at any time.
ElegantFE does not sell, rent or trade personal data processed by Elegant Vault, nor share files, names, paths, manifests or usage information with advertisers, data brokers or analytics platforms because that information is not transmitted to ElegantFE. Store interactions are processed by Microsoft; Elegant suite integrations remain local as described above.
You control retention. You can remove app preferences and logs by deleting its data folder; WebView2 cache by deleting its local folder; catalogs and temporary files by deleting the corresponding local files; vaults, copies, manifests and reports from the chosen drives; and restored files from the restoration folder.
Close Vault before deleting its data folder. Removing preferences, catalogs or logs may reset settings and local technical history, but should not delete files already in a vault. Uninstallation may remove package-managed data but does not necessarily remove files written to user-selected folders or drives.
Vault uses Windows file-access mechanisms and account permissions. Its Win32/WPF package declares runFullTrust to access folders and drives you select; it declares no specific camera, microphone, location, contacts or personal-library capabilities.
SHA-256 fingerprints verify integrity but are not encryption. Vault does not claim to encrypt vault contents. To protect against physical access or other authorized computer accounts, use Windows and drive protections such as file permissions, BitLocker, device encryption and account protection.
You are responsible for protecting your Windows account, controlling physical drive access, keeping additional copies when needed, checking source, destination and restore locations, and securely removing data you no longer want.
ElegantFE makes no international transfer of Vault files or local data because they are not sent to the company. Microsoft may process Store, account, purchase, rating and update data in different countries under its own infrastructure and privacy policy.
Vault is not specifically directed to children and has no registration, behavioral advertising or proprietary profiling collection. ElegantFE does not attempt to determine users' ages. Guardians should supervise children's use of the computer and storage drives.
ElegantFE has no remote database of Vault files, paths, manifests, preferences or usage history. Access, correction, portability or deletion of local data must therefore be performed by you on the computer and drives where it resides. Requests concerning a Microsoft account, purchase, payment, licence, rating or Store history should go to Microsoft. If you voluntarily sent information to support, contact ElegantFE about that interaction, subject to applicable legal duties.
This policy may be updated to reflect changes in the app, law or services. Material changes will be published with a new effective date. If a future version transmits data that currently stays only on the device, that change will be clearly disclosed before or when the new processing starts.