SHA-256
chain linking every row to the last
measured
Compliance
An audit trail your security reviewer can verify.
Every consequential action in Neuradesk Hire lands in a cryptographically chained audit log: each row carries the actor, IP, timestamp, and a hash linked to the previous row, so tampering breaks the chain visibly. A live integrity check verifies the chain on demand, and an AI compliance copilot summarizes anomalies while reading only event metadata, never candidate content.
30d–180d+
retention scaling Free to Scale
measured
Hash-chained rows
Each audit row includes the previous row's hash. Delete or alter one entry and the chain breaks loudly in the integrity card; an external reviewer can verify independently.
Identity on every row
Actor, IP, and timestamp on every event. Analytics deliberately aggregate; audit deliberately attributes. A compliance log that hides who did what is useless.
AI constrained to metadata
The compliance copilot phrases rule-based anomaly findings and answers audit questions, but it only ever sees event metadata. Resume contents and message bodies are structurally out of its reach.
Export for reviewers
Hand an auditor the export and the verification method; they do not need to trust your word or ours.
Versus Naukri RMS and LinkedIn Recruiter activity logs
Standard activity logs are editable tables that ask reviewers to trust the vendor. A hash-chained log is self-verifying: an enterprise security review or a DPDP inquiry can check the chain math instead of taking anyone's word.
How it works
- 1Consequential actions write chained audit rows automatically.
- 2The integrity card verifies the chain live; breaks surface loudly.
- 3Filter the event stream, or ask the compliance copilot in plain language.
- 4Export the log plus verification method for external review.
Questions, answered
What events are recorded?
Pipeline decisions, candidate data access, document opens, permission changes, and other consequential actions, each with actor, IP, and timestamp. Routine reads of your own dashboards are not the point; decisions and access are.
Can an admin quietly edit the log?
No. Rows are hash-chained: any alteration breaks the chain for every subsequent row and the integrity check fails visibly. That is the property that makes it evidence rather than a diary.
How long is the log retained?
30 days on Free, 180 days on Growth, and longer on Scale. Exports let you archive beyond the retention window.
Related:Hiring IntelligenceThe Screening RoomCandidate Dossier
Tamper-Evident Audit Log
Every plan; retention scales by tier. Start free; upgrade when the volume does.