0x00000000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x00000010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x00000020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x00000030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x00000040: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

XeroPDF

Zero Retention Certificate

Independent memory inspection proof

Verified

PASS

Test Parameters

Method:Isolated child process

Renderer:Chromium (Playwright)

Payload:HTML with PII data

PDF size:18,816 bytes

Inspection Results

Heap scanned:99.54 MB

Document data leaked:0 bytes

Disk artifacts:None

Temp files:None

memory-inspection.sh

$ node --expose-gc zero-retention-proof.js

[1] Spawning isolated renderer with sensitive PII payload...

[2] Child rendered PDF (18,816 bytes) and exited

[3] OS kernel reclaimed child address space

[4] Scanning parent process memory (99.54 MB)...

[5] Searching for: SSN, account numbers, HTML fragments

Document content found: 0 bytes

Disk artifacts found: 0 files

VERDICT: ZERO RETENTION CONFIRMED ✓

Generated: August 22, 2026

Engine: XeroPDF v1.0 (Node.js + Playwright + Chromium)

xeropdf.com

Privacy-first PDF API

Share this certificate

Copy the embed code below to display this certificate on your website:

<a href="https://xeropdf.com/zero-retention-certificate.html" title="XeroPDF Zero Retention Certificate - Verified Memory Proof">
  <img src="https://xeropdf.com/examples/rendered/zero-retention-certificate.png" alt="XeroPDF Zero Retention Certificate showing 0 bytes of document data retained in memory after PDF generation" width="800" />
</a>

How this proof works

XeroPDF renders every PDF in a dedicated child process with its own isolated memory address space. When the rendering completes and the PDF is delivered to the client:

The child process exits completely
The operating system kernel deallocates the entire virtual address space
No document content remains in any process, cache, or disk location

This proof verifies the claim by injecting known PII (SSN, account numbers, financial data) into a test document, rendering it to PDF, then scanning 99+ MB of process memory for any trace of that data. The result: zero bytes retained.