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.

Images and Forms cloud libraries

Optional cloud libraries use your Emberkit account. Images saves named export settings, never source image contents. Forms Save uploads a blank PDF template and its chosen name; editable answers clear, but printed content and read-only fields remain. Cloud items are stored in our server database and retrieved only through authenticated, owner-scoped requests. They have no public sharing URL.

You can open or delete saved items after cancelling a cloud subscription. New saves require an active subscription. Account deletion removes cloud items from the application database; provider backups may retain copies for their backup lifecycle. Stripe processes billing details and does not receive your saved PDF templates.

Shared accounts and Sheets

One Emberkit account works across our products. When you choose an available social sign-in provider, we use its account identifier and the name, email and profile image it returns. Existing accounts link a provider only while signed in. Optional country, age range and gender fields are saved only when you submit Account settings; they are not required to use the tools.

Sheets uploads workbook contents only when you choose Save to cloud. Owners can grant named accounts viewing or editing access. People with access see collaborator display names and editing or viewing status while a workbook is open; presence expires after inactivity. Workbook contents, comments and saved versions remain private to authorized accounts and are not included in the public sitemap. Deleting a workbook removes its active records, comments, versions and sharing permissions. Provider backups follow their retention lifecycle.