Legal
Privacy for this catalog.
What this site stores
The catalog pages are static. There is no waitlist form and no analytics script. Visiting a page does not create a marketing profile. The membership desk, described below, is the exception: it keeps a subscription record and a signed cookie. This site does not sell personal data.
Checkout
A connected plate opens checkout. The payment processor handles the payment as merchant of record. The processor’s privacy notice governs the card, the receipt email, and the download link. Card numbers are not entered on this site. A button that says checkout is closed does not open a payment page.
Order notices
If a checkout webhook is pointed at this host, the receiver checks the signature. For a one-time edition it does not keep the payload. It does not store the buyer’s email, name, or card, and it does not receive the card number. The receipt and the files for that edition stay in the processor’s email.
Membership desk
When the desk is connected, a membership notice stores the subscription’s status, the renewal dates, the shelf it maps to, and a hash of the receipt pass. It stores the edition chosen for the month. It does not store the pass itself, the buyer’s name, the email, or the card. A signed cookie keeps the desk open in that browser. A short-lived counter stores a hash of the network address to slow repeated pass attempts. Billing links shown on the desk are the processor’s links, and they expire.
Support mail goes to [email protected]. Do not send passwords, client files, or secrets. Notes inside a kit about what not to paste into a chat model ship with the files. This website does not receive those pastes.
Cookies
This catalog does not set an analytics cookie. The membership desk sets one signed cookie after a receipt pass is accepted. It is limited to the desk. It is not an advertising cookie. When the affiliate program is open, the payment processor’s script loads on these pages. It contacts the processor only when an affiliate code is in the address or a referral cookie is already present. That contact includes a browser identifier, the page address, and the referrer, and the script may store a referral cookie named for that program. A visit with no code and no referral cookie does not create that contact. A live checkout may set cookies on the processor’s domain. Read the processor’s notice when that checkout is the one you are using.