Cookie Policy

Cookies are small text files stored on your device when you visit a website. They help the site remember preferences, keep sessions secure, and understand how pages are used. This policy explains how DontHireDevs uses cookies and how you can manage them.

We group cookies and similar storage into these categories:

• Strictly necessary: required for the Site to function (for example security, load balancing, or remembering cookie consent choices if we present a banner).
• Performance and analytics: help us measure traffic and improve the Site. Where enabled, we use Google Analytics 4, which sets its own cookies or identifiers subject to Google's policies. It records page views and a handful of named events — a comparison page opened, the rate calculator used, a form submitted. We do not send your name, email address, company, or any form contents to analytics.
• Functional: remember choices such as region or form state where we implement them.
• Campaign attribution: remember which email, ad, or shared link brought you here, so that if you contact us we know what the conversation relates to. See "Similar technologies" below.
• Advertising: where enabled, the LinkedIn Insight Tag lets us measure our LinkedIn ads and show follow-up ads to people who have already visited the Site. See "Advertising and the LinkedIn Insight Tag" below.

We advertise on LinkedIn. When the LinkedIn Insight Tag is enabled on the Site, a small script from LinkedIn loads on pages you visit and may set or read LinkedIn cookies. It reports to LinkedIn that a browser visited a particular page — for example our rates page — together with data such as IP address, timestamp, browser and device characteristics, and the referring URL. LinkedIn may match that browser to a LinkedIn member.

We use it for two things, and nothing else:

• Retargeting: showing our ads on LinkedIn to people who have already visited this Site. LinkedIn only reports these audiences to us in aggregate — we do not receive a list of who visited.
• Conversion measurement: counting how many people who saw or clicked one of our ads later took an action we care about, so we can tell which campaigns are worth running. We count four: submitting the pilot form, submitting the contact form, using the rate calculator, and viewing the rates page. Three of those never change the URL, so the tag reports them as an explicit event — a call telling LinkedIn that this browser did one of those things. The event carries an identifier for which of the four it was, and nothing else: not what you typed into a form, not the numbers you put into the calculator, not your name or email address.

LinkedIn acts as an independent controller for the data it collects through the tag. Its handling is governed by the LinkedIn Privacy Policy, and you can control ad personalisation in your LinkedIn advertising settings — including if you do not have a LinkedIn account.

We honour Global Privacy Control (GPC). If your browser or extension sends a GPC signal, the Insight Tag is not loaded at all on your visit and no request is made to LinkedIn. Conversions are covered by the same switch: the code that reports one only exists if the tag loaded, so on a GPC visit no conversion is or can be sent. You can also block the tag with standard browser or extension controls. We do not load a <noscript> tracking pixel, so disabling JavaScript also prevents it.

We use your browser's local storage for campaign attribution. If you arrive from one of our emails, an ad, or a shared link, we store the campaign parameters and reference code carried in that URL for up to 90 days, and attach them to any form you submit during that time. That tells us which outreach a request came from. The reference code is a random string and does not contain your name or email address. Clearing your browser's site data removes it.

We may also use local storage, session storage, or pixels for security, fraud prevention, and aggregated usage metrics.

Our fonts are self-hosted and served from our own domain, so they set nothing and tell no one you were here. Embedded content, on the other hand — a scheduling widget or a video player, where we use one — is loaded from the third party and may set its own cookies. We do not control those; check that provider's policy for details.

Most browsers let you block or delete cookies through settings. Blocking all cookies may affect Site functionality (for example forms or security features).

For advertising specifically, you have three routes: send a Global Privacy Control signal (we honour it automatically, and the LinkedIn tag will not load), adjust your LinkedIn advertising settings, or email us and ask to be excluded — see the Privacy Policy.

Browsers never converged on a standard for the older "Do Not Track" header, so we do not act on it.

We do act on Global Privacy Control (GPC), which is recognised as a valid opt-out signal under California law. If your browser sends one, we do not load the LinkedIn Insight Tag on your visit, and no conversion is reported.

To be clear about the boundary: GPC turns off advertising, not analytics. Google Analytics still loads on a GPC visit, because measuring which pages get read is site measurement rather than cross-context behavioural advertising — it is not "sharing" in the California sense. If you want analytics off as well, use Google's opt-out browser add-on or a tracker-blocking extension. We also treat privacy requests submitted by email as described in our Privacy Policy.

We may update this Cookie Policy when our practices or vendors change. Review this page periodically; the "Last updated" date reflects the latest version.

Questions: pilots@donthiredevs.com. See also our Privacy Policy.