Privacy Inspector
Privacy Inspector is a local leak scan. Review the report first. Sanitize writes a new file from an explicit checklist. It reduces what casual sharing exposes; it does not prove every hidden object is gone.
Privacy and offline checks
Document processing runs locally in supported PDFForge workflows. This panel is a diagnostic view; it cannot prove that no data left the device.
Observed resource activity
0 observations in this page session · 0 need inspection
Resource timing is unavailable in this browser. Use the independent checks below.
Page timing and the active service worker report different surfaces and may observe the same request. Worker activity can be incomplete; WebSockets, request bodies and extensions are outside this view. The latest 60 sanitized observations stay in memory only. URLs, filenames, query strings, document content and byte counts are not recorded here.
Verify independently in DevTools
- Use a clean browser profile and synthetic documents. Open Network in DevTools and enable Preserve log.
- Prepare offline below. Switch Network to Offline, then reload the saved workspace and select a new file.
- Inspect, redact, run output checks and download. Inspect failed requests and request payloads, including worker requests. A same-site request can still transmit data.
- Inspect Application or Storage. Cache Storage should contain public app assets and setup records only. Document recovery and content telemetry are disabled; recipe settings are saved only after opt-in.
Offline readiness
Full workspace not prepared for offline use
English OCR not prepared for offline use
Prepare while connected to save the workspace, tools, fonts and workers. English OCR is optional. Only public app assets are saved; documents, outputs and passwords are excluded. Browser storage can be cleared or evicted. Check saved assets before disconnecting and prepare again after an app update.
Checking saved app assets…
Open saved workspaceReady for local work · One heavy job at a time in this tab
Drop your PDF file here, or browse
Supports standard PDF documents • Up to 100 MB
Private by design. Document processing runs in this browser. PDFForge has no document upload API.
How it works
How Privacy Inspector works
Privacy Inspector is a local leak scan. Review the report first. Sanitize writes a new file from an explicit checklist. It reduces what casual sharing exposes; it does not prove every hidden object is gone.
Guided steps
How to use Privacy Inspector
- 1Select a PDF from your device.
- 2Run Scan PDF and read the report.
- 3Choose which cleanup steps to apply.
- 4Sanitize locally and download the new file. Re-scan if you want a second look.
In this tab
What stays in this browser
The file stays in this tab.
- What this tool reads
- Metadata, attachments, JavaScript, form values, incremental leftovers, hidden text, and image EXIF.
- What the download contains
- A report on this page. A download is a new PDF with the sanitize options you confirm.
Questions
Privacy Inspector FAQs
Does the scan upload my PDF?
No. Inspection and sanitizing run in this tab and a same-origin worker.
Is a clean report a guarantee?
No. The scanner covers common leak paths. Unknown encodings, custom objects, and some image metadata can remain.
Does sanitize remove hidden sentences on the page?
Not by default. Use Redact PDF for selected visible regions. Sanitize focuses on metadata, attachments, JavaScript, form values, rewrite leftovers, and best-effort EXIF.
Continue locally
Related tools
Stay in the browser with these nearby PDFForge tools.