CV
Start free

Architecture

How ConV processes images without uploads

ConV runs image optimization locally in the browser using WebAssembly and Web Workers. Your image files are never transferred to ConV servers.

Section 1 — Zero-upload data flow

Files you add in the optimizer are decoded and re-encoded entirely inside your browser tab. Workers coordinate tasks; codecs run as WebAssembly. Packaged ZIP archives are assembled locally before download.

User device
Browser memory
WebAssembly codecs
Web Workers
Local ZIP export
  • No server upload
  • No image storage
  • No image transfer
  • No cloud conversion

Section 2 — What ConV servers can see

  • Billing and licensing requests routed through Stripe and our server-side entitlement checks.
  • Basic HTTP requests when you load pages or call authenticated APIs.
  • Optional privacy-friendly analytics, only if explicitly enabled for a deployment.

Section 3 — What ConV servers cannot see

  • Image pixel data from optimizer jobs.
  • In-browser previews or thumbnails generated for the UI.
  • EXIF or GPS payloads from your files.
  • Optimized output blobs before you download them.
  • Filenames from the optimizer pipeline (they stay local unless you voluntarily share elsewhere).

Section 4 — Local processing components

WebAssembly modules host trusted codecs off the UI thread while Web Workers schedule parallel jobs. Intermediate buffers stay in RAM you control; ZIP archives are emitted without round-tripping image bytes through ConV infrastructure.

Section 5 — Billing separation

Stripe processes payments and recurring subscriptions. Session checks validate whether a billing relationship exists—they do not include image payloads. Image optimization never depends on transmitting files to Stripe.

Section 6 — Security limitations

  • Browser vendors, extensions, malicious software, or policies on corporate devices may affect runtime behavior.
  • Metadata stripping is best-effort and cannot be warranted for every format variant.
  • You remain responsible for verifying outputs in regulated contexts.
  • ConV does not provide legal advice; involve counsel for contractual or statutory obligations.

Technical buyer FAQ

Straight answers procurement, IT security, or data protection reviewers usually ask.

Are images uploaded to ConV servers?

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.

Can ConV employees access uploaded files?

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.

Does ConV store optimized images?

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.

Does Stripe receive image data?

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.

Is ConV suitable for GDPR-sensitive workflows?

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.

Does metadata stripping guarantee legal compliance?

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.

Can agencies use ConV for client images?

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.

Can public-sector teams evaluate ConV?

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.

What happens if the browser tab is closed?

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.

Does ConV use advertising trackers?

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.

Open the optimizerRead the privacy policy