Privacy Policy

Last updated: September 26, 2026

The short version

Resume Notebook can be used three ways, and they store your data in genuinely different places. Which one you are in is the single most important fact in this policy, so it comes first.

	Where your data lives	What we know about you
Browsing as a guest	Your browser only	Nothing that identifies you
Trial session	Our database, under a temporary account	What you upload or type
Registered account	Our database, under your account	The above, plus your email address

You move from the first to the second when you build a resume on the homepage or the ATS checker, including a blank one. Nothing else does it, and it is described in detail below.

We don't sell your data, and we don't use it to train anybody's model.

If you open the career builder and start typing, your work is saved in your browser's local storage under the key resume-builder-guest. It never leaves your device. We cannot read it, we cannot recover it for you, and clearing your browser data deletes it.

In this mode we hold no record of you beyond the ordinary web-server logs and the analytics described under What else we collect.

Trial session (an automatically created temporary account)

Saving a resume you build from an upload, and reading a job posting, need a server. So when you build a resume, we create an account for you automatically, without asking for an email or a password. This happens when you press "Build my resume" or a report's "Fix" on the homepage or the ATS checker, or start with a blank resume there. Anything you already had in the builder as a guest is copied up to the new account at the same time.

If you are already signed in, these save to your own account instead.

From that point on you are using the database like any other user, and this policy's account sections apply to you. Concretely, the temporary account holds:

Your career data — everything you upload or enter: your name, contact details, work history, education, skills, and so on.
Your resumes and the choices you made building them.
Job postings you paste, each saved as an application, along with any career track created to file it under.

A trial session has no email address and no password. It is tied to the browser that created it, so it can't be recovered, moved to another device, or looked up by us — there is nothing to identify it by.

We delete trial sessions 30 days after they are created, along with the career data and resumes they hold. That is a fixed lifetime, not an idle timer: it runs out whether or not you're still using it. Sign up before then if you want to keep any of it. You can also delete it yourself at any time from Settings → Data → Delete Account.

Signing up converts the trial session into a registered account in place. It keeps the same underlying record, so nothing is copied, moved, or lost — it simply gains an email address and a password, and stops being on a timer.

Registered account

A registered account is a trial session plus credentials. In addition to everything above, we store the email address you sign up with, and use it to sign you in, to send password-reset and email-verification codes, and to send one welcome email.

If you buy a Pro subscription, we also store your subscription status and the customer and subscription identifiers our payment provider gives us. We never receive or store card details.

What else we collect

These apply in every mode, including guest browsing.

Usage analytics. We use Umami, a privacy-focused analytics tool, to count page views and a small set of product events (for example, "a resume was created"). It sets no cookies and does not follow you to other sites.
Error reports. We use Sentry to record crashes and errors so we can fix them. A report includes the error itself, your browser and operating system, a short trail of the actions that led up to it, and — if you are signed in — your internal user ID. It is not meant to include the contents of your career data, though an error message can occasionally quote a value that caused it.
Rate-limit records. To stop one person from creating thousands of trial sessions, we keep a one-way cryptographic hash of the IP address that created one. The hash is salted with a secret only our server holds, so it cannot be reversed into an IP address, and the record is deleted after 24 hours.
Server logs. Our hosting provider keeps standard request logs, which include IP addresses, for a short period.

Resume Notebook itself sets no cookies — your sign-in session is kept in your browser's local storage. Our payment provider's checkout runs on their own site and follows their policy.

Resume files you upload

When you upload a resume on the homepage, to the ATS checker, or to the builder's import, the file is read entirely inside your browser. It is not uploaded to us and we never receive a copy.

If you only run the ATS checker, nothing about your resume reaches our servers.
If you build a resume from what was read, we save it — your name, contact details, work history and the rest — as career data in the trial session described above, or in your account if you are signed in, so you can keep working on it.

What leaves our servers for Google Gemini

A few features send parts of your career data to Google's Gemini models:

Pasting a job posting — on a resume, or when you start one from a posting on the homepage or the ATS checker — reads out its job title, company and skills, and matches it to one of your career tracks by their names and notes.
"Create from a job posting" builds a resume around a pasted posting, picking and tailoring the bullets from your career data that fit it.
Checking a resume against its posting again compares a resume you already have to the posting once more.
The same kinds of checks through the HTTP API or the Claude connector — reading a posting, checking how your items fit it, matching or grouping your career tracks, or building a resume from a posting — when you or an agent you connected call them.

For each of these, we send Google the posting text, when there is one, and the parts of your career data and resumes it needs. Google processes it to produce the result.

This work needs a server; none of it can run on your own device alone. If you would rather no third party ever saw your career data, use the career builder as a guest and don't paste a posting — every other feature of the builder works without one.

If you connect Resume Notebook to an outside assistant yourself — via an API key or the Claude connector in Settings — then that assistant reads and writes your real career data, and its provider receives whatever it reads. That connection is yours to make and yours to revoke, from the same settings page. API keys and connector links are available on registered accounts only.

Publishing a resume creates a link at /r/… that anyone holding it can open, without signing in. The link contains an unguessable identifier, but it is not otherwise protected — treat it as public. You can unpublish it, reset it to a new identifier, or give it an expiry date at any time.

Who processes your data

Convex — application database and backend
Vercel — web hosting
Google (Gemini) — the language model behind job-posting features
Resend — transactional email (welcome, verification, password reset)
Polar — payments, as merchant of record; they receive your email and billing details when you buy a subscription
Umami — usage analytics
Sentry — error reporting

These providers may process data in the United States and other countries. We don't sell your data to anyone, and we don't provide it to anyone to train a model.

How long we keep things

Guest data — in your browser until you clear it. We never have it.
Trial sessions — deleted 30 days after the session is created, along with the career data and resumes they hold.
Registered accounts — kept until you delete the account.
Rate-limit hashes — 24 hours.
Billing records — kept as long as we're required to for tax and accounting.

Privacy Policy

The short version

The three modes, in detail

Browsing as a guest