The document is opened, edited and built locally on your device. This page also explains browser storage and external services.
Open the PDF editorPDF.js displays pages, pdf-lib builds the result, and a local PDFium Web Worker attempts direct text edits. Document bytes move between these parts inside your browser.
The app has no PDF-upload endpoint. The payment backend and Stripe receive transaction data, but the frontend does not send them the document, its filename or inserted images.
During regular editing, the document, history and inserted images stay in the current tab memory. They may remain there until the document is replaced or the app is refreshed or closed. No server copy exists from which the file could be restored.
When payment starts, the finished PDF is saved in this browser’s IndexedDB. The record is removed after payment confirmation or cancellation; after 25 hours it is treated as expired and removed the next time the app runs cleanup. sessionStorage holds a fulfillment identifier, while localStorage holds the chosen language.
The site is hosted on Azure Static Web Apps. If you choose payment, the browser connects to the payment API and Stripe Checkout. The app loads no external fonts and contains no first-party analytics or advertising pixels.
No server copy improves document privacy, but it also means there is no recovery after clearing browser data or changing device or profile. Payment return must use the same browser in which the file was prepared.
No. The frontend sends identifiers needed to create and verify a session, but the PDF, its filename and image contents stay in the browser.
The application code creates no first-party cookies and contains no analytics. Hosting providers or Stripe may process connection data or use their own mechanisms under their policies.