Livre blanc — Sécurité et confidentialité

Architecture overview

ConV loads WebAssembly codecs and schedules work on Web Workers while the UI thread stays responsive. Encoded outputs and optional ZIP archives assemble without round-tripping through ConV-backed object storage for the optimizer workflow.

Privacy model

The product is built for European and privacy-sensitive buyers: fewer third parties touch your pixels compared with typical cloud converters. That does not imply legal certification—map our documentation to your DPIA or TOM requirements.

Data flow narrative

User selects files → browsers read bytes into RAM → WASM decodes/encodes → optional metadata strip → downloadable artifacts. Network calls to ConV cover pages, entitlements, optional analytics—not image streaming.

Metadata handling

Stripping leverages the same local pipeline. Unsupported edge cases may remain—engineers should spot-check critical files.

Billing separation

Stripe processes card data and subscription lifecycle events. ConV servers may cache entitlement decisions but not image blobs from the optimizer workflow described here.

Technical limitations

Browser security posture, device memory, codec bugs, or extensions can change outcomes. ConV does not promise universal metadata eradication or uninterrupted availability.

Suggested internal review checklist

• Confirm local-only processing satisfies your data processing agreements.
• Document which browser versions are approved for production use.
• Align outputs with creative QA and accessibility reviews.
• Retain counsel for GDPR, sectoral rules, or contractual clauses.