Pilot trust sheet

Current pilot operating posture

Nimloth is in controlled pilot.

This page describes how Nimloth is intended to be used today: as a structured hiring workspace that helps companies define roles, collect better candidate evidence, and support human review.

The pilot is designed with clear product boundaries. Nimloth does not automate hiring decisions, does not score or rank candidates, and does not replace employer judgment.

Nimloth does not currently claim formal compliance certification or enterprise procurement readiness. The purpose of this page is to be clear about what the product supports now, how responsibility is handled, and where its current limits are.

Product role

What Nimloth supports

Nimloth helps employers define a role, build structured candidate-facing application work, review submitted evidence, and prepare accountable human follow-up.

The product is designed to support better hiring judgment. It does not replace the employer's responsibility for evaluating candidates or making hiring decisions.

Pilot scope

Controlled and employer-led

During the pilot phase, Nimloth should be used in bounded hiring workflows with a limited group of trusted users.

Employers remain responsible for role setup, application design, candidate review, and any hiring action taken outside the system. Nimloth supports the process, but the employer remains the decision-maker.

AI boundary

AI supports; humans decide

AI may help employers summarize submitted evidence, identify gaps or uncertainties, and prepare interview follow-up questions.

AI does not make hiring decisions.

No scoring.
No ranking.
No automated hiring decisions.

Visibility

Candidate and employer boundaries

Candidates use candidate-facing application and account surfaces. They can submit and track only their own applications.

Employer review workspaces, internal notes, admin views, billing data, and employer-only role context are not candidate-facing.

Employers can review applications submitted to their own roles. Internal support access is bounded and used only for support, readiness, and operational work.

Role context

Employer-only context stays private

Employer-side role definition and role foundation help structure the employer's review workflow.

They are not shown to applicants as a hidden answer key, scoring model, or internal evaluation workspace.

Data handled

Operational data used to run the service

Nimloth may handle employer account data, company and workspace data, job setup information, published application content, candidate contact information, submitted answers, timestamps, review states, and operational metadata needed to run the service.

This data is used to operate the product, support the hiring workflow, and maintain the separation between candidate-facing and employer-only surfaces.

Security posture

Current operating controls

Nimloth keeps secrets and runtime credentials server-side and avoids rendering secrets in browser pages.

Operational access is bounded and used for support, readiness, and maintenance work. Internal write actions are intended to be explicit, limited, and recorded where supported by the current system.

Current limits

Nimloth is currently in controlled pilot. Use should remain supervised by the employer and limited to appropriate pilot workflows.

Customer-specific legal, data retention, or operational commitments require written agreement.

Nimloth does not currently claim independent compliance certification, formal audit completion, or broad enterprise procurement readiness.

Operational support may require direct coordination with Nimloth.

Support

Support and trust questions

For pilot support, contact Nimloth through the agreed pilot channel or the public contact page.

Legal and data-handling information is available through the Trust & Legal hub.