ConvertUnlimited

Trust Center

What the privacy build changes

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.

Removed from the privacy build

  • Ads: Ad provider scripts and ad slot scaffolding are removed from the generated privacy artifact.
  • Analytics: GTM, GA4, analytics-events.js, and file-operation telemetry are stripped or no-oped.
  • Remote runtime assets: Runtime CDNs and remote fonts are removed or replaced with same-origin vendored files.
  • Third-party script policy: The privacy build is audited for known third-party runtime script references.

What stays the same

The tools remain static browser pages. They still rely on the user's browser, CPU, memory, and supported APIs. The privacy build does not add server-side conversion, account storage, or a stronger device sandbox.

Deployment boundary

Trust topics

FAQ

Should I use the privacy build for sensitive files?

Yes, when the workflow is supported and browser/device limits are acceptable.

Does the privacy build include ads?

No. The generated privacy artifact removes ad scripts and ad scaffold DOM.

Does the privacy build send analytics events?

No. Tracking helpers are stripped or rewritten to no-ops in the privacy artifact.

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.