Privacy policy

Effective September 26, 2026

• Who we are
• The website
• Analytics and cookies
• The app
• Other people in your data
• Why we use it
• Automated decisions
• Who handles it
• What we never do
• International transfers
• How long we keep it
• Your rights
• California
• Washington and Nevada
• Children
• Security
• Changes
• Contact

Who we are

Hunt helps developers find the roles worth their time and apply with every answer ready.

Hunt is run from the United States by an independent developer trading as Hunt ("we"). We decide how your personal data is used, which makes us the "controller" of that data in legal terms. For our legal name and postal address, write to privacy@usehunt.dev and we'll send them. When a company takes over running Hunt, we'll name it here first.

This policy covers:

• usehunt.dev, this website. It's live.
• The Hunt app at app.usehunt.dev. It isn't built yet. It will be an invite-only closed beta, and it isn't open to anyone.
• The @usehunt/cli package on npm. For now it's a placeholder. It prints a "coming soon" message and exits, and it collects and sends nothing.

During the beta, the Hunt app is offered only to people who live in the United States.

Hunt is also being built to help teams find the developers who fit. That side, the head hunt, isn't open. Before it opens, we'll update this policy to say what it collects from recruiters, what a recruiter can see about you (only what you agree to share, role by role), and how any ranking works.

usehunt.dev is Hunt's home during the beta. If Hunt moves to another domain or changes its name, this policy moves with it, and we'll say so here.

Privacy questions, requests and complaints go to privacy@usehunt.dev. Everything else goes to hello@usehunt.dev.

We haven't appointed representatives in the EU or the UK. Before the app opens to people there, we'll appoint them and name them here.

What the website collects

usehunt.dev is a set of static pages. There's no account, no sign-up, no waitlist and no email field. Hunt runs no server code of its own for the site and keeps no server logs. The records of your visit are Cloudflare's (below) and the Google Analytics data collected for us (see Google Analytics and cookies).

Our own code stores nothing in your browser: no cookies and no local storage. Google Analytics, which our code loads, sets two cookies (see Cookies).

The invite box

The home page has one form, a box for an invite code. The code is checked in your browser and never sent anywhere. The page stops the form from submitting, and the site's security policy blocks it from submitting even with JavaScript turned off. For now, a valid-looking code only shows a message that invites open soon. Nothing is looked up or stored.

If you open an invite link (usehunt.dev/i/…), your browser asks Cloudflare, our host, for that address. So the code reaches Cloudflare as part of the web address, the same way any address you visit does. Hunt doesn't store it, and Google Analytics sees only /i/, never the code.

"Come back later…" is just text. It collects nothing.

Cloudflare

Cloudflare hosts the site. To deliver a page, Cloudflare's network receives what any web server receives: your IP address, the address you asked for, and the standard details your browser sends with each request, such as its type and language. Hunt hasn't turned on any request logging of its own. Cloudflare's dashboard does show us traffic statistics for the site, which may include the addresses people asked for, so an invite link's code may appear there. What Cloudflare keeps is covered under How long we keep it.

Network error reports

Cloudflare adds a standard instruction to the site's responses called Network Error Logging. If loading the site fails, your browser may send Cloudflare a short report about the failure: the address that failed to load (on an invite link, that includes the code), the page that led there, if any, which Cloudflare server answered, your browser type, how long it took, the kind of request, the stage it failed at, the protocol, the status code and the type of error. Cloudflare also receives your IP address with it, as with any request. Successful page loads aren't reported.

Google Analytics and cookies

We use Google Analytics 4 on every page of usehunt.dev, including this one, to count visits and see which pages work. Apart from Cloudflare, Google is the only company the site's pages talk to. The fonts and images come from usehunt.dev itself.

What Google Analytics receives

• The page you're on: its full web address, including anything after a "?". On an invite link, only usehunt.dev/i/. Our code removes the invite code, and anything after it, before any event is sent.
• The site that sent you here, if your browser shares it.
• What you do on the page, through Google's "enhanced measurement":
  • scrolling near the bottom;
  • links you follow off the site, and which link;
  • file downloads and video plays;
  • forms you start or send: the form's ID, where it points and its button text, never what you typed. On the invite box that's "invite", usehunt.dev/ and "Let me in";
  • a search term in a page's address (like ?q=…). The site has no search box.
• General facts about your visit: your browser, device and language, and a rough location that Google works out from your connection. Google says Google Analytics 4 doesn't log or store IP addresses.
• A random ID, kept in the cookies below, so Google can tell a returning visitor from a new one.

We've turned off Google signals and ad personalization in our code. Those are the features that tie visits to Google accounts and to ads. Our pages also tell your browser never to pass their own address on, whether to Google's requests or to the next page you open, so an invite link's address can't reach Google that way either.

Google Analytics works for us as our service provider. We keep Google's data-sharing settings off and have accepted Google's data processing terms, so Google may use this data only to run Analytics for us, not for its own purposes or for ads. Google explains how it handles data from sites that use its services here: How Google uses information from sites or apps that use our services.

Cookies

Hunt sets no cookies of its own. Cloudflare may set a short-lived security cookie to tell people from bots, such as __cf_bm (up to 30 minutes) or cf_clearance (after a bot check). These are strictly necessary, and they aren't used for analytics.

Saying no

The site doesn't show a cookie banner. Where you are decides what Google Analytics does:

• In the EU, the EEA, the UK and Switzerland, analytics consent starts out denied, because the law asks for your consent before analytics cookies are set and the beta isn't offered there. Google Analytics sets no cookies and reads none. It still sends Google a cookieless ping for each page you open (the time, your browser, the page and the site you came from, with invite codes removed), with no ID that links one visit to the next.
• Everywhere else, Google Analytics sets the cookies above as soon as a page opens.

If you'd rather Google Analytics didn't run at all, block cookies for usehunt.dev or block Google Analytics, in your browser's settings or with a content blocker. You can delete the cookies above at any time. The site works the same without them.

Do Not Track and Global Privacy Control: our code doesn't read these signals, and Google Analytics loads either way. We don't sell or share personal information, so there's no sale or sharing for those signals to stop.

In the app

When the app opens, it will use Google Analytics too, under a stricter rule: analytics count visits and screens, never which role, company, fact or email. Screens are reported by their shape (like /jobs/:id) with generic titles, and links you follow by their domain only. No event may carry a job, company, fact, email, search text, invite code or token. Google signals and ad personalization stay off. The _ga cookie belongs to usehunt.dev and its subdomains, so the same ID can link your visits to this site with your use of the app.

The app will also set a few strictly necessary cookies of its own: one keeps you signed in, and short-lived ones carry a sign-in or an invite. None is used for analytics.

What the app collects, and why

The app isn't built yet. Nothing in this section is live. It describes what the app is designed to collect and why, so you know before you accept an invite. If what ships differs, we'll update this policy first.

You need an email address, through your sign-in, to have an account. Everything else is optional. Hunt works with what you choose to give it, and does less without it.

Your account

Hunt's sign-in has no passwords. Sign-in starts with GitHub. Google, a one-time code by email, and passkeys come later.

• GitHub: Hunt asks only to read your profile and email addresses. It keeps your GitHub account ID and your primary verified email, and it gets no access to your code or repositories.
• Google: Hunt asks only for your basic profile and email. Signing in with Google never gives Hunt your Gmail, Calendar or Drive. If your Google login belongs to a company-managed domain, Hunt asks you to use a personal login for a job hunt, because your employer could see the sign-in or lock you out.
• Email: a 6-digit code or a confirm link. Each is single use and expires after 15 minutes.
• Hunt also keeps your sign-in sessions, the devices you've connected (as tokens stored only in hashed form, which you can revoke), and which invite you used and when.

Why: to know it's you, keep you signed in, and keep the beta invite-only.

Your search

What you're looking for (titles, remote or location, minimum pay, tech stack). The roles Hunt finds or you add: title, company, links, pay, the posting's text, and Hunt's scores and vetting notes. Where each role stands: status, rank, applied, heard back. Your notes and drafts, the companies you watch, the searches Hunt runs for you and their logs, and an activity feed.

When you delete a role Hunt found, Hunt keeps a small record of it (where it came from, company, title and link) so the next search doesn't bring it back.

Your resume, if you give Hunt one.

Why: this is the tracker. It's what Hunt is for.

Your identity vault

Facts you tell Hunt about yourself, so it can answer application questions the way you would: contact details, links, work authorization, education, experience, pay, preferences, your story, and rules you set (like "never name my current employer"). Also answers you've saved to application questions.

Every fact is optional. Nothing about you is made up or upgraded: what Hunt doesn't know, it asks.

Each fact has a sensitivity level, which decides where it can go:

• Public facts can fill any application form. Links, work authorization, education and experience start here.
• Private facts fill only a direct-apply form Hunt matched to a job. Contact details, preferences, your story and your rules start here.
• Criteria facts are used only to judge a role's fit, never in a form or a draft.
• Sensitive facts are never filled in automatically. Pay and demographic facts start here.

You can change a fact's level, except that demographic facts always stay sensitive.

Sensitive facts get extra care:

• Their words never go into an AI prompt. Hunt's agents can see that a sensitive fact exists, never what it says. This covers the facts in your vault. Anything you type in chat, and the text of a resume or email Hunt reads for a task, does go to Anthropic (see Chat and AI).
• Demographic answers (age band, gender, ethnicity, sexual orientation, veteran status, disability) are never filled in automatically. The default is "prefer not to answer", and you choose each time.
• Some of these reveal special categories of data, such as racial or ethnic origin, health, or sexual orientation. Hunt will store one only with your explicit consent, asked for separately and naming what it is and why. We treat gender and veteran status the same way. This consent step isn't built yet. We'll build it before the app opens to anyone.
• You can withdraw that consent at any time. Withdrawing it erases that fact and every earlier version of it, for good. We keep a record that you gave and withdrew consent, never the fact itself.

When you replace a fact, Hunt keeps the old version as history. When you forget a fact, Hunt stops using it at once, but keeps it as history so you can trace an old answer. Forgetting a fact doesn't erase it. You'll be able to erase all your facts, their history and your saved answers for good, in one step.

Why: so Hunt drafts answers from things you've confirmed, instead of guessing.

Your mailbox, if you connect one

Connecting a mailbox is optional, and it isn't available in the app yet. This is how it works:

• Read-only. Hunt connects with an app password over IMAP in read-only mode, or through a Google or Microsoft app you set up yourself, with read-only permission (Gmail's read-only scope, or Microsoft's Mail.Read). It never sends, deletes, moves or marks your mail.
• Only job mail is kept. Hunt checks message headers first and downloads only messages that look like they're about your search, including your own replies. For those it keeps the sender, recipients, subject, date, the message text and its links, a short preview, a link that opens it in your mail app, which job it belongs to and what it needs from you. Marketing mail and newsletters aren't kept unless they're about a job you applied to.
• Sensitive details. Job mail can hold sensitive details, such as a disability accommodation or a health note. When you connect a mailbox, Hunt will ask you to agree, in plain words, that it may keep those details as part of the emails it stores, only to run your tracker. You can withdraw by disconnecting, which deletes those emails.
• Invites become events. Interview invites become calendar events and reminders.
• Disconnecting will delete the connection, its password or token, and the emails and reminders it brought in. Calendar events stay until you delete them.
• Your credentials stay yours. A mailbox password or token you give Hunt will be encrypted, never shown again, and used only for your own work. You'll be able to keep it on your own computer instead, through Hunt's connector (not built yet).

Why: so replies, rejections and interview invites update your tracker without you copying them over.

Google user data

This covers Sign in with Google and a Gmail account you connect. Hunt's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Chat and AI

Hunt uses Anthropic's Claude models to chat with you, find and vet roles, draft answers and notes, and sort job mail it can't place on its own. For each task, Hunt sends Anthropic the text that task needs. That can include your resume, your confirmed facts that aren't sensitive, your criteria (including the minimum pay you set), your roles, notes and calendar, a job posting, and emails the task reads. Anything you type in chat goes too, so leave out what you'd rather Anthropic didn't see.

To sort an unclear email, Hunt sends its subject, sender, date, the first 4,000 characters of its text, any calendar summary, and the companies and jobs it might match. That's at most 20 messages per sync, the model gets no tools, and you can switch this step off.

Hunt keeps your chat history. For every AI run, it will record which provider and model ran it, how many tokens it used and what it cost.

There will be two ways to run Hunt's AI:

• Bring your own AI: your own Anthropic API key, either stored in Hunt or kept on your own computer through the connector. Anthropic handles those requests under your own agreement with Anthropic. A key you store in Hunt will be encrypted, never shown again (only its last 4 characters), used only for your runs, and deleted when you delete it. Storing keys isn't built yet.
• Hunt AI: Hunt's own Anthropic key, on a plan. Anthropic then processes these requests for us, as our processor. Under Anthropic's commercial terms it may not train models on this content. By default it deletes API inputs and outputs within 30 days. If a request is flagged under its Usage Policy, it may keep it for up to 2 years, and its safety scores for up to 7. It keeps data longer when the law requires.

Why: this is how Hunt does the work you ask of it. AI output can be wrong, so read every draft before you use it. You press Submit.

Notifications and email from Hunt

Hunt's own email is limited to sign-in codes and the Brief, a summary of your search. Emailing the Brief is off unless you turn it on, and every Brief email has a one-click unsubscribe.

If you turn on browser notifications, Hunt keeps your browser's push subscription so it can reach you. In discreet mode, a notification says only something like "2 updates", never a role, company or title.

The browser extension (later)

Hunt's browser extension isn't built yet. It's designed to run only on a tab where you turn it on, never across all sites. It sends the app only what you capture: the page's address and title, the form's questions (labels, types and options, not anything you've already typed), the page's text up to about 30,000 characters, and a screenshot only if you tick the box. A screenshot shows whatever is on screen, including anything you've typed. It shows you a receipt for each capture.

It fills an answer only when you press Fill. It never answers consent, AI-disclosure or demographic questions for you, and it never clicks Submit. We'll update this policy before it's released.

Payments

Hunt takes no payments today. If that changes, this policy will name the payment processor first.

Other people in your data

A job search involves other people. The emails Hunt will keep from your mailbox, and the notes and calendar events in your tracker, can hold recruiters' and interviewers' names, email addresses and messages. Job postings Hunt reads are public pages, and some name a hiring contact.

Hunt keeps this only inside your own workspace, to run the tracker you asked for. That's our legitimate interest. It comes from your mailbox, from what you add, or from public job pages. It isn't used for anything else, and it never reaches anyone else's workspace.

Our providers handle it for us: Cloudflare stores it, and Anthropic reads an email when Hunt sorts one it can't place or when a task needs it. It's kept as long as the user keeps it (see How long we keep it).

If you're one of those people, you can ask what we hold about you, object to our keeping it, or ask us to delete it. Write to privacy@usehunt.dev. We can't always tell which workspace holds your data, so tell us the email address you wrote from.

Why we use it: our legal bases

In the EU and the UK, data protection law asks us to name a legal basis for each use of your data.

Automated decisions

Hunt scores and ranks roles for you. It compares each role's title, remote and location rules, pay and stack with the criteria you set, and its AI can vet a role in depth. That's advice for you. You make every decision, and Hunt never applies for you.

Hunt makes no decision about you based solely on automated processing that has legal or similarly significant effects on you.

Who handles your data

We use a few providers to run Hunt. Each gets only what its job needs.

Each of our processors works only on our instructions, under a written data processing agreement. We'll name any error-reporting service here before we use one.

Beyond these, your data goes somewhere else only when you choose to send it, or when the law requires it. We may also share data with professional advisers or authorities when we need to establish or defend a legal claim. When you share a role, you share the role, never your status, notes, scores or targets unless you add them.

If Hunt moves to a company formed to run it, or is ever sold, your data moves with it only under this policy's promises. We'll tell you first, and you can leave with your data before it moves.

What we never do

• Sell or share your data. No data brokers and no "partners". Our processors work only on our instructions.
• Read your data. No one at Hunt looks at your mail, facts or drafts, unless you ask us to (say, to fix a problem you reported), it's needed to investigate abuse or a security issue, or the law requires it.
• Show ads. No ads, no sponsored or boosted listings, and no paid placement in your rankings. We don't use analytics for advertising.
• Send email as you. Hunt reads mail read-only and drafts replies for you to send yourself.
• Submit for you. Hunt drafts, fills and prepares. It never submits an application or sends a message on your behalf.
• Make things up about you. Hunt is built never to invent experience, numbers or degrees. An AI can still get something wrong, so check every draft.
• Fill in sensitive answers automatically.
• Let a recruiter reach you without your say. Your data reaches a recruiter only with your consent, role by role, and no one can pay to reach you or move a ranking.
• Grow by pressure. No address-book uploads, no contact scraping, no auto-posting, and no dark patterns in sign-up or cancel.
• Train AI models on your data. Hunt trains no models on your data, and data from your mailbox or Google account is never used to train general AI models.
• Hand back passwords. No tool, API or export ever returns a password or token.
• Take orders from strangers' text. Hunt's agents are built to treat emails and job pages as data, never as instructions. They have no way to send email or submit an application, so a trick hidden in a posting can't do either as you.

International transfers

Hunt is run from the United States, and your data is processed there. Cloudflare's network also handles each request at the data center nearest you, which may be in your own country or another one.

When we pass personal data about people in the EU or the UK to our providers, we rely on:

• Cloudflare: the EU-US Data Privacy Framework (and its UK extension), and the standard contractual clauses in Cloudflare's data processing addendum.
• Google: the EU-US Data Privacy Framework (and its UK extension).
• Anthropic: the EU standard contractual clauses and the UK Addendum in Anthropic's data processing addendum.
• Our email delivery service and the service that runs Hunt's AI agents: we'll name each one's safeguard here when we choose them.

How long we keep it

The app isn't built yet, so the app rows are the rules it's designed to follow.

Your rights

Wherever you live, you can ask us to:

• Show you the personal data we hold about you (access).
• Fix anything that's wrong (correction).
• Give you a copy in a format other tools can read (portability).
• Delete it (erasure).
• Limit how we use it while a question is settled (restriction).
• Stop using it where you gave consent. You can withdraw consent at any time. That doesn't undo what we did before.

How: write to privacy@usehunt.dev. We may ask you to confirm it's you, for example by writing from the email on your account. We'll answer within one month.

In the app, export and account deletion will sit in Settings, two clicks away, with no survey. They aren't built yet. Until they are, email us and we'll do it for you. Leaving never holds your search hostage: you can take everything with you.

Your right to object

You can object at any time, for reasons relating to your situation, to any use of your data that relies on our legitimate interests (see Why we use it). We'll stop, unless we have compelling legitimate grounds that override your interests, or we need the data to establish, exercise or defend legal claims. To object, write to privacy@usehunt.dev. To object to analytics on the site, block or delete the Google Analytics cookies as described in Saying no.

Complaints

Tell us first if you can, at privacy@usehunt.dev. We'll acknowledge your complaint within 30 days, look into it, and tell you what we found and what we did.

You can also complain to a data protection authority. In the EU, that's the authority where you live, work, or where you think the problem happened. The EDPB lists them all: edpb.europa.eu. In the UK, it's the Information Commissioner's Office: ico.org.uk/make-a-complaint, or 0303 123 1113.

California

We give California residents this notice whether or not the California Consumer Privacy Act applies to Hunt yet.

• What we've collected in the last 12 months: only what the website collects and what people send us by email, since the app isn't open:
  • identifiers: your IP address, which Cloudflare receives to deliver pages, Google Analytics cookie IDs, and the email address you write from;
  • internet activity: the pages and events listed above;
  • a rough location.
• What the app will collect when it opens: what's listed in What the app collects.
  • identifiers, such as your email;
  • professional and education information;
  • only if you add them, or they're in your job mail, sensitive personal information: the contents of job emails, your citizenship or immigration status (from work-authorization facts), racial or ethnic origin, health, sexual orientation, or account credentials.
• Sources: you, your browser, and in the app the sign-in provider you pick and the mailbox you connect.
• Why: the purposes in Why we use it.
• Who receives it: the service providers in Who handles your data, for the purposes listed there.
• How long we keep each kind: see How long we keep it.
• No sale, no sharing. We don't sell or share personal information, as the CCPA defines those words, including that of anyone under 16. We use sensitive personal information only to provide what you asked for, never to infer things about you.
• Your rights: to know, delete and correct your personal information, to opt out of sale or sharing (there's none), to limit the use of sensitive personal information, and not to be treated differently for using any of these. Use them as described in Your rights. You can also use an authorized agent.
• Other companies: Google Analytics collects information about your visits to this site over time. We don't let other companies use our site to track you across other websites: its cookies belong to usehunt.dev, and the Google features that connect visits to your Google account or to ads are off.
• Do Not Track and Global Privacy Control: see Saying no.
• Effective: September 26, 2026.

Washington and Nevada

Hunt may hold health data you choose to give it, such as a disability in your vault or a health detail in a job email. In Washington and Nevada, the law calls this consumer health data.

We collect it only to provide what you ask for. We never sell it, and we never share it beyond the providers that run Hunt for us, or as the law requires. Before the app opens to anyone in Washington or Nevada, we'll publish a separate consumer health data privacy policy and link it from our home page.

Children

Hunt is for adults. It isn't for anyone under 18, and you confirm you're 18 or older when you create an account. If we learn an account belongs to someone under 18, we'll close it and delete its data. We don't knowingly collect personal data from anyone under 16. If we learn that we have, we'll delete it. If you think a child has given us data, write to privacy@usehunt.dev.

Security

On usehunt.dev today:

• No database, no server code of our own, and no form that sends anything. The site holds nothing about you.
• A strict content security policy. Pages can run scripts only from usehunt.dev and Google's tag server, can connect only to Google (its tag and analytics servers, and google.com), and can't submit forms. Other sites can't embed the pages in a frame.
• The pages tell your browser not to pass their address on to other sites, and they turn off camera, microphone and location access.
• Fonts and images come from usehunt.dev itself, not from third parties.

The app isn't built yet, so its protections are commitments rather than measures you can check. Signing in to Hunt will never use a password. Invite codes and device tokens will be stored only as hashes. An AI key or mailbox credential you give Hunt will be encrypted, used only for your work and never shown again. No tool, API or export will return a password or token. Each workspace will be walled off from every other. And Hunt's agents are built to treat text in emails and job pages as data, never as instructions.

No system is perfectly secure. If a breach puts your personal data at risk, we'll tell you and the authorities as the law requires. If you find a security problem, tell us at hello@usehunt.dev.

Changes to this policy

When we change this policy, we'll post the new version here and update the effective date at the top. For a change that matters, such as a new kind of data or a new use, we'll tell you in the app and on this page at least 30 days before it takes effect, and say why.

We'll never apply a looser practice, such as AI training or new sharing, to data we already hold without your clear, affirmative consent.

This is the first version of this policy. When we change it, we'll list the earlier versions here.

Contact

Hunt. Our legal name and postal address are yours on request at privacy@usehunt.dev.

• Privacy and data requests (access, export, correction, deletion, complaints): privacy@usehunt.dev
• Everything else: hello@usehunt.dev

Mail to both addresses passes through Cloudflare Email Routing to the inbox where we read it.