Anonymous local tools
Phase 1 local tools run in the browser. Files do not upload to ClearPDF for these workflows.
Privacy
ClearPDF labels local, cloud, AI, and API workflows so users can decide before processing.
Phase 1 local tools run in the browser. Files do not upload to ClearPDF for these workflows.
Planned cloud jobs will use temporary uploads with a 60-minute deletion target for anonymous processing.
Future accounts will expose saved history and deletion controls instead of hiding retention in support flows.
Future AI tools will explain extracted text, embeddings, provider settings, and immediate deletion controls.
ClearPDF should use provider configurations that do not train on customer content where commercially available and document subprocessors.
Analytics events should never include file names, file contents, extracted text, or unique document strings.
Review the supporting privacy guide, audit checklist, or processing policy.
Local-processing proofReview the supporting privacy guide, audit checklist, or processing policy.
AI data policyReview the supporting privacy guide, audit checklist, or processing policy.
Help
No. Local tools are designed to read and process files in your browser.
Cloud tools will disclose upload and deletion behavior before processing.
Analytics should track product events without file names, document contents, or extracted text.
Backend status
Backend readiness data separates local privacy claims from account, cloud, AI, telemetry, and retained-evidence launch gates.
Build local-build-unset; release domain api.clearpdf.net; retained evidence missing items 0.