No processing API
The static application contains no route that accepts document bytes, filenames, extracted text, or passwords.
PDFPioneer is exported as static files. Application assets may be requested from your own origin, but document content is processed by browser workers and never submitted to a document-processing service.
The static application contains no route that accepts document bytes, filenames, extracted text, or passwords.
Document APIs remain guarded. A separate, validated ad transport allows only configuration, ad selection and delivery events to the configured PicPlayer service.
OPFS stores recoverable revision snapshots where supported. An in-memory fallback is used when local persistence is unavailable.
IndexedDB stores small operation records and preferences. Clearing site data removes that local workspace state.
The activity panel exposes allowed and blocked browser requests rather than asking users to trust a marketing claim.
No document analytics or session replay is included. The separate advertising rail contacts PicPlayer’s ad service without receiving PDF files, filenames, passwords or page content. Ad choices can disable delivery on this device.
Browser storage controls
Revision snapshots use OPFS where available. IndexedDB stores session and operation metadata. Cached application assets enable offline use.
Origin usage
Checking…
Estimated quota
Checking…
Persistence
Checking…
Serve the editor from an isolated origin such as app.pdfpioneer.com, self-host all core WebAssembly, OCR, and font assets, and apply the included CSP/COOP/COEP headers. Deploy optional add-ons separately. Ad delivery uses a restricted transport and sandboxed creative origin. Ad-enabled deployments do not require cross-origin isolation; disable advertising at build time to restore COEP require-corp.