Vendor Security, Data Custody & Network Audit Brief

Technical memorandum for Chief Information Security Officers (CISOs), IT Administrators, and Compliance Officers evaluating Papryx Desktop for corporate deployment.

1. Core Execution Model: 100% On-Device

Unlike cloud-hosted SaaS PDF services (e.g., Adobe Document Cloud, Smallpdf, iLovePDF) that ingest documents onto multi-tenant remote clusters, Papryx Desktop processes all document content entirely on the user's physical machine. All 24+ document tools including inline text modification, table extraction to Excel, Tesseract OCR, compression, and permanent vector redaction are strictly bound to the local loopback interface (127.0.0.1). Zero bytes of document content ever leave the workstation.

2. Sovereign Data Custody & Compliance Matrix

EU GDPR (Articles 25 & 28)

Complies with Privacy by Design & Default (Art. 25). Zero third-party document sub-processors under Art. 28 because document content never leaves local hardware.

India DPDPA 2023

Preserves sovereign data custody. Ensures zero unauthorized cross-border transmission of confidential personal or financial records.

US HIPAA Security Rule

Confines Protected Health Information (e-PHI) to the covered entity's physical workstation, eliminating third-party cloud data repository risks.

Commercial Non-Disclosure Agreements

Enables legal counsel, auditors, and investment bankers to edit client balance sheets and M&A contracts without violating non-disclosure covenants.

3. Independent IT Network Audit Recipe

Enterprise IT administrators can independently audit and verify zero document egress using standard native diagnostic utilities:

// Windows Audit via Resource Monitor:

1. Run resmon.exe → Network Tab → Filter by Papryx.exe.

2. Perform large PDF text editing, OCR scanning, or Excel conversion.

→ Verified Result: Network Send remains strictly 0 B/s.

// macOS Socket Audit via Terminal:

lsof -i -P | grep -E "Papryx|papryx-backend"

→ Verified Result: All sockets bound strictly to 127.0.0.1 (Loopback). Zero external WAN listeners.

4. Gated External Network Communication (Disclosures)

License Activation (TLS 1.3): Connects strictly during activation to verify cryptographic seat tokens. Transmits only: one-way SHA-256 key hash, pseudonymous client-side hardware asset tags (EDPB Guidelines 01/2025), machine hostname, and app version. (0 bytes of document content or filenames).
Differential Auto-Updates: Checks for signed version manifests on Fastly CDN / GitHub Releases. Downloads delta blockmaps on Windows or prompts for direct DMG update on macOS.