privacy
What we collect, and what we do with it
This covers this website and the notification list. There is no product in service and no product data, so there is nothing else to describe. When that changes, this page changes before anything collects.
If you only read
Nothing is collected from you directly. There are no cookies, no analytics script, no tracking pixels, no embedded videos, no comment system and no social widgets. Every stylesheet, font and image on this site is served from this domain, so reading a post makes no request to anyone else’s server.
Cloudflare serves the site and, like any web host, records a log of requests: the page, the time, the country, the IP address the request came from. We read those in aggregate to see which posts get read. We do not join them to anything, and there is no cookie or identifier that would let us follow one reader between visits.
If you use the form
The notification form stores one row. It contains:
- the email address you typed
- which page you submitted it from
- the date and time
- the domain part of your address, and whether that domain is a free mail provider, both derived from the address itself
- a one-way hash of your IP address, used only to stop the same connection submitting repeatedly. The address itself is never written down, and a hash cannot be turned back into one
No name, no company field, no job title, no phone number. The form has one input and that is the whole of it.
What it is for
Two things. New writing when it is published, and one message when the product opens. That is the entire purpose, and it is the same thing the form says above the field.
The record is stored in Cloudflare D1, on the same infrastructure that serves the site. It is not shared, not sold, not rented, not passed to any third party, not loaded into an advertising platform or a CRM, and not used to train anything. There is no analytics product, no marketing automation and no email service holding a copy of it.
How long it is kept
Until you ask for it to go, or until the list is retired. There is no fixed expiry, and that is a consequence of what this is: a notification list rather than a campaign, where the whole point is still being able to reach you when there is something to say. An address that sits untouched for two years is a person who has not asked to leave, not a lapsed lead.
If the list is ever retired, or if this stops being something we act on, the table is deleted rather than archived.
Getting removed
Reply to anything we send, or email hello@assayerworks.com and say so. The record is deleted. You do not have to explain why, there is no confirmation step designed to talk you out of it, and there is no window during which we keep it anyway.
The same address works for asking what we hold about you, or for correcting it.
Two things worth being plain about
Removal is manual. There is no unsubscribe link, because nothing has been sent yet and a link that goes nowhere is worse than none. It is a person reading a reply and deleting a row. That works at this scale and it is a real commitment; when the list is large enough that it stops working, it gets automated before it gets ignored.
Cloudflare can see what it serves. They are our host and our access gate, so requests pass through their network and their own terms apply to that. We have not added anyone else to the path.
How this page is written
It is an accurate description of what this site does today, written from the schema rather than from a template. If it ever stops matching what we do, the page is wrong and we will fix it.