Cookie policy
There is no banner on this site asking you to accept anything, and this page explains why there is nothing to ask about.
The pages you are reading now
They load one stylesheet from this address and run no JavaScript at all. They request nothing from another company: no analytics, no advertising pixel, no web font, no embedded video, no chat bubble.
One cookie is set, by the framework, to hold the session. On these pages the only thing kept in it is which language you last chose, so that an address without a language prefix opens in it next time.
That is the whole of it. Nothing here builds a profile of you, and there is nothing here to opt out of.
Once you sign in
The product itself sets two cookies. Both are needed for it to work at all, and neither is used to follow you around other websites, because neither of them leaves this one.
They are:
- estateschedule-session — the session. It is what keeps you signed in between pages, and it is marked so that a script on the page cannot read it.
- XSRF-TOKEN — proof that a form was submitted from a page we served. This one is deliberately readable by the page, because the interface has to send it back as a header; on its own it grants nothing.
The page a client opens from a reminder
That page carries its own key in the address, so it is served with instructions not to store it, not to index it, and not to pass its address on to any site linked from it.
It is handled by the same session machinery as the rest of the site, so the session cookie above may be set. Nothing about the client is written into it.
Nothing from anybody else
There is no analytics account behind this site, no tag manager and no advertising network. The response headers on the public pages block a script from loading at all, so a snippet added by accident fails visibly instead of shipping quietly.
If that changes, this page changes with it, and the change will be described before it is made.
Turning them off
Your browser can refuse or clear cookies for this site, and these public pages read perfectly well without them. You would simply pick your language again on each visit.
The signed-in product needs the session cookie. Without it there is no way to stay signed in from one screen to the next.