Back to Workspace
Wasm Sandbox Active
Engine Trust & Compliance Architecture

Zero Server Uploads. Client-Side RAM Processing.

Official compliance documentation across Merge, Split, Compress, and Image to PDF modules. Your files stay strictly in local memory and are never transmitted to cloud servers.

Merge PDFSplit PDFCompress PDFImage to PDF

Execution Runtime

WebAssembly (Wasm) isolated engine

LOCAL
Cloud Server Upload
0 KB
Telemetry & Analytics
DISABLED
Processing Speed
Instant RAM

Why Browser-RAM Architecture Keeps You 100% Safe

Direct structural comparison between traditional cloud converters and our local engine.

Traditional Web ToolsRisk Exposure
  • ✗Files uploaded over network to third-party server.
  • ✗Risk of temporary storage in server logs or disk cache.
  • ✗Latent response times tied to cloud queue bottlenecks.
PDFlow Local EngineZero Risk
  • Documents processed 100% in local device browser RAM.
  • Closing tab purges memory instantly with zero disk footprint.
  • Instant conversion speed unthrottled by server queues.

Official Policy Clauses & Declarations

Filter or search specific compliance policies below.

CL.01
User Owned

Copyright & Content Ownership

You retain 100% full ownership of every document, image, and PDF processed on our platform — whether merged, split, compressed, or converted from images. We claim zero rights over your IP or generated output files.

#sec-01
CL.02
Zero Uploads

Local RAM Privacy Engine

All conversions happen inside your browser memory (WebAssembly local sandbox). No document buffers are transferred across the network to external remote servers.

#sec-02
CL.03
Commercial OK

Fair & Transparent Terms

Provided as-is for lawful utility. Free for commercial, personal, and educational use without hidden telemetry, watermarks, or mandatory subscription traps.

#sec-03
CL.04
Hardware Optimised

Hardware & Browser File Capacity

Capacity thresholds are optimized strictly against local browser RAM bounds to guarantee non-blocking UI render speeds and instant download generation.

#sec-04
CL.05
TLS 1.3 Active

TLS Encryption & Transmission

All website static payloads operate under strict HTTPS/TLS 1.3 encryption. For cloud fallbacks, transient buffers are encrypted end-to-end.

#sec-05
CL.06
Instant Memory Release

Automated Zero-Trace Purge Policy

Because processing occurs in WebAssembly RAM, closing your browser tab immediately releases memory allocations. Zero residual files remain on disk.

#sec-06
Module Capacity Matrix

Optimised Local Capacity Per Module

Merge PDF

Max 20 Files

100 MB / file
Split PDF

Max 500 Pages

150 MB / file
Compress PDF

Max 200 MB

Up to 90% reduction
Image to PDF

Max 30 Images

JPG, PNG, WEBP, HEIC

Frequently Asked Security Questions

Clear responses concerning your data privacy and ownership.

No. Our PDF suite relies on WebAssembly compiled engines running client-side inside your browser sandbox. Your files stay strictly in local device RAM.