Loading
Loading
Applicants
Written for a candidate, not a lawyer. It explains what is collected, what an automated pass does and does not do, and who can see the result.
PLACEHOLDER — no applicant privacy notice has been supplied. Before launch this page must explain, in plain language: what is collected, who can see it, how long it is kept, how to withdraw consent or ask for deletion, how a human reviews and can override any automated screening output, and how to reach the data owner.
The one rule that matters
Automated screening never rejects an applicant and never sends an offer.
Every application is read by a person. Automated screening produces an advisory score with written evidence only — it never rejects anyone on its own, and a human reviewer can and does override it.
How the advisory pass works
Each job states what it screens on, with a weight and whether it is required. Where the owner has not specified a requirement, the page says so — and absence is never treated as a gap.
The pass reads the words you wrote. It does not infer skills you did not mention. A CV is used only as a document a reviewer may open — never as a scoring input.
Each criterion result shows the exact sentences it relied on, plus a plain-language explanation. If the explanation looks wrong, that is a reviewer problem to fix, not yours.
Every application is read by a person. They see the score, the evidence and the explanation together, and they can overrule the advisory output with a written reason that is stored on the record.
If you need an adjustment to the process, that is a conversation. It is never entered into the score and it never counts against you.
Your documents
Share a CV only if you want us to have one. In this demonstration nothing you select is uploaded, stored, or transmitted anywhere — the file is never read.
A CV is never required. Skipping it does not count against you and will not be read as a lack of interest.
In the live version a document you share is stored privately and referenced by an opaque reference. It is never exposed at a guessable public URL.
Your document is used to assess you for roles you applied to. It is not used for unrelated marketing and not shared with a third party.
You can ask for your application and any document to be deleted. How long records are retained, and who the controller is, must be stated in the reviewed notice before launch.
Consent and the record
Agreeing to be assessed records a timestamp and the version of the privacy notice you agreed to. If the notice changes materially, the version changes with it — so it is always possible to show what someone agreed to at the time.
Current policy version recorded by this demo: applicant-privacy-draft-v0 (placeholder)
Common questions
No. There is no code path in this product where a screening score produces a rejection. A person decides, every time. If a rejection ever happens, the reason is recorded and you can ask for it.
They are stored with your application and used only to assess you for the roles you applied to. Ask for deletion or export and a person handles it.
It must not, and the published criteria say so. An accessibility need is a conversation with a person, never a scoring input. If a system ever behaved that way, that is a bug to report — use the accessibility route and it will be treated seriously.
A reviewer can, and they see the evidence alongside the conclusion. Candidates are not shown the score, because a number encourages exactly the over-trust this design is trying to avoid. Ask for the reasoning and a person will explain the decision in plain terms.
No. Those questions are answered by a person, deliberately. An automated answer to “what does this pay” or “can you sponsor me” would be a guess dressed as an answer, which is the failure mode this whole site is built to avoid.