ConvertZiva

Security

Security is part of the conversion workflow, not a badge.

The live image and PDF converters run locally in your browser with conservative file limits and no account requirement.

Browser-local processing

The live converters read selected files in the browser and do not upload them to ConvertZiva servers. This reduces unnecessary file transfer while still depending on the safety of the visitor's browser, device, and selected files.

Minimal data handling

The public site does not include accounts, payments, advertising trackers, or file-content analytics. Conversion events should remain anonymous and should never include filenames, file hashes, document text, image content, or private metadata.

Separate feedback text

Feedback is a separate server-side text feature. It records visitor-submitted feedback and tool context only; it does not receive converted files, filenames, file contents, PDF text, or image content from the converter workspace.

HTTPS and headers

Production traffic uses HTTPS. Security headers restrict object embedding, framing, broad browser permissions, and external connection origins while allowing the WebAssembly and worker behavior needed by current browser-local tools.

PDF handling

PDF to JPG uses PDF.js in a browser worker and Canvas output. Browser-local PDF editing uses pdf-lib, and Compress PDF uses qpdf compiled to WebAssembly. ConvertZiva does not render PDF-provided HTML.

File handling principles

Selected files are handled through browser file APIs, processed in memory, and downloaded from generated Blob URLs. Unsupported, encrypted, damaged, or oversized files show clear errors instead of being silently accepted.

Dependency maintenance

Converter libraries and production dependencies should be reviewed during release work, with high-severity advisories treated as launch blockers when they affect the shipped browser workflows.

Responsible claims

ConvertZiva does not claim perfect conversion, absolute privacy, certification, or specific uptime unless those controls are implemented, verified, and documented.