Privacy

Last updated 30 September 2026.

Without an account, your resume stays in your browser

The builder works without signing in, and that is the default. Everything you type is saved to IndexedDB, a storage area belonging to this site inside your own browser. It is not transmitted to us. Clearing your browser data, or using the “Clear all data” button in the builder, deletes it permanently.

The practical consequence: we cannot recover your resume for you, and we cannot read it either. Both follow from the same design.

If you create an account

An account exists for one reason: so your resumes follow you between devices. Creating one is optional, and nothing you build is sent to us until you explicitly save it.

Signing in stores your email address. If you sign in with Google we also store the name Google gives us; we do not ask Google for anything else, and we do not store your profile picture. Saving a resume stores its content, its title, and when it changed.

There is no password. You sign in with a link emailed to you, or with Google. We never hold a password, so there is none to leak, reuse, or reset. Sending that link is the only time your email address is handed to another company — a transactional email provider — and the message contains a login link and nothing else. No part of your resume is ever included.

Your files are generated on your device

The PDF, DOCX, and text files are built in your browser and handed straight to your downloads. They are never uploaded, never generated on a server, and never stored by us — with or without an account.

Optional local AI, no third-party analytics

If you choose Enhance in the cover-letter editor, a small model is downloaded once and runs in your browser. The selected paragraph and resume evidence stay on your device: they are not sent to us, to a language-model API, or to the model host, and they are never used for training. The model host receives an ordinary request for its public model files, like any other file download.

Enhance is optional, proposes wording for you to review, and is free. There are no third-party analytics or advertising scripts on the builder.

Server logs

Serving the site produces ordinary web-server logs — IP address, timestamp, and which page was requested. These record that a page was fetched. They never contain resume content: error reports are scrubbed of it, and without an account none of it reaches the server at all.

What we count, and what we do not

This site keeps a tally of how often each of its pages is viewed and each of its tools is used, so we can tell which pages help people and which do not. It is a count and nothing more: for each thing below, one number per day. The table it is kept in has a column for the name of the thing, one for the day and one for the number, and no column where a person, a device, an address or a word of your resume could go.

No cookie, no identifier, no IP address. The count is sent to this site and nowhere else, without the cookie a signed-in visitor has — the server refuses one that arrives with a cookie — so it cannot be tied to an account. Nothing you type is ever part of it. Crawlers are not counted, and if your browser sends Global Privacy Control or Do Not Track, nothing is sent at all.

What is counted:

which page on this site was viewed;
where a visit came from, as one name from a short list — a search engine, a social site, “other” or “direct” — and never the page it came from;
that a file was read by the free ATS check;
that a file could not be read by the free ATS check;
that the ATS check's result was taken into the builder;
that the keyword scanner compared a posting with a resume;
that the keyword scanner's resume was taken into the builder;
that the bullet checker checked something (once per visit);
that a PDF was imported into the builder;
that a Word file was imported into the builder;
that an older Word (.doc) or RTF file was imported into the builder;
that a JSON Resume file was imported into the builder;
that a file could not be imported into the builder;
that a template was applied;
that a template was downloaded as a Word file;
that a template was downloaded as a PDF;
that an example resume was downloaded as a Word file;
that an example resume was downloaded as a PDF;
that the Six seconds tab was opened;
that the X-Ray tab was opened;
that the Interview tab was opened;
that a resume was matched against a job description;
that a cover letter was composed;
that a PDF was downloaded;
that a Word file was downloaded;
that a plain-text file was downloaded;
that a JSON Resume file was downloaded;
that a sign-in link was requested;
that a Google sign-in was started;
that a sign-in completed;
that a resume made without an account was saved to one;
that a backup was downloaded from the reminder to keep one;

Your rights

Without an account we hold no personal data about you at all, so there is nothing for us to export, correct, or erase — your data is on your device, and the builder can delete it.

With an account, deletion is in your hands and takes effect immediately. Deleting a resume removes it and its history outright; deleting your account removes the account, every resume on it, and everything derived from them. There is no trash, no grace period, and no backup copy we could restore from, which is the same trade as the guest path: we cannot undo it for you because we did not keep it.

Export is one click and needs no request: “Download everything” on your dashboard gives you every resume on the account in the open JSON Resume format — the full content, not a summary, in a format we did not invent and other tools already read. Every resume can also be downloaded as PDF, DOCX, and plain text from the builder, for nothing and without limits.

Fields we deliberately do not have

There is no field for a photograph, date of birth, marital status, gender, or nationality. These invite discrimination in most hiring markets and are unnecessary in nearly all of them, so the app does not collect them at all rather than storing them carefully.