Privacy & file handling

What stays on your device

The PDF you choose, its preview, your drawn or imported signature, and the generated PDF are handled locally by the page. There is no account, document inbox, or server-side document storage.

Your signature is not saved by this site for a later visit. Reloading the page starts a new editing session. Download the finished PDF before leaving the page.

What happens when you download

The browser saves a new PDF using its normal download controls. That file remains on your device until you remove it. The site cannot erase it from your Downloads folder, a cloud-synced folder, backups, or a recipient's device.

Your original PDF is not rewritten by the tool. If a save dialog offers to replace an existing file, choose a different filename to keep both copies.

Website requests and hosting

Your browser requests this site's pages, scripts, fonts used for PDF rendering, and other static resources from Cloudflare hosting. Those requests can expose ordinary connection information to the hosting provider, such as your IP address, requested URL, browser information, and a referring page when the browser supplies it.

Loading the website is separate from opening your PDF in the tool: the file contents and signature are not included in those website requests. External reference links in the guide take you to another provider, whose own privacy practices apply.

Accounts and advertising

There is no sign-in, payment form or advertising script. The page metadata and ads.txt identify the AdSense publisher account for verification; they do not load ads or send your PDF or signature to Google. The site does not use cookies or browser storage to keep your PDF or signature.

Optional task statistics

Statistics are off by default. If you choose Share basic task statistics for this tab, future signing attempts can send their start, outcome, download action, broad error category and time range to this site's Cloudflare-hosted collector. Uncheck the box to stop new requests and discard pending events. Reloading resets the choice to off. Requests already received cannot be recalled by unchecking.

Each attempt has a random identifier held only in page memory and used for events for at most 30 minutes. It is not a visitor account or a cross-site identifier. The data includes a fixed site/page name and a test-or-observed flag. We do not send your PDF, signature, filename, exact input values, page URL, search query or referring page in these task events. Built-in sample tasks and designated test runs are labeled synthetic. A generated or download-triggered event does not prove a file was saved or accepted.

The collector accepts at most 1,000 events per day for this site, including tests. Blocking statistics or reaching that limit does not block signing. Collection covers only participating, successfully received task events; it cannot establish the total number of visitors or all users' completion rate.

Daily cleanup is configured to remove individual task records older than 24 hours, normally within about 48 hours, and daily aggregate counts older than 90 days. This scheduled cleanup is newly configured and has not yet been observed running in production; failures can delay deletion. Cloudflare database recovery may retain deleted data for an additional seven days. There is no public endpoint for reading the records.

We do not enable collector request logs, invocation logs or traces. Cloudflare still processes connection information, including an IP address, to deliver and protect requests, under its own platform policies and retention; this site does not control all of that processing. The separate page-visit measurement described below does not use this task-statistics checkbox. Ordinary website resource requests remain separate from optional task statistics.

Page visits and performance

Public tool, guide and privacy pages use one manually installed Cloudflare Web Analytics script. It runs when those pages load on inkonpdf.com, separately from optional signing-task statistics. It helps us understand page visits, referring pages and loading performance. It does not measure whether you successfully signed a PDF.

The script sends page and referring URLs with query strings and fragments removed, a temporary page-load identifier, browser performance measurements and browser/device information to Cloudflare. It does not use analytics cookies or persistent browser storage. We do not add PDF contents, signatures, filenames or form values to it. The signing tool continues to work if an ad blocker prevents these requests.

Cloudflare provides these reports for up to six months and applies sampling to some reports. A page-view count is not a count of unique people. This service does not provide our UTM campaign or custom task-event reporting, and its visit population cannot be used as the denominator of the optional task statistics. See Cloudflare's description of the beacon and data handling and its analytics FAQ.

Using a shared device

• Download and check your finished PDF before clearing the editing session.
• Close the tab when you finish.
• Remove downloaded PDFs and source signature images from shared folders if you no longer need them.
• Check whether your browser or operating system syncs downloads to another device or cloud account.

Closing a tab is not a secure erase of your device. Browser extensions, operating-system tools, and anyone with access to your saved files are outside the signing tool's control.