Trust Center

What the privacy build changes

The privacy build is a generated deployment artifact for privacy-sensitive workflows and privacy review. It removes ads, analytics, remote fonts, Google services, Cloudflare Insights, and third-party runtime scripts from the app artifact.

Short answer

Use privacy.convertunlimited.com when you want the tracker-free ConvertUnlimited build. The public site remains ad-supported and is not the review target for no-ads/no-analytics claims.

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.

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

privacy.convertunlimited.com is deployed separately from the ad-supported public site. Cloudflare Web Analytics, Zaraz, Rocket Loader, email obfuscation, and other runtime script injections must remain disabled for the privacy hostname.

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.