Privacy Policy

• We collect the minimum needed to run accounts, billing and usage limits.
• We do not store the invoice documents you validate. They are processed in memory to produce a result and then discarded.
• We do not sell your data, and we do not train models on your invoice contents.
• We use a small, named set of sub-processors, listed in clause 6.

Account data — your email address, an optional name, and a bcrypt hash of your password. Purpose: to create and secure your account. Legal basis: performance of a contract.

Usage records — for each API call, a timestamp, the type of call, which API key was used, and whether the result was valid. Purpose: to enforce plan quotas, show you your usage, and detect abuse. Legal basis: performance of a contract and our legitimate interest in protecting the service. These records do not contain your invoice contents.

Billing data — if you subscribe, our payment processor collects and holds your payment details. We store only a customer identifier and your plan status; we never see or store full card numbers. Legal basis: performance of a contract and our legal obligation to keep accounting records.

Technical logs — IP address, request timing and error information, used for security, rate limiting and debugging. Legal basis: legitimate interest. We do not log request bodies.

When you send a document to the validation or generation endpoints it is parsed in memory, checked against the rules, and the result is returned to you. The document itself is not written to our database and is not retained after the response. We keep only the metadata described above.

If you would prefer that invoice data never leaves your infrastructure at all, use the open-source library, which runs entirely locally with no telemetry. See Security.

If you use the optional explanation feature, the validation findings for that request — rule identifiers, business term references and our own message text — are sent to Anthropic for processing so that a plain-language fix list can be generated. The feature is opt-in per request. If you do not call that endpoint, no data is sent to Anthropic.

We use a single strictly necessary cookie to keep you signed in. It is HttpOnly, SameSite and Secure. We do not use advertising or cross-site tracking cookies, so we do not show a consent banner for them. [If analytics are added later, update this clause.]

We use these third parties to run the service:

• Vercel — application hosting and delivery.
• Neon — managed PostgreSQL database.
• Stripe — payment processing (paid plans only).
• Anthropic — AI explanations (only when you use that optional feature).
• [Email provider, once transactional email is enabled]

We will update this list before adding a new sub-processor that handles personal data. Some of these providers may process data outside the UK/EEA; where they do, transfers rely on appropriate safeguards such as Standard Contractual Clauses. [Confirm current hosting region and transfer mechanism.]

Account and usage data are kept while your account is open. If you delete your account, your account record, API keys, sessions and usage history are deleted immediately. Invoice documents are not retained at all. Billing and invoice records are kept for as long as tax law requires, typically six years.

Invoices normally contain personal data about your customers. Where you send such data to our hosted API, you are the controller and we act as your processor. A data processing agreement (Auftragsverarbeitungsvertrag) is available — [status: in preparation; contact us]. Using the open-source library locally avoids this question entirely, since no data reaches us.

Under UK and EU data protection law you may request access to your personal data, request correction or deletion, object to or restrict processing, and request portability. You can delete your account and its data yourself at any time from Settings.

To exercise any right, email [privacy@stampbench.com]. We aim to respond within 30 days. If you believe we have handled your data improperly you may complain to your supervisory authority — in the UK, the Information Commissioner's Office; in Germany, your state data protection authority.

We will update this policy as the service evolves and will change the date at the top. For material changes affecting how we use personal data, we will notify account holders by email.