Come ConV elabora le immagini senza caricamenti

Sezione 1 — Flusso senza caricamento sul server

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.

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.

Sezione 6 — Limiti

• 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.