Short answer
Build boundary
Verification path
Use the verification page, browser DevTools, and repository privacy tests to inspect the behavior instead of relying on marketing language.
Trust Center
ConvertUnlimited Trust Center
ConvertUnlimited uses browser-native processing for supported utility workflows. This Trust Center explains what runs locally, what the privacy build changes, how network isolation is verified, and where browser or device limits still apply.
What this Trust Center covers
This section documents the technical trust model behind ConvertUnlimited. It separates public-site behavior from privacy-build behavior and avoids broad claims that cannot be verified from the page itself.
The main trust boundary is the browser tab. Supported tools use browser APIs, local JavaScript, Canvas, Web Crypto, and vendored client-side libraries to process selected files without a server-side upload endpoint for those processing flows.
Where to start
- Local processing
How browser-native file processing works and when uploads are not required. - Privacy build
What changes on privacy.convertunlimited.com compared with the public site. - Verification
How to inspect network behavior and run local verification tests. - Limitations
What browser-native processing does not protect against.
Trust topics
FAQ
Is the public site the privacy-reviewed build?
Does every workflow run without upload?
No. Trust claims are scoped to supported local-processing flows. Pages should state when browser support or device limits apply.
How can I verify the behavior?
Use the verification guide, browser DevTools Network panel, and the repository privacy tests before processing sensitive files.
Review note
Trust documentation reviewed: May 2026. These pages describe the current public and privacy-build architecture and should be updated when deployment, telemetry, or runtime dependencies change.