BatesKit

Privacy

Short version: your PDFs are opened, modified and written by code running inside your own browser tab. They are never transmitted, and there is no server that could receive them.

Last updated 2026-08-05 · English only; the English text is authoritative.

What happens to your documents

Nothing leaves your device. When you add files, the tool reads them with the browser’s own file APIs, rewrites them in memory, and writes the results either into a folder you picked or into a ZIP download. There is no upload step, no queue, and no storage. The processing has no server side to it.

You do not have to take this on trust. Open your browser’s developer tools, switch to the Network panel, and run a full batch: no request carries your data. Then disconnect from the network entirely and run it again. It works.

What this site does send

Five counting events, each roughly thirty bytes, sent to api.bateskit.com. Listed in full:

  • view — a page was loaded.
  • run — a batch finished. Recorded at most once per session.
  • buy — the checkout page was opened.
  • unlock — a licence key verified successfully.
  • error — stamping failed, together with a category such as encrypted or damaged.

No cookie, no identifier, no session ID, no fingerprint, no filename, no file size, no page count, and nothing derived from your documents. The requests exist so that the ratio between two adjacent numbers is knowable; they are not analytics in the usual sense. Block them with any content blocker and the tool behaves identically.

Your IP address and user agent reach the receiving server, as they do with any HTTP request. They are not stored alongside the event and are not used to build a profile.

No third parties

There is no analytics SDK, no tag manager, no advertising pixel, no embedded video, no chat widget, and no font loaded from a content delivery network. The site is served with cross-origin isolation enabled (COEP: require-corp and COOP: same-origin), which means the browser itself refuses to load third-party resources here. That is a rule enforced by your browser, not a promise made by us.

What is stored in your browser

  • Local storage — your stamp profiles, your interface language, and your licence key if you have one. All of it is readable and deletable by you at any time.
  • IndexedDB — the progress of an unfinished batch: file names, page counts and the number ranges already allocated. Never file contents. This is what allows a run to resume after a tab closes.

Clearing site data removes all of it. Nothing is synchronised anywhere, so there is no copy for us to delete on your behalf.

The feedback form

The form on the home page sends exactly two things: the text you typed and the email address you chose to leave, if you left one. It never sends a file, a filename, or anything about your documents. If you include an address, it is used to reply to you and for nothing else.

Payment

Payments are handled by a merchant of record, which acts as the seller and processes your card details on its own systems. We never see or hold your card number. That provider receives the information it needs to complete and tax the sale, and it applies its own privacy terms to that data. Your licence key is generated from the order and verified offline in your browser afterwards; buying does not create an account here, because there are no accounts.

Children

This is a professional document tool and is not directed at children. We do not knowingly collect information from anyone, of any age, beyond the five events above.

Changes

If this page changes, the date at the top changes with it. Material changes to what is sent would also be reflected in the FAQ on the home page, because hiding them there would defeat the point.

Contact

Questions about this page, or a request to remove feedback you sent: [email protected].