No
Smoke.
Just Math.
Security isn't a marketing buzzword. It's cryptographic rigor. Here is exactly how we protect your data.
The Shredder Engine
We never send the original PDF to the client's browser. Doing so would allow anyone to open the network tab and download the file. Instead, we use a process we call "Shredding."
- 1. Ingestion & Vectorization The uploaded PDF is broken down into vector blocks server-side.
- 2. AES-256 Encryption These blocks are encrypted at rest using AES-256 block cipher.
- 3. Ephemeral Streaming When a viewer opens a link, our server renders *only the visible viewport* into a proprietary binary stream, delivered via WebSockets over TLS 1.3.
// Inspecting the network tab yields nothing but websocket frames:
Frame 1: Binary (Encrypted Viewport Chunk) - 14kb
Frame 2: Binary (Encrypted Viewport Chunk) - 12kb
Frame 3: Client Action (Scroll Down) - 102b
Frame 4: Binary (Encrypted Viewport Chunk) - 18kb
Encryption Overhead Estimator
How much latency does our military-grade streaming add compared to downloading a raw PDF? Almost none, because you only load what you look at.