Privacy Policy

The short version: there is no server, so there is nothing to send your resume to.

What we collect

Nothing about your resume. This application has no backend, no database and no authentication. Your resume, the job descriptions you paste, and your theme preferences are stored in your browser's localStorage and are never transmitted anywhere, under any circumstances.

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 — on every page, including this one — a request to Google Analytics. See the Analytics section below for exactly what that carries. 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 single exception to everything above, and only at one moment. Opening that page sends nothing. 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. That is the only request this site makes to anyone else, and it happens only because you asked for it.

  • 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.
  • Do not put personal details in a message. The tools do not need them and neither do we.

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 banner below 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 itself does not appear on this page — ads have never appeared here either — so whatever you already decided elsewhere on the site is what applies here too.

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 only analytics actually running on this deployment is Google Analytics, described above.

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 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 by clearing this site’s storage.
  • 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.

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.

🚀 Share this resource

💙 Help someone else with their job search.

👀 Preview

I found this useful and thought it might help with your job search. https://atsresumekit.com/guides/ats-resume-format

🚀 Help a Job Seeker

Found this useful? Share ATSResumeKit on LinkedIn or social media. Your one share could help someone create a better resume and get closer to their next job.

❤️ Thanks for helping us reach more job seekers!