Privacy Policy

What ATS Resume Optimization collects — and why the resume you check never reaches our servers.

Introduction

ATS Resume Optimization (atsresumeoptimization.com) is an ATS readiness checker for resumes. It is operated by an individual, not a company, and this page tells you exactly what touches our servers.

The short version: the free ATS check runs entirely inside your browser. Your resume file is not uploaded, and there is nothing for us to receive.

The free check: what never happens

When you drop in a PDF or DOCX, or paste text, the file is parsed by JavaScript running on your own device. During that check:

The file itself is never sent anywhere. No upload request leaves your browser.
The extracted text, the parsed layout, your score and the list of issues are held in the page's memory only. Reload the tab and they are gone — we do not write them to disk, to localStorage, or to any database.
The identity block of your resume (name, email, phone, address, profile links) is parsed locally as well, because a few checks need it (for example, "is your contact info actually in the body text?"). It is used for that calculation and for nothing else.
We do not currently run third-party analytics, session recording, advertising or ad-exchange scripts on this site. ads.txt is empty today for the same reason; if we ever join an ad exchange, it will list only our publisher ID.
No account, no email address, and no sign-in is required to use the check.

Two things may be stored on your device. Your theme choice. And, if you arrive from a link that carries a campaign tag (utm_source), that tag is kept in a cookie for 30 days so we can tell which link brought you here. Neither is sent to us while you only use the free check. If you later create an account, sign-up reads that cookie and saves the tag on your account record. Clearing your browser data removes both.

If you create an account

An account exists only for features that need one. If you sign in — now or later — we collect:

Account information: your email address and a hashed password. If we enable a social sign-in and you choose it, we also receive the name and profile picture that provider (for example Google) shares when you authorize.
Credits and orders: the balance and transaction records for any paid feature you use. Payment cards are handled by our payment processor; we store the order and its status, not your card number.
Usage details: which feature you used and when, so we can bill correctly and debug failures.
Session cookies: to keep you signed in.
Device information: browser and device type recorded when a sign-in session is created, to diagnose crashes and abuse.

We do not collect your resume content through an account unless you deliberately use a feature that sends it, and any such feature shows you exactly what is about to leave your browser before it does.

Where paid AI features will differ

If we ship AI-powered rewriting or interview practice, those features send text to a model provider. When that happens, the text we send will be de-identified first: employer names, school names, people's names and dates are replaced with reversible placeholders inside your browser, and the identity block never enters the request at all. The AI features collect no account or identity information; they receive only the de-identified body text needed to answer your request. We will update this policy before any such feature goes live.

We describe this honestly as PII-minimized, not anonymous. A sufficiently unusual job title or project detail inside the body text can still identify you to whoever reads it.

Data storage and security

Account data is stored in a managed database hosted on Cloudflare. Sign-in secrets are held in encrypted environment bindings, not in page source or in our repository. We use HTTPS everywhere.

No method of transmission or storage is 100% secure, so we do not promise absolute security — we promise the specific, checkable things above: your resume file is not uploaded, and the free tool has no server-side storage to breach.

We do not sell personal information. We share it only with the processors needed to run the site (Cloudflare for hosting and DNS, Google for sign-in, and a payment processor for orders), to comply with a legal obligation, or to protect our users or ourselves from abuse.

Privacy Policy

Introduction

The free check: what never happens

If you create an account

Where paid AI features will differ

Data storage and security

Retention and deletion

Changes to this policy

Contact