Short answer
For supported processing flows, selected file contents are handled locally by your browser. The public site may load ads and analytics; the privacy build is the no-ads, no-analytics version for privacy-sensitive workflows.
ConvertUnlimited
For supported processing flows, selected file contents are handled locally by your browser. The public site may load ads and analytics; the privacy build is the no-ads, no-analytics version for privacy-sensitive workflows.
For supported processing flows, selected file contents are handled locally by your browser. The public site may load ads and analytics; the privacy build is the no-ads, no-analytics version for privacy-sensitive workflows.
For supported tools, selected file contents are processed locally in your browser using browser APIs and client-side JavaScript. ConvertUnlimited does not provide a server-side upload endpoint for those processing flows.
Local processing does not mean every browser or device can handle every file. Large files, unsupported formats, memory limits, and browser differences can still cause failures.
The public site at convertunlimited.com may load advertising, analytics, fonts, and other public-site services. These services can receive normal web request metadata such as IP address, user agent, page URL, referrer, and timing data according to their own service behavior.
Do not use the public ad-supported site for sensitive workflows if your requirement is no ads, no analytics, and no third-party runtime scripts.
The privacy build at privacy.convertunlimited.com is generated separately without ads, analytics, remote fonts, or third-party runtime scripts. It is the intended build for privacy-sensitive workflows and technical privacy review.
The privacy build uses a restrictive security header policy and is audited for third-party runtime requests as part of the deployment workflow.
Do not enter secrets, passwords, private keys, API tokens, or personal documents into tools unless you have verified the deployment behavior and are comfortable with local browser processing on your device.
Analytics events are designed to use tool metadata and not filenames, file contents, raw text, or document contents.