Cookie policy
Last updated
There are two kinds of page in this product, and they treat cookies completely differently. This page names every cookie we set, explains why the public pages set none, and lets you change your choice.
Where cookies apply
Directories serves two kinds of page, and the difference between them decides everything below.
- This marketing site and the operator dashboard, on our own domain. You sign in here, so these pages need a cookie.
- Public directory pages, served on an operator's own domain. Nobody signs in there, and those pages set no cookies at all.
Cookies on this site
On our own domain, which is this marketing site and the operator dashboard behind it, we set two cookies and no others.
- _directories_session — The session cookie. It keeps you signed in and carries the token that stops another site submitting our forms on your behalf. It is marked HttpOnly and secure, restricted with SameSite=Lax, and it goes when your session does. This one is strictly necessary: the site cannot work without it, so there is nothing to consent to.
- cookie_consent — The consent cookie, which records your answer to the banner. It is described in full below.
That is the entire list. No advertising cookies, no third-party tags, no cross-site tracking, and nothing that follows you off this site.
Pages on customer domains
Public directory pages, served on an operator's own domain, set no cookies whatsoever. No session, no consent cookie, no analytics, nothing.
This is not a preference we could quietly reverse. Those pages are held at Cloudflare's edge and served from cache for up to six hours, and a response that set a cookie could not be cached at all. The public rendering path therefore carries no session, by construction. Somebody reading a listing is not tracked by us.
The consent cookie
The consent cookie records the answer you give the banner, so we do not ask again on every page.
- cookie_consent — The name this cookie is stored under.
- Its value is a version number and whether you allowed analytics. Nothing in it identifies you.
- It lasts 6 months from the moment you choose.
- It is restricted with SameSite=Lax and marked secure everywhere except local development. This site's own scripts can read it, because the page has to know your answer before it decides what to load.
If the cookie is missing, the banner appears. If it is there, the banner stays away.
Analytics
Analytics is a category we ask about but do not yet use. No analytics tool loads on this site in any consent state, and the category stays denied unless you allow it, so doing nothing means no analytics.
The choice exists so that adding a tool later is a decision made in the open rather than under time pressure. If we ever add one, we will name it on this page before it runs, and it will honour the answer already stored in your consent cookie instead of asking you again.
Your choice
Change your answer whenever you like. It takes effect immediately and is written back to the consent cookie.
Blocking cookies yourself
Your browser can block or delete cookies for any site, this one included. Deleting the consent cookie brings the banner back. Blocking it means we ask on every visit, because we have nowhere to write your answer down.
Blocking the session cookie signs you out and stops forms on this site from submitting, including the waitlist form. Public directory pages are unaffected, because they never needed a cookie in the first place.
Changes to this policy
We update this page whenever a cookie is added, removed, or changed, and the date at the top of it moves with the change.
Contact
Questions about cookies, or about anything else on this page, go to the address below.