Privacy Policy

What we collect

Nothing about your resume. This application has no backend, no database and no authentication. What you type never leaves your browser:

• A resume you write in the builder, your saved resume library, pasted job descriptions and display preferences are kept in your browser’s localStorage, so they are still there next time.
• A resume you paste or upload on a tool page is kept in that tab’s memory only. It is gone when you close or reload the tab.
• Your answer to the cookie question, and a few small markers (for example, whether you have seen the builder tour and when you last exported a backup), are also kept in localStorage.
• A service worker stores copies of this site’s own files so pages open faster and work offline. It stores nothing you typed.

How to verify that

1. Open your browser's developer tools and select the Network tab.
2. Use every feature of the builder — type, analyze, export a PDF.
3. You will see requests for the application’s own files and for the third-party services listed under Every third-party service below. What you will not see, on any page, is a request carrying your resume.
4. That check needs no trust in us at all — it is your own browser reporting what it sent.

Deleting your data

Use the clear button in the builder toolbar, or clear site data in your browser. Because nothing was ever sent anywhere, that is the complete deletion process.

The contact form

The contact page is the one place where something you type is sent anywhere, and only at one moment. Opening that page sends nothing you typed. When you press Send, the name, email address and message you typed are posted to Web3Forms, a form-delivery service that emails the message on to us.

• Your resume is not attached and is not accessible to the form. It carries three fields, all of them ones you typed into it.
• The email address is required, and is used for one thing: replying to you. It is not added to any list, and no list exists to add it to.
• Messages you send become ordinary email, so they persist in a mailbox until deleted — unlike everything else here, which never leaves your device. Ask through the same form and we will delete your messages.
• Do not put personal details in a message. The tools do not need them and neither do we.

Who is asked about cookies

Everyone. Every visitor, in every country, starts with analytics and advertising cookies switched off, and is asked once. Nothing that needs your agreement happens until you press Allow.

Analytics

This deployment uses Google Analytics 4 to count visits and see which tools people actually open. It does not receive your name, your email, or any part of your resume — verified directly by watching this site's own network traffic while typing into the builder and exporting a PDF. Beyond the page views and product events this codebase explicitly reports (which tool you opened, whether you exported a resume), Google Analytics' own default “enhanced measurement” feature also automatically reports how far you scrolled and how long you stayed, the same as it does on any other site using GA4's defaults — none of it carries anything you typed.

• The script loads on every visit, before you are asked anything — but it cannot store or read a cookie until you say yes. The cookie banner asks once, and the same answer governs both analytics and ads: decline (or send Do Not Track or Global Privacy Control, honoured automatically before you are ever asked) and Google Analytics falls back to an anonymous, cookieless ping with no stored identifier, the same mechanism Google calls Consent Mode. Accept, and it behaves like standard GA4 from that point on. A browser extension that blocks Google’s analytics domains stops even the cookieless ping, the same as on any other site running GA.
• The builder is measured like any other page — a page view is reported for the URL /resume-builder, same as elsewhere, subject to the same consent rule above. What you type into it is not: that never leaves your browser’s localStorage, and GA has no way to read it. The banner does not open by itself on this page, because ads never appear here, so whatever you already decided elsewhere applies. Cookie choices at the bottom of the page opens it if you want to change that answer.

Google’s handling of the data it receives is described at policies.google.com/technologies/partner-sites.

Separately from Google Analytics above, this project supports an optional second, self-hosted analytics module (src/lib/analytics.ts) that a deployment can point at its own cookieless, IP-anonymising endpoint (Plausible, Umami, GoatCounter) instead of relying on Google. This deployment has no endpoint configured, so the module makes zero network requests and loads zero scripts — it is inactive. The analytics that do run here are Google Analytics, described above, and Ahrefs Web Analytics, listed under Every third-party service below.

When that module is configured, three rules apply, enforced in code rather than by policy:

• Nothing is ever recorded on the builder page. The one route where your resume exists reports nothing — not even a page view.
• No resume content can be sent. The tracking function takes an event name and nothing else. There is no payload parameter to misuse.
• Do Not Track and Global Privacy Control are honoured. If your browser sends either signal, nothing is recorded.

Advertising

This deployment serves ads through Google AdSense. The base advertising script loads on every page except the builder (and a few utility pages: the error, maintenance, announcements and offline pages) as soon as you arrive, independently of whether you have answered the banner below — verified directly by watching this site's own network traffic. The ad placements this site's own code controls wait for your answer: decline, or send Do Not Track or Global Privacy Control, and this site requests no slot for any of them, sets no personalised-ad cookie for them, and Google's consent signal for you stays “denied” from that point on — the same way, confirmed before and after each answer.

• Google and its partners use cookies to serve ads based on your prior visits to this site and other sites, once you have agreed.
• You can opt out of personalised advertising at Google Ads Settings, and review how Google uses data at policies.google.com/technologies/partner-sites.
• Ads never appear inside the builder, and your resume is never available to any advertiser — it does not leave your device, so there is nothing to share.
• You can change your choice at any time under Changing your cookie choice below.
• One limit this site’s own code cannot reach: Google AdSense offers a separate, account-level “Auto ads” feature that can request and place its own ad units on its own initiative, on any page carrying the base script above — independently of the placements this site controls, and independently of your answer to the banner. Whether Auto ads is active is a setting in this site’s AdSense account, not something a consent banner running in your browser can see or switch off. It never runs on the builder, because the builder never loads the base script it depends on.

Every third-party service

These are all the outside services this site loads. None of them receives your resume or anything else you type into the tools.

A browser extension that blocks trackers will stop most of these. The tools keep working without them.

Changing your cookie choice

Your answer is stored in this browser only. Change it here, or with Cookie choices at the bottom of any page, and the banner opens again with your current answer shown. If you switch to Decline, the Google Analytics cookies set by an earlier Allow are deleted and Ahrefs Web Analytics stops recording from the next page you open.

Your resume is your data

Export it as JSON at any time. That file is the complete document in an open format — you can re-import it here, or parse it with anything else.

The rest of the rules for using this site are in the terms and conditions. Shorter answers to common privacy questions are on the FAQ page.