How Vaultxon browser tools handle local media, network requests, support email and browser data. This page describes the current browser-based release and its known limits.
Scope and current release
This policy describes the data paths for the current static Vaultxon workspace. The site does not require account registration. In the local file-picker workflows, selected media is read and processed by browser APIs; this release does not send those selected media bytes to a Vaultxon transcoding endpoint. The package does not include advertising or analytics tags by default. The published notice must be updated if the live site enables additional services.
This policy should be read with the Cookie Policy and the descriptions shown on individual tools. It does not control how a third-party source host, email provider, browser vendor or hosting provider handles information under its own terms.
Files selected for local processing
When you select a file, the page receives a browser File object and uses supported browser functions to read, decode, transform, inspect or preview it. The output is created in the browser and offered for download. Temporary Blob objects and object URLs may be used while the operation runs; these are not a permanent Vaultxon file archive and may be released when the page no longer needs them.
Your browser and operating system manage downloaded copies after you save them. Vaultxon cannot remotely remove a file saved to your device. For sensitive work, use a trusted device, avoid shared browser profiles and follow your own retention policy.
Direct-link requests and third-party code
The direct-link tool requests the URL you enter from the host that serves it. That host may receive your IP address, request headers, authentication state and other connection data, and its own privacy and logging policies apply. A browser may block a response because of cross-origin restrictions even where the URL opens in a separate tab.
When MP3 output is requested, the page loads the LAME encoder script from a content-delivery network. In that step, the script code is requested; the selected media file is not sent to that CDN by the encoder-loading step. The browser also requests Vaultxon HTML, stylesheets and JavaScript, and the hosting provider may process ordinary connection and security logs.
Server logs and operational information
Depending on the hosting and security configuration, routine server logs may include requested URLs, date and time, IP address, user-agent, referrer, response status and security events. The hosting provider controls the exact fields, retention period, access and deletion rules. Vaultxon does not claim that all network activity is private to the browser or that infrastructure logs never exist.
If you contact support, the team receives the email address and the information you choose to include. Please do not send passwords, login codes, confidential files or signed private URLs unless a safe and necessary process has been agreed. Email service providers may retain message metadata and copies under their own practices.
Cookies, advertising and analytics
The packaged release does not include Google AdSense, other advertising tags or site-owner analytics tags by default. The live site owner must verify the actual scripts, cookies, local storage and network requests before describing any service as active.
If Google AdSense is enabled, Google and its advertising partners may use cookies or similar technologies to serve, measure and limit ads, help prevent fraud, and—in accordance with user settings and applicable consent—personalize ads based on prior visits to this site or other websites. Google provides advertising controls through
Google Ads Settings and users can also review opt-out choices at YourAdChoices. Other vendors may use their own technologies and controls; the live policy should identify the ad technology providers actually enabled.
For personalized advertising to users in the EEA, the UK or Switzerland, publishers must use a Google-certified consent management platform integrated with the IAB Transparency and Consent Framework (TCF). Configure an eligible CMP and region-specific consent choices before enabling applicable advertising. See Google’s publisher CMP requirements.
When advertising, analytics or another third-party service is enabled, keep this policy synchronized with the real production configuration and applicable legal requirements. Do not enable scripts until the corresponding notices and consent controls are in place.
Your choices and data minimisation
Use the local file-picker workflow when it fits your task, avoid entering private URLs into the direct-link tool, and choose small non-sensitive test files when troubleshooting. You can close the page to end a typical local processing session, though downloaded copies remain under your control and ordinary server logs may be retained by infrastructure providers.
Privacy requests can be sent to support@vaultxon.com. Explain the relevant page or data flow without sending unnecessary personal information. Whether a request can be fulfilled may depend on whether the information is held by Vaultxon, a hosting provider, an email provider or a source host.
Children, updates and contact
The tools are general-purpose media utilities and are not designed as an account-based service for collecting children’s personal information. Adults should ensure that any use involving a child’s image, voice or personal data has a proper legal basis and appropriate permissions.
This policy may change when the code, hosting, advertising or other services change. The page’s review date identifies the published version. For privacy questions, write to support@vaultxon.com. The site owner should keep this notice consistent with the actual live network requests and local law.