Cookie policy
The short version
Rolehound sets cookies to keep you signed in, and for nothing else. There are no analytics cookies, no advertising cookies and no third-party tracking cookies of any kind. That is why you have not been shown a cookie banner: there is nothing here to ask your consent for.
What is actually set
- hunter.auth — the sign-in cookie for the app. It is what keeps you signed in as you move between pages, and it is set only once you sign in. It is marked HttpOnly, so no script on the page can read it, and it is sent as a secure cookie over HTTPS. It expires after a period of inactivity and refreshes itself while you keep using the site. Strictly necessary.
- hunter.admin.auth — the same thing for the separate admin console on the admin subdomain, and set only if you sign in there. It is deliberately a different cookie from the one above, so an admin session and an ordinary account session can never be mistaken for one another. Strictly necessary, and irrelevant to you unless you are an operator.
- A short-lived two-factor cookie — if you have two-factor authentication turned on, the sign-in system sets one more cookie to hold the moment between entering your password and entering your code. It is named by the framework, it carries no more than the fact that a sign-in is half finished, and it is discarded as soon as that sign-in completes. Strictly necessary.
All of these are first-party: they are set by Rolehound, for Rolehound, and nobody else can read them.
What is not set
No Google Analytics or any other analytics tool. No advertising pixels. No social-network buttons that report back. No session recording. No A/B testing tool. No consent-management platform, because there is no consent to manage. The public pages load no scripts from anybody but Rolehound itself.
Strictly necessary cookies do not need consent under the UK rules, and Rolehound sets nothing outside that category — so there is no banner, and no "reject all" button, because there would be nothing behind it.
Other storage in your browser
A couple of interface preferences are kept in your browser's local storage rather than in a cookie: whether you have dismissed the prompt to install Rolehound as an app, and which columns of your pipeline you have expanded. These never leave your browser, are never sent to the server, and identify nobody. Clearing your browser's site data clears them.
How to clear or block them
Every browser lets you view, clear and block cookies from its settings, usually under privacy or site data, and you can do it for this site alone without touching any other.
Clearing the sign-in cookie simply signs you out. Your account, your CV, your applications and your history are untouched — sign in again and everything is where you left it.
Blocking it is different: without a sign-in cookie there is no way to stay signed in, so the app will not work at all. That is what "strictly necessary" means in practice.
Cookies set by other people
Two journeys take you off Rolehound's pages.
Paying takes you to a checkout or billing portal page hosted by Stripe. That page is Stripe's, and any cookies it sets are Stripe's, under Stripe's own policy. Connecting a mailbox with Google or Microsoft sends you to that provider's sign-in page, which is the same story.
On Rolehound's own pages, no third party sets anything.
Changes and questions
If Rolehound ever sets a cookie that is not strictly necessary, this page will say so before it does, and you will be asked first. What happens to the rest of your data is on the privacy policy. Anything else, ask on the contact page.