Security you can check, not just trust.

For each certificate, HR can open every crossing to and from the engine: time, direction, the number of replaced items per category, the SHA-256 of the payload and the pseudonyms used. Real values are never shown there. The view exports as CSV.

Managers, or HR, rate each aspect of performance and conduct. The AI writes text that matches those ratings and cannot change them. The overall level is calculated from the ratings, not chosen by the model.

Each evaluative sentence records the aspect and rating it expresses, and HR sees this in the editor, so every sentence can be traced back to the rating behind it.

Before HR review, every AI draft goes through the engine's fairness analysis. A blocking finding holds the certificate until an edit clears it or an HR partner overrides it, and the override is recorded in the audit trail. Employment confirmations, which are built from a template without AI, skip this step.

No certificate reaches an employee without review and finalisation by an HR partner or administrator. Automations can start requests but never finalise them.

We do not use customer data to train, fine-tune or evaluate models, and customer requests never enter our reference corpus.

Each certificate names its jurisdiction, Switzerland, Germany or Austria, explicitly instead of guessing it from the text. Only the Swiss rules have been reviewed so far; assessments for Germany and Austria are marked as limited.

Every lifecycle step and change is written to an audit log in which each entry carries the hash of the previous one, so an edited entry breaks the chain. The chain is checked when a dossier or verification page is opened, and each certificate's dossier can be downloaded with its audit entries.