Privacy

Who is responsible

This site is independently operated and not run by a registered company. The site operator is responsible for everything described on this page and can be reached at [email protected].

What we do not collect

There are no accounts and no logins. The one thing that asks for anything about you is the optional email alert described in the next section, and it asks for an email address and the professions you want to hear about. Nothing here asks for your name, your address or your CV, because nothing here needs them. There is no contact form.

The third-party tools described below may each set their own cookies. The next section explains which of them wait for your permission and which do not.

Email alerts

If you sign up for the weekly email of new roles, we store your email address, the professions you chose, the page you signed up on, the time, your IP address and the exact consent wording you were shown. We send one confirmation email with one link; nothing else is sent until you open it. After that you get one email a week, only in a week that added a role in your professions.

Every email carries an unsubscribe link and the one-click unsubscribe header your mail app may show. Unsubscribing takes effect at once; we keep the address on a do-not-contact record so it is never written to again. A sign-up that is not confirmed within 7 days is deleted. The emails are sent through Resend, whose servers process the address to deliver the message. We do not track whether an email is opened. Links in it carry a tag that tells us the visit came from an email, not who you are.

Cookies and your choice

When you first arrive (outside the United States), this site asks whether to use advertising and analytics cookies. Rejecting takes one press, exactly like accepting, and you get the same site either way. Your answer is remembered in your own browser and is never sent to us. You can change it at any time with Cookie settings at the bottom of any page.

Google Ads conversion tracking and the Meta Pixel. In the UK, the EU and EEA, Switzerland, and anywhere we cannot tell where you are, they load only after you press Accept: if you press Reject, or never answer, neither is loaded and neither sets a cookie. In the United States, Canada, Australia, New Zealand, Argentina, Brazil, Chile, Colombia, Mexico and Peru they are on until you press Reject; in the United States no banner asks, and you turn them off with Cookie settings at the bottom of any page. Everywhere, a browser that sends the Global Privacy Control signal is treated as a Reject. Rejecting after they have run deletes the cookies they set.

Running either way: Microsoft Clarity, our own visitor beacon, our apply-click redirect, and Cloudflare Web Analytics. Clarity records how pages are used whatever you answer. Its cookies follow your Analytics choice: in the UK, the EEA and Switzerland it sets them only after you accept; elsewhere it sets them unless you reject. The rest set no cookies. Each is described in the sections below.

Analytics

Visits are counted with Cloudflare Web Analytics, which is cookieless, and Microsoft Clarity, which helps us understand how people use the site through interaction analytics and session recordings. Clarity may use first-party analytics cookies to connect page views into a session, and only with your consent in the UK, the EEA and Switzerland; without them it records each page on its own. Both run whatever you answer.

Cloudflare gives us aggregate page-view counts and coarse breakdowns such as referring site and country. Clarity records interactions such as clicks, scrolling and page layout for playback and aggregate analysis; sensitive fields are masked by Clarity, and so is anything typed into a box. We label relevant site actions with non-personal context such as the role ID, platform, profession, filter type, quiz step or the ad or post that linked you here, so we can understand which features lead to an apply click. We do not use these tools to identify you by name.

We also run Google Ads conversion tracking and a Meta Pixel, for the same reason: measuring paid advertising, on Google and on Facebook and Instagram, so we can tell which ads bring people who go on to apply. These two load only if you press Accept. Once loaded, each records a page view, and an event every time you press an Apply button. A second, separate event is recorded only when that press followed some real reading — ten seconds on the page, or a second page viewed — and that is the one we count as a result when we measure an ad. The Meta Pixel sets its own cookie, _fbp, and may read a click identifier (fbclid) from the page address when you arrive from a Meta ad. Google's and Meta's own privacy policies govern what each does with this data on their side; we only receive the ad performance figures they report back to us.

Separately, some pages remember a preference for the length of the browser tab, the sort order you chose on a profession page, for instance, using the browser's own session storage. That stays in your browser, never reaches us, and disappears when you close the tab.

On the roles page, we may suggest a country using the coarse country code Cloudflare provides for your connection. You can change it or choose “Any country.” An explicit country choice is remembered for this browser tab. Recommendation events include the country filter and whether it came from an IP suggestion or a supplied choice or link; they do not include your IP address. We also record whether a displayed role matches the profession you selected. This does not assess your qualifications.

Visitor beacon

A small script on every page records which pages you visit, how long you stay, and which links you click. It sends this to an endpoint on the same site, which writes it into Cloudflare Analytics Engine. To tell visits apart it stores two random identifiers in your browser (one per session, one persistent) containing no personal data. They cannot be linked to your name, email or IP address, never leave this site, and are never sent to any third party.

On the role search page, it also records which ranked role cards were actually visible, their position, the version of the ordering used, and the structured filters that produced it. It also records the words you type into the role search box, once you pause typing, with how many roles they found. The words are stored in lower case and cut to 100 characters, and anything that looks like an email address or a phone number is discarded without being stored. The same cleaned words are also attached to your Clarity recording as a label. If you open one of those roles and then press its Apply button within 30 minutes, the events share a random decision identifier. This lets us measure the path from a displayed recommendation to a role opening and then an apply click. The identifier is created by this site, contains no account information, and is not sent to the hiring platform.

Our own visitor beacon does not set a cookie. If you clear your browser storage or use a different device, you appear as a new visitor to that beacon. Clarity's separate cookie and retention rules are controlled by Microsoft; see Microsoft's Clarity privacy documentation for details.

Apply clicks

When you press an apply button, you pass through this site's own /go/ redirect before you reach the platform. That redirect records the click so we can see which professions and which roles are worth the effort of listing. What it records is:

• which role was clicked
• which profession the click came from
• which platform it went to
• a coarse country
• the referrer host (the site you arrived from, not the full address)
• the same random visitor identifier the beacon uses, described above. The page adds it to the redirect link at the moment you click it
• how much reading came before the press: how many seconds the page was on your screen, and how many of our pages you had opened in that browser tab. Both describe the visit, not you, and neither means anything outside it. They are what let us tell someone who read a few roles and then applied from someone who arrived and pressed straight through
• one word for how the click arrived — whether it came from a browser, a crawler, a link preview or a page loading the link in advance. Your browser's user-agent line is read to work that out and is not stored; only the one word is. It is what lets us tell real applications apart from the robots that follow every link on the web
• when you arrived through one of our own social posts, the name of that post design and any test version it used. This is a short label such as hook or hook.x-link.reply, kept in the current tab for up to 30 minutes so a later Apply press can be attributed to the post. It contains nothing about you and is not sent to the hiring platform
• a few housekeeping flags about the role itself: whether the link resolved to a destination, which host it went to, and whether the row was a labelled sample. These describe the posting, not you

The identifier is there for one reason: without it we cannot tell one person clicking five roles from five people clicking one each, and we cannot see which guides the people who apply had actually read. It lets us count readers instead of clicks and write more of what helps.

It is the same random string described above, with nothing behind it. It is not a cookie, it is never sent to the platform you apply on, and it is not shared with anyone. If you clear your browser storage you become a new visitor and there is no way for us to reconnect the two. A link someone shares with you never carries it, because it is added at the moment of a click and is not part of any page.

When you leave for a platform

The redirect hands you to the platform, and from that moment the platform's own privacy policy governs what happens. Read it there; we cannot answer for it.

We have no access to your application. We cannot see what you typed, whether you sat the interview or what the platform decided. The referral link identifies this site as the source of the click; it does not identify you to us.

Hosting

The site is hosted on Cloudflare Pages. Serving a page means Cloudflare handles the request, so it processes request logs (the ordinary technical record of a web request) as a data processor for this site.

Beyond that there is no application server of ours and no database: the pages are static files rebuilt each morning.

Data retention

Cloudflare Web Analytics retains aggregate visit data for up to six months. Beacon and click records in Analytics Engine are retained for up to 90 days. The random identifiers stored in your browser are controlled by you. Clearing your browser storage removes them immediately. An email alert subscription is kept until you unsubscribe, and then as a do-not-contact record; an unconfirmed sign-up is deleted after 7 days.

Your rights

The only personal data we hold is an email alert subscription, if you made one. Unsubscribe from any alert email, or write to us to see, correct or delete what we hold about your address. The random identifiers in your browser are yours to clear at any time through your browser settings. If you think something is wrong, email us.

Children

This site is not directed at children under 13, and the email alert is not for them.

Changes to this page

If this page changes, the date at the top changes with it. We do not notify visitors of updates because we have no way to contact you. There is no email list and no account system.

Questions

Email [email protected]. If you are writing to ask what we hold about you, the honest answer is already on this page: there is no record here with your name, your email or your address in it for us to look up.