Rule engine is deterministic — the same resume always scores the same. Deep analysis is generated
by a model and should be read as a screener's opinion, not a guarantee.
What happens to your data
This is a personal side project run by one person, not a company. There is no account
system and no support desk. Please treat it accordingly: submit a redacted resume if you
would rather not hand over your real contact details.
What is stored
Every completed check is written to a database — not parsed in memory and discarded.
The stored row holds the full text of the resume, the full text of the job posting if you
supplied one, the complete report, your uploaded file's name, and your browser's user-agent
string. The uploaded file itself is not kept, only the text extracted from it.
Separately, your IP address is recorded to count unique visitors, with the first and last
time it was seen. In most jurisdictions an IP address is personal data on its own.
Who can read it
The site operator, through a token-gated admin console. Nobody else — but the protection is
a single shared token, not per-user accounts, so it is only as good as that token.
How long it is kept
The newest 500 submissions are kept; older ones are dropped as new ones arrive. That is a
row cap, not a deletion schedule — a quiet month means your submission stays longer.
The visitor list has no cap.
What is sent to Google
With Deep AI analysis ticked, the resume text and job posting are sent to Google's
Gemini API, and are handled under Google's terms once they arrive. Drafting a cover letter
does the same. Untick the box and the check runs entirely on this server — you still get the
full rule-based report, just without the model's review.
Deletion
There is no self-service delete. Ask the operator and the row will be removed.