Your documents and privacy

The PDF editor and local tools process document contents in your browser. They do not upload your document unless you explicitly choose Upload to cloud history. That optional paid feature sends the completed PDF and filename to Emberkit. Download your work before closing the tab.

Word conversion sends extracted document content to our server for rendering. This conversion endpoint does not store that content. Developer API requests and existing account features have their own server-side processing and storage behavior.

We measure tool starts, download clicks and whether a browser used a tool on an earlier day. These events contain only the tool name, event type and a returning-use flag. We do not send filenames, document contents, field values or a persistent visitor ID in these events. A date is stored locally; Do Not Track disables these tool events. Hosting services may separately retain normal request logs such as IP addresses.

Existing cloud documents remain accessible to their account owner. Support messages and account or billing information are processed to provide those services.