ConvertUnlimited

Trust Center

How to verify local processing

Trust claims should be testable. You can inspect the Network panel, run the privacy build audit, and run the no-network processing test against representative workflows.

Short answer

Open DevTools before selecting a file, clear the Network log, run the tool, and confirm processing does not create third-party or upload requests. For repository verification, run npm run verify:privacy.

Build boundary

The public site may load ads and analytics. The privacy build at privacy.convertunlimited.com is the no-ads, no-analytics review target.

Verification path

Use the verification page, browser DevTools, and repository privacy tests to inspect the behavior instead of relying on marketing language.

Browser DevTools check

  • Open a clean browser profile: Use privacy.convertunlimited.com and disable browser extensions if possible.
  • Open Network panel: Enable Preserve log and disable cache before selecting a file.
  • Process a sample file: Run the workflow and watch for new requests.
  • Review requests: Expected requests should be same-origin static assets, data URLs, or blob URLs. Third-party analytics, ads, or file uploads should not appear.

Repository checks

The repository includes static and runtime checks for the privacy artifact. The static audit scans for known third-party runtime references. The runtime test blocks common network APIs while exercising representative processing flows.

npm run build:privacy
npm run audit:privacy
npm run test:privacy-network
npm run verify:privacy

Related proof page

The existing proof page summarizes the privacy artifact, verification command, network isolation model, and threat-model limitations.

Trust topics

FAQ

What should I look for in the Network panel?

Look for unexpected upload, analytics, ad, CDN, or beacon requests during processing.

Does a clean Network panel prove all security properties?

No. It verifies a narrow behavior: whether the tested processing flow caused network requests.

Can browser extensions affect the result?

Yes. Extensions can inject scripts or inspect page data depending on their permissions.

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.