Files and contact data

Updated 19 October 2026.

Your documents

Images, signatures, source PDFs, CSV files and the values you add to documents are processed in your browser. These files, their contents and the source PDF hash are not uploaded to our servers. Opening the site still requests pages, scripts, fonts and other resources from its host.

PDF templates and saved sources

A PDF layout is saved in this browser only when you press Save template. Keeping its source PDF is a separate option, initially off. A saved source contains the document’s original content. CSV records, batch values, constants, signature images, previews and generated results are not automatically saved. Exported template JSON contains configuration and field names, without the PDF or batch values. Delete individual templates or clear the template library to remove its saved copies.

Optional usage statistics

Usage statistics are off by default. Your choice in Usage statistics at the bottom of each page covers automatic local counts, our server counts and self-hosted Umami. With permission, we count the tool, interface language and fixed steps such as accepted files, a prepared result, a download click or an error category. Umami also receives known public tool paths, fixed source and campaign codes, and a mobile/desktop label. Its server uses the network address and browser information to create a daily hash identifier and derive the browser, operating system, device, country, region and city. The location may be inaccurate. No identity, email or document data is attached. Our counters describe actions; Umami estimates sessions and does not count unique people precisely.

Each event sent to our audience API has a random identifier to prevent duplicate counts. It is not reused to identify a person or connected to an email address. That deduplication window is 30 days; expired records are removed when the database is used. Umami separately groups events using hash-based identifiers. It receives no account ID or email address, and we do not set analytics cookies. File names, file contents, signatures, PDF text and page parameters are excluded. Screens and editor contents are not recorded.

Ratings you choose to send

After a download, you can submit Yes, Partly or No and select a reason. Sending a rating does not subscribe you to email updates and does not require usage statistics to be enabled. Reports include rating counts by day, tool and language for the last 90 days. Older counts are removed when records are written or reports are read.

Email requests

When you submit the email form, we receive your address, language, selected message types and the tool where you submitted it. We also store the time and version of your permission. News about tools and invitations to product studies are separate choices, both initially unchecked. Your email is stored separately from usage statistics.

Automatic confirmation emails are not currently configured. Addresses submitted through the website remain unconfirmed requests, and no confirmation message is sent. They are not an active mailing list. The working support mailbox is a separate service.

Contact records older than 90 days are removed when a new email request is saved or the owner reads audience records. This browser can remove a new unconfirmed request only if it received a removal token. A token is not issued after a request to the email provider. For mailing subscriptions, use the unsubscribe link in the email. Only the site owner can view or export contact lists and server reports.

Settings in this browser

Browser storage remembers your statistics choice. Showing the rating prompt is remembered only in the current tab. If you close it or submit a rating, the browser remembers that choice to avoid asking again for seven days. A token for removing a new unconfirmed email request may also be stored here; the email address itself is not. Pilot reports and deliberately saved PDF templates remain local. Clearing site storage removes these settings and local copies.

How local storage is cleared

Saved templates and source PDFs remain until you delete them or the browser clears its storage. With statistics enabled, new local counts keep the latest 30 days. Earlier local reports are not automatically deleted while no further data is written. Imported pilot reports remain until you clear them. SQLite audience records cover 90 days; cleanup runs on database use. Umami records older than 90 days are removed by a daily job. Up to seven daily backup copies of each database are kept on the same server. Removed records may remain in those copies until they are replaced. Deleting a record from SQLite does not erase a copy already held by an email provider.

Your choices

You can turn statistics off at any time. This stops new automatic local counts, server events and Umami tracking. It does not erase earlier reports or recall requests already sent. Sending a rating, answering a local pilot questionnaire and requesting email are separate actions. You can use the tools and download documents without any of them. To remove local pilot reports, use the clear controls in Pilot reports.

Hosting and delivery

The site and API run on a Contabo VPS. SQLite on that server stores email requests and audience records, including daily action and rating totals. Self-hosted Umami stores analytics in a separate PostgreSQL database on the same VPS. Hosting processes network requests, including the address needed to deliver responses. Our audience API uses a temporary in-memory hash of that address to limit repeated requests. Raw IP addresses and the raw User-Agent header are not stored in these analytics databases. Brevo receives contacts only when email delivery is configured; it receives no documents. Hosting and email providers may process data outside your country.