Trust center
ConV is privacy-first infrastructure: keep agency, healthcare, legal, or public-sector media off surveillance-heavy cloud converters whenever your policies demand it.
Privacy is the product — not an afterthought.
ConV does not monetize image workflows via advertising trackers or file-based profiling. If optional analytics exist in a deployment, they are constrained to privacy-friendly tooling—never ad auctions tied to pixels you process.
Optimization jobs stay inside the browser sandbox. Servers route HTML, WASM assets, entitlement checks—not your pixel payloads.
EXIF, ICC, GPS, and other embedded payloads are rewritten or stripped before download, contingent on codecs and formats you choose.
You are no longer routing batch creative work through SaaS ingestion flows just to shave kilobytes. That aligns better with disciplined vendor lists.
There is nothing to warehouse on our disks for optimizer jobs—we never receive those binaries in this architecture.
Cards, invoices, refunds, and subscription status live in Stripe. Image processing binaries never piggyback on those payloads.
Web Workers isolate concurrency; WASM modules sandbox codec execution; memory stays ephemeral to the browsing profile you control.
ConV minimizes unnecessary transfers to image SaaS stacks. DPIAs still belong to your organization—we provide documentation instead of vague marketing claims.
Browser extensions, rogue profiles, DRM tooling, or OS policies can undermine any web workflow. Outputs should be validated whenever legal stakes are high.
Language deliberately cautious—individual vendors may vary. Procurement should validate each shortlisted service.
| Topic | ConV | Typical cloud converter |
|---|---|---|
| Image upload required | No upload | Usually yes for cloud converters. |
| Server-side image access | None for optimizer payloads | Typically yes. |
| Temporary cloud storage | Not used for optimizer bytes | Often unclear or vendor-specific. |
| EXIF / GPS handling | Stripped locally inside the workflow you trigger | Varies; may remain on vendor infrastructure. |
| Batch workflow | Yes | Yes |
| WebP / AVIF encode | Yes (codec dependent) | Yes |
| Sensitive workflows | Designed for teams that disallow cloud transfers | May still work, but procurement should review uploads. |
Straight answers sourced from architecture reviews—we still recommend counsel for binding opinions.
No. The optimizer runs in your browser. Image bytes stay in browser memory/workers unless you deliberately download outputs. Routine page loads send no image payloads to ConV.
There are no uploads to inspect in the optimizer flow. Operational staff operate the website and billing stack only; they do not receive your image files through the tool architecture described on this site.
ConV does not persist your source or optimized image files on its servers as part of the zero-upload workflow. Outputs exist on your device after processing when you save or download them.
Stripe handles payments and subscription status. ConV is designed so image processing is separate from checkout. Stripe does not receive your image files from the ConV optimizer workflow.
Many teams use local processing to reduce unnecessary transfers to third-party image services. ConV is designed to be GDPR-friendly, but it is not legal advice and does not guarantee compliance—your DPO or counsel should review fit for your case.
No. Metadata removal is performed locally on a best-effort basis and depends on file type, codecs, and browser capabilities. Critical workflows still require validation and documented processes.
Yes, when keeping assets off external compression clouds is preferred. Agreements with your clients still govern how you handle their data; ConV only provides the browser-local toolchain.
You can review the architecture and privacy materials, run the tool locally, and involve security or procurement as needed. Pilot on non-sensitive fixtures before production use.
In-memory jobs are discarded. Nothing is synced to ConV servers as part of optimization. Reloading starts a fresh session; download important ZIP outputs before closing the tab.
ConV does not monetize image workflows through ad networks. Optional privacy-oriented analytics may be configured per deployment—there is no ad-tech profiling tied to processing your files.