Stamp — Privacy Policy

Effective July 2, 2026 · Applies to the Stamp browser extension and web app

The short version

Stamp collects no data. Your documents never leave your device. All PDF processing — Bates numbering, exhibit stamps, watermarks, splitting, extraction, flattening — happens locally in your browser using a bundled JavaScript library. There is no server, no account, no analytics, and no telemetry.

What Stamp stores on your device

Two things, both kept in your browser's local extension storage and never transmitted:

1. License state. After you enter a Pro license key, the activation result is cached locally so you don't have to re-enter it.
2. Saved templates. Your own stamp presets (e.g. a Bates prefix and position for a client matter), if you choose to save any.

Uninstalling the extension removes both.

The only network request

When — and only when — you enter a Pro license key, the extension sends that key to Gumroad's license verification endpoint (api.gumroad.com/v2/licenses/verify) to confirm the purchase. The request contains the key you typed and the product identifier — never any document content or personal data. Gumroad's handling of purchase data is covered by Gumroad's privacy policy. If you never enter a key, Stamp makes no network requests at all.

What Stamp never does

Stamp does not collect, store, or share personal information, document content, filenames, usage analytics, browsing history, or anything else. The extension requests a single browser permission (storage) and cannot read or modify web pages, tabs, or browsing activity.

Changes

If this policy changes, the updated version will be posted at this address with a new effective date. Because Stamp's architecture has no data collection to begin with, changes would only ever narrow or clarify, not expand, data use.

Contact

Questions: bearman.derek@gmail.com