Answer a candidate, a lawyer or the CNIL, with the facts.

What Ojja shows you

1. The state of your tools on a given date. On any date since your first readout: what was active, what the vendor said about it, what you had decided. The means to answer a candidate, a lawyer or an inspection.
2. What each feature does, according to the vendor. Recommends, ranks, sorts, filters or rejects; human review documented or not; data used; training on your data; where it is processed. When the vendor says nothing, we write it: not documented by the vendor.
3. What the vendor documents of its logic. For each feature that ranks, sorts or evaluates candidates or employees: the criteria and the data it uses, according to the vendor, with the address of the page read. Yes, partly or no; “not documented” as long as nothing is found.
4. Where each fact comes from. Read in your tools, declared by you or inferred: each line says so, with its date. A feature's activation date stays “not read” until a reading or a dated declaration gives it.
5. The answer to a candidate: the state of your HR tools on the day of their application.
6. For a CNIL inspection. The AI part of an inspection: the features that touch personal data, what they read, where the vendor processes it, whether it trains its models on it, and the decisions recorded, with their dates and sources. A recruiting part covers your HR tools.

Files for third parties come with Ojja Watch Committee; you can also ask for a single one.

Fictional example

A rejected candidate writes to a company: which tools processed their application, and how? Its recruiting software was found behind its website's careers link, then confirmed by the company; the company declared the activation date of the feature that sorts applications. The state of its HR tools on the day of the application shows this feature active, what the vendor says about it, and what it documents of its logic: partly, with the address of the page read. The company writes its answer.