Sensitive hiring data.Clear boundaries.
Cernor gives models the context required for the current evaluation.
Source records, access, the locked Standard, policy, retention and final hiring authority stay outside model control.
- AI processing
- Context for the current evaluation
- Source records
- Stored separately from model judgment
- Decision authority
- Remains outside model control
- Security review
- Controls available for review
Your data stays separate from the judgment it produces.
Source records remain independently readable. Cernor scopes the context used for evaluation, stores model judgment separately and keeps access, policy, retention and final authority outside model control.
The judgment can change.The source record does not.
Role and candidate evidence
- Role inputs
- Candidate material
- Follow-Up responses
Readable independently.
Context for this evaluation
- Relevant role context
- Candidate evidence
- Locked Standard context
Scoped to the requested judgment.
Judgment stored separately
- Source-linked
- Versioned
- Receipted
Does not replace the source record.
Source identity · Access · Standard · Policy · Retention · Final human decision
Security starts before the model call.
Encryption, tenant isolation, access control, secrets management, monitoring, recovery and secure development protect the application independently of model behavior.
Encryption
Protected in transit and across production storage.
Tenant isolation
Workspace and project boundaries enforced server-side.
Access control
Sensitive candidate and administrative actions require authorized access.
Secrets & credentials
Production and provider credentials stay server-side.
Monitoring & recovery
Operational events are recorded; candidate and project records are backed up and recoverable.
Secure development & releases
Production changes move through controlled environments and dependency checks.
Retention is a policy, not a side effect.
Retention follows your organization’s policy where retention rules are available. Scoped deletion can be requested for candidate or project records and is reflected in system state.
Your organization
- Active project
Follow the current organization retention policy.
- Closed project
Continue under the configured workspace policy.
- Scoped deletion
Candidate or project records can be explicitly removed.
Security, billing or legally required records may follow separately documented rules.
Every consequential change keeps a history.
Who locked the Standard. Which version governed the evaluation. What changed later.
Cernor appends new state instead of rewriting history.
9 criteria · 2 must-haves
Current Fit 61.0 → 68.0 · policy v30
Commercial ownership elevated
3 dependent decisions reopened
Prior decisions stay readable under the version that produced them.
Security review starts with clear answers.
Architecture, data flow, subprocessors, privacy terms and implemented controls, organized for direct security review.
Does Cernor use customer data to train models?
No. Cernor does not use candidate or role data to train or fine-tune generalized foundation models, and does not intentionally opt it into third-party generalized model training. Production AI processing is selected and configured against documented data-handling restrictions covering training and retention.
What data is sent to model providers?
Only the context required for the current evaluation: the role, the candidate evidence being judged and the locked Standard, sent through the approved production model path.
How is customer data protected?
Candidate and role data is protected in transit and across production storage, with authenticated workspace and project boundaries enforced server-side.
Who can access candidate information?
Access follows workspace and project permissions. Sensitive administrative and consequential actions are attributable to the person who took them.
How long is data retained?
Retention follows your organization's policy where retention rules are available. Scoped deletion can be requested for candidate or project records and is reflected in system state.
Where is data processed?
Production hosting and processing locations are shared through the security review process. Contact us for current deployment details.
Is Cernor SOC 2 or ISO 27001 certified?
Not currently. We don’t claim certifications we haven’t earned. We can provide our current architecture, data flow, subprocessors and implemented controls for review.
Need to review Cernor before using it?
We can provide the current architecture, data flow, model-processing path, subprocessors and implemented controls for review.