Privacy

Measurement is opt-in, and no answer means no

The first time you arrive, a banner asks whether we may count your visit. Until you answer yes, nothing about your visit is written to our database — not the page, not a hashed address, not a timestamp. Closing the banner, ignoring it, or navigating away is treated exactly like declining.

That is a deliberately expensive choice. It means our visitor numbers are a floor bounded by how many people say yes, rather than a total, and the internal dashboards that show them say so. We would rather have an honest undercount than a complete record nobody agreed to.

What is recorded when you say yes

One row per page view, written on our own server, in our own database. It contains:

• the path you viewed, without any query string;
• a one-way hash of your IP address, salted with the current date and a secret key — never the address itself;
• the referring website’s hostname, if you arrived from one (our own pages are not counted as referrers);
• your browser’s User-Agent string, and a coarse device class derived from it — desktop, mobile or tablet;
• the time of the view.

If your browser is running JavaScript, a small first-party script may also report how long you stayed on a page and how far down it you scrolled. It sends nothing else, it is sent to our own server, and it checks the same consent answer before it sends anything at all.

The daily salt on the address hash matters more than it looks. Two visits on the same day from the same connection produce the same hash, which is how we can tell one person reading five pages from five people reading one. Once the date rolls over, the salt is different and the old hashes cannot be linked to anything — including by us.

What is never recorded

• Your IP address in a form anyone can read.
• Your name, unless you type it into the contact form or create an account.
• Anything you type into the search box. Query strings are stripped before a page view is stored.
• A cross-site profile. We set no advertising cookie, run no third-party tag, and load no script that reports to anyone else.
• Precise location. We do not use geolocation, and we do not resolve addresses to a place.

Crawlers are recorded, and here is why

Automated visitors — search engine crawlers such as Googlebot and Bingbot, AI crawlers such as GPTBot, ClaudeBot and PerplexityBot, social preview fetchers, SEO tools and uptime monitors — are logged whether or not a consent banner has been answered, because a crawler cannot answer one.

A crawler is a piece of software identifying itself by name in its User-Agent. It is not a person, it carries no personal data, and knowing which of them read which pages is most of the reason the measurement exists at all. Crawlers and people are never blended into a single “visitors” figure — every panel we look at is scoped to one or the other, because on a directory like this one a combined number is meaningless.

If a visit is misclassified as automated when it was a person, the row still contains nothing but a hashed address, a path and a User-Agent.

How long anything is kept

Visit records are deleted after 180 days, roughly 6 months. That figure is read from configuration by the page you are reading, so it cannot fall out of step with what the system actually does.

Messages sent through the contact form are kept while they are being dealt with and for a reasonable period afterwards, so that a follow-up about the same listing has context. Email alert subscriptions are kept until you unsubscribe; unsubscribing marks the record as cancelled and it stops receiving anything immediately.

Cookies

Three, at most, and none of them advertising: cpsj_analytics stores your answer to the measurement question, a session cookie keeps you signed in if you create an account, and a CSRF token protects forms from being submitted by other sites. Full detail is on the cookies page.

If you create an account

An account is optional and only exists to save jobs and searches. It stores your name, email address and a hashed password, plus the jobs and searches you save and whether you want a digest emailed. You can change any of it, or delete the account outright, from your account settings — deleting removes the saved jobs and searches with it.

Email alerts

Job alerts use double opt-in: we send one confirmation email and nothing else until you click the link in it. This is what Canada’s anti-spam legislation asks for, and we treat it as the rule rather than the ceiling. Every alert carries a one-click unsubscribe that works without signing in.

Who else sees any of this

Our hosting provider, which stores the database and serves the pages, and our email provider, which delivers alert and contact mail. Both act on our instructions only. We do not sell, rent or share personal information with anyone else, and we do not send anything to an advertising platform because we do not use one.

When you click an apply button you leave this site for the employer’s own system, and what happens there is governed by their privacy policy, not ours. We record that a click happened — which listing, when, hashed address, whether it looked automated — and nothing about you travels with you.

Your rights

Under PIPEDA and equivalent provincial legislation you can ask what personal information we hold about you, ask for it to be corrected, and ask for it to be deleted. Write to sales@uniqevo.co.uk and we will answer within thirty days.

One honest limitation: for visit records there is usually nothing to retrieve. The address hash is one-way and re-salted daily, so we cannot search the logs for you even if you ask us to. The way to stop visit recording is to decline — which you can do below, at any time, with no effect on anything else on the site.

Changes and contact

If this policy changes in a way that affects what is collected, the date at the top of the page changes and the consent question is asked again. Questions about any of it: sales@uniqevo.co.uk, or the contact form.