Local PDF work and online delivery are separate by design.

Local desktop processing

Opening, viewing, editing, form filling, page organization, OCR, redaction, comparison, compression, summaries and template operations are designed to run on the device.

Encrypted templates and secure packages

Reusable templates are encrypted with AES-256-GCM using operating-system-protected device keys. Password-protected KarmaPDF packages use AES-256-GCM with keys derived using scrypt. These packages are not a substitute for a standards-based PDF permissions system when another workflow requires one.

Explicit e-signature transmission

A document is submitted online only after the user deliberately creates a signature request, identifies recipients, places fields and confirms sending. Provider credentials remain server-side. Events and status are tracked for delivery and evidence.

Private signed-document repository

KarmaSigner account access is authenticated, repository requests are authorized server-side, and completed PDFs are stored in private object storage rather than exposed as public files. Each portal account is linked to its own active KarmaSigner plan before envelope history or completed documents can be retrieved.

Signed software

Windows installers are code-signed. macOS releases are signed and notarized. Customers should download only from karmapdf.com or an official platform store.

Responsible use

No software eliminates all risk. Organizations should apply their own access controls, retention schedules, backups and regulated-industry requirements. Report suspected vulnerabilities to security@karmapdf.com.