Local tools
Local workflows run in the browser when available and should not upload the selected PDF.
Terms
ClearPDF terms are tied to available product modes.
Local browser tools, cloud processing, API usage, paid billing, partner widgets, and signing workflows have different operational requirements. Live paid, legal, enterprise, and partner claims remain blocked until the required retained evidence and approvals exist.
Cloud and API workflows
Server-side processing requires explicit upload, retention, deletion, quota, and worker disclosures.
Billing
Paid checkout remains evidence-gated until production payment processing and webhook proof are retained.
Signing and legal copy
Legal-validity or jurisdictional e-signature claims require retained counsel approval before publication.
Partner widgets
White-label or embedded widgets require partner contracts, domain verification, origin enforcement, and attribution rules.
Status
The public status page is the runtime source for current local readiness and missing production evidence gates.
Operational status
Review backend readiness and retained-evidence gates before relying on production API, billing, AI, integrations, or deployment claims.