The website loads; the document stays local
Your browser downloads Paperkit's code, fonts, and libraries from the website. When you choose a PDF or image, the editor reads it locally. There is no document upload endpoint in this version. Rendering, editing, and PDF creation happen in the browser.
Local processing is not automatic saving
The open document and changes are held in the browser session. They are not stored in a cloud account or automatically saved to your original file. Closing the tab, refreshing, or a device running out of memory may lose the work. Download a copy before leaving.
Website visits still create technical data
The hosting provider handles requests needed to deliver and secure the website. These can include IP addresses, request information, and traffic statistics. The operator can view visitor and page-view counts. This is different from receiving the contents of your selected PDF. See the Privacy page for the current setup.
Covering text is not complete sanitization
When a page is edited, Paperkit exports its rendered appearance as an image instead of retaining the page's original text underneath. However, the editor is not a comprehensive document-sanitization tool. Do not assume that covering one area checks every page, attachment, metadata field, or copy of sensitive information.
Use the right workflow for sensitive files
Keep the original privately, review every exported page, and use a dedicated redaction and verification workflow when disclosure would cause harm. Paperkit's convenience features are intended for ordinary visual edits. A browser extension or another application on your device operates outside Paperkit's control.