Cookie Notice

Nothing, as measured rather than asserted. No page or API route on this site returns a Set-Cookie header; none of our code reads or writes document.cookie, localStorage, sessionStorage or indexedDB. There are no accounts, so there is no session identifier to keep, and the pay stub form you fill in lives in the page's memory — reload it and the fields are empty again.

That covers the whole browser side of the product. What we do store on our servers — the encrypted draft created when you request a document, the single-use hashed download and lookup tokens, and the request metadata used for rate limiting — is described in the Privacy Policy, not here, because none of it touches your device.

This website is operated by a United States–based independent operator under the Paystubs name, with its operator and hosting located in the United States. This site is offered from the United States and is governed by the laws of the State of Alaska. The single published channel for questions, compliance reports and legal notice is support@paystubs.shop.

Strictly necessary. None. The document builder, the watermarked preview and the download flow all work with cookies disabled in your browser, because none of them depends on state kept on your side.

Analytics. None. We load no third-party analytics or tag-management script, and no first-party usage cookie either.

Advertising, personalisation, profiling. None, and none is planned: the product is one document per request, ordered for a fee or provided free under a promotion, and there is no advertising revenue in it.

Social sharing. The share card on /opengraph-image is an image we generate. No like button, no embed, no pixel — so opening a link to this site in a social app does not put a cookie on your browser through us.

Under the EU ePrivacy Directive (as implemented in member-state law such as Germany's TTDSG and the UK PECR) and the GDPR's consent standard, a consent prompt is required before storing or reading information that is not strictly necessary to deliver what the user asked for. There is nothing here in that category, so a banner would be asking permission for an operation that never happens. Cookie walls of that kind are noise, and regulators have said so.

The obligation we do carry is transparency, which is what this page is for, plus the honesty rule that keeps it true: if we ever add a script or cookie that is not strictly necessary, this notice and a consent mechanism go live before that script does. Not after, and not “in the same release”. A regression check runs against the source on every change, so the statement above cannot quietly rot.

When you press the payment button you leave this site and land on a checkout page served by our payment provider, Creem, which acts as merchant of record for the purchase. That page can set its own cookies — for fraud screening, session integrity and tax/invoice records — under Creem's privacy and cookie terms, not ours. We neither control nor read anything stored there, and we never receive your card number. If you want the precise inventory for that step, it is Creem's to publish and you should read their policy for it.

Because there is no tracking on this site, there is nothing to disclose under California's categories of personal information collected by automated means: we do not sell or share personal information as those terms are defined, so there is no “Do Not Sell or Share My Personal Information” link to offer, and no Global Privacy Control signal for us to honor differently from the rest of this notice. What we do hold about you is what you typed into the form when you asked for a document, plus optional email, and you can have it deleted through order lookup for a paid order, or by asking, as the Privacy Policy explains.

Everything continues to work. Blocking cookies on this domain removes nothing you need, and the only place it bites is the hosted checkout in the previous section, which is a third-party site with its own requirements. Should a purchase ever fail in a cookie-blocked browser, the failure is on that checkout page and support can re-issue a download link from the order record.

Version 3.0 — last updated September 24, 2026. This is the version currently in force for the cookie notice you are reading. We do not keep superseded versions at a separate URL: the change log below is the record of what changed and when.

• Version 1.0 — September 22, 2026: First published version: no cookies, no browser storage, hosted checkout carve-out.
• Version 2.0 — September 23, 2026: Added the operator identity and contact line so this page names who is speaking.
• Version 3.0 — September 24, 2026: Marked the hosted-checkout section as describing a paid order, since while documents are free no third-party page is opened and no third-party cookies are set, and replaced the "one document for one payment" framing with one document per request.

A material change to this document gets a new version number and date above, and the date the service terms refer to is the same date.