Privacy Policy
What hiringlab collects, why, and who else sees it.
Last updated November 14, 2026
Overview
What this covers
hiringlab (Score, Tailor, and Outreach) scores your CV against a job description, rewrites it for a specific role, and drafts outreach to a hiring manager. Doing any of that means reading real, often identifying information off your CV: your name, contact details, employment history, and education. This page explains what we collect, why, where it goes, and how to get it deleted.
Collection
What we collect
Directly from you: the CV file or text you upload or paste, the job description or job posting URL you provide, saved CVs you name and store for reuse, hiring manager and company details you enter for Outreach, and anything you type into a profile (bio, links, work eligibility, skills, experience) if you build one.
Automatically: your account email if you sign in, short-lived anonymous trial counters (browser cookies, no account needed) that track whether you've used your one free Score check and your one free Tailor run, and basic usage counts (how many checks, tailorings, or outreach drafts you've run this month) used only to enforce your plan's limits.
Processing
Where it goes to generate a result
To score, tailor, or draft anything, your CV text and the job description are sent to Google's Gemini API for that one request, purely to generate the result you asked for. Outreach's research step may also run a live web search (via the same provider) on the company or hiring manager name you give it, to ground its drafts in real information.
The writing steps of Tailor and Outreach use a Gemini model that Google runs through its global service, so for those requests your CV text and the job description may be processed in data centres outside Europe.
We don't use your CV or JD content to train our own models, and we don't sell it or hand it to advertisers. It's processed to answer the request you made, nothing else.
Chrome extension
The hiringlab Chrome extension
The extension adds the job you're looking at to your hiringlab account, and on LinkedIn it can save the person you're viewing as a contact for one of your applications. It only works after you connect it to your account, and it only reads a page when you click its icon. It never runs in the background, never reads other tabs, and never tracks the pages you visit.
On a job posting, when you click Add: it reads that one page's visible text, any text you've highlighted, the job data the site publishes for search engines (title, company, location, description), the page title and the page URL. It sends these to hiringlab with the CV you picked, the tools you ticked and any hiring manager name you typed. We use them to pull out the job description and save it as an application. If the page doesn't publish its own job data, the page text is sent to Google's Gemini API for that one request so it can find the job description on the page. We keep the job description and the posting URL with your application, not the rest of the page.
On a LinkedIn profile, when you click Add contact: it reads the person's name, headline, current company and profile URL. The headline and company are only used inside the extension to pick the matching application for you. What gets saved to your application is the name, the profile URL, and any email or notes you type in.
Stored in your browser: to keep you signed in, the extension stores your hiringlab sign-in session (access and refresh tokens and your account email) in Chrome's extension storage. Nothing from the pages you visit is stored there. Signing out in the extension, or removing it, deletes this.
Everything the extension sends goes only to hiringlab, over an encrypted connection, and is handled under the rest of this policy. We don't sell it, use it for advertising, use it to decide credit or lending, or use it for anything other than the features above. hiringlab's use of information received from the extension follows the Chrome Web Store User Data Policy, including its Limited Use requirements.
Storage
What we keep, and for how long
If you're signed in, we store your checks, tailored CVs, and outreach drafts in our database (hosted on Supabase) so your Applications dashboard can show them to you later, grouped by the job they were for. Ask us from the Contact us page if you want them deleted.
Saved CVs and your profile are kept until you delete them yourself, they're a deliberate personal library, not ambient history.
If you're not signed in and run your free Score check or free Tailor run, we hold that result (the score, or the tailored CV), with the CV and job description it used, for up to 7 days. It's linked only to a random ID in a browser cookie, not to you, and exists so the result can be saved into your account if you sign up from the same browser, along with the CV it used, which goes into your CV Library. If you don't, it's deleted after 7 days. Beyond that, nothing is stored server-side for signed-out visitors except the anonymous trial cookies (which just remember a count, not your CV).
Access
Who can see it
Your own checks, tailorings, outreach drafts, and saved CVs are visible only to you when signed in, enforced at the database level so one account can never query another's rows.
A small admin team can access account-level data (usage limits, access requests) and, when needed to debug a reported problem, an individual check's content, to keep the product working. Admin access is not used to browse CVs without a reason to.
Your choices
Deleting your data
You can delete a saved CV, a profile, or an application yourself, at any time, from within the app. Deleting your account removes everything tied to it. If you'd rather we do it for you, or you have any other question about your data, reach out from the Contact us page and we'll handle it directly.
Other
A few more things
hiringlab isn't directed at children, and isn't intended for anyone under 16 to use.
If this policy changes in a way that matters, we'll update the date at the top of this page.