Pillar 2
Secure Viewing
A controlled session, not a file download. Server-rendered previews where every page request is policy-evaluated, watermarked, and audit-logged.
What you get
- Original document never leaves the server — recipients see rendered images only
- Watermarks baked into pixel output at render time, not overlaid client-side
- Cache-Control: no-store on every response prevents intermediate caching
- Per-token and per-IP rate limiting blocks automated scraping and brute-force
- Revocation takes effect on the very next page request
How it works
- 1Recipient opens share link
The backend evaluates the full policy stack: expiry, view count, passcode, OTP, revocation status.
- 2Server renders page
The document is rasterised server-side (PDF to PNG/JPEG). Watermarks with recipient identity and timestamp are composited into the pixel output.
- 3Hardened delivery
Response includes no-store, nosniff, CSP, and frame-deny headers. Every access is logged with outcome, policy state, and client IP.