Privacy

Privacy starts with knowing where your PDF is processed.

ClearPDF labels local, cloud, AI, and API workflows so users can decide before processing.

Anonymous local tools

Phase 1 local tools run in the browser. Files do not upload to ClearPDF for these workflows.

Anonymous cloud jobs

Planned cloud jobs will use temporary uploads with a 60-minute deletion target for anonymous processing.

Account retention controls

Future accounts will expose saved history and deletion controls instead of hiding retention in support flows.

AI indexes and delete-now

Future AI tools will explain extracted text, embeddings, provider settings, and immediate deletion controls.

Provider training defaults

ClearPDF should use provider configurations that do not train on customer content where commercially available and document subprocessors.

Analytics boundaries

Analytics events should never include file names, file contents, extracted text, or unique document strings.

PDF privacy report

Review the supporting privacy guide, audit checklist, or processing policy.

Local-processing proof

Review the supporting privacy guide, audit checklist, or processing policy.

AI data policy

Review the supporting privacy guide, audit checklist, or processing policy.

Help

Common questions

Do local tools upload my PDF?

No. Local tools are designed to read and process files in your browser.

What happens for cloud tools?

Cloud tools will disclose upload and deletion behavior before processing.

Does ClearPDF use file contents in analytics?

Analytics should track product events without file names, document contents, or extracted text.

Backend status

Privacy evidence status

Backend readiness data separates local privacy claims from account, cloud, AI, telemetry, and retained-evidence launch gates.

  • Object storageazure-blob storage signing probe generated upload/download contracts without exposing storage secrets; live write/delete/read-after-delete evidence is still required.
    partial
  • AI provider executionAI provider execution is disabled or missing explicit provider policy/credentials.
    blocked
  • pgvector runtimepgvector is not configured for production runtime execution.
    blocked
  • Telemetry and error reportingNo Sentry/PostHog/OpenTelemetry exporter configuration is present.
    blocked
  • Retained production evidence0 valid retained candidate manifests; 0 required evidence items missing.
    configured

Build local-build-unset; release domain api.clearpdf.net; retained evidence missing items 0.