Privacy Policy

What hiringlab collects, why, and who else sees it.

Last updated August 24, 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, nationality or work eligibility, skills, experience) if you build one.

Automatically: your account email if you sign in, a short-lived anonymous trial counter (a browser cookie, no account needed) that tracks whether you've used your one free check, and basic usage counts (how many checks, tailorings, or outreach drafts you've run this month) used only to enforce your plan's limits.

If you use the "Remember this CV on my device" toggle without an account, that copy stays in your browser's local storage only, it is never sent anywhere until you actually run a check.

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.

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.

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 History can show them to you later. That history is kept on a rolling 10-day window, anything older is automatically deleted, not just hidden.

Saved CVs and your profile are kept until you delete them yourself, they're a deliberate personal library, not ambient history. A profile edit history is kept too, capped at your last 10 snapshots.

If you're not signed in, nothing is stored server-side beyond the anonymous trial cookie (which just remembers a count, not your CV), and whatever "Remember this CV" saved in your own browser.

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 any single history entry 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.