Cookies

Public pages

No advertising or external analytics tracker is configured on public pages. There is no claim here that a future integration will be exempt from consent.

Fonts load from this website. The department examples do not contact an AI provider.

Private sign-in

Admin sign-in uses the necessary elevate_admin secure, HTTP-only session cookie. It lasts up to eight hours and ends when you sign out.

If two-step sign-in is on, a necessary elevate_admin_step cookie holds the sign-in for up to five minutes between the password and the code. It is removed once sign-in finishes.

The client area uses Clerk’s authentication cookies and browser session mechanisms. They support sign-in rather than public audience measurement.

Private sign-in providers have their own privacy information. Those routes are separate from the public enquiry forms.

Calendly, only if you choose it

The configured calendar is loaded after you press “Show available times”. Calendly can then use its own cookies and process booking information.

Review Calendly’s privacy information before opening it. Sending a message or email does not require loading the calendar.

Loading on click does not establish that every use of a calendar provider is exempt from consent.

External links and photographs

External websites apply their own cookie rules after you follow a link. An externally hosted founder photograph contacts its host when it loads.

If this changes

Any new analytics, video or other integration needs a documented review of its actual data flows, retention and consent or objection controls.

The privacy and cookie notices must then match that configuration before the integration is released.