No more disputes over who owns the candidate
Candidate ownership is the trust layer underneath every submission — explicit consent, timestamped claims, and duplicate checks that protect both sides without exposing raw candidate data.
Consent, first
Every submission starts with documented consent
Before a candidate can be submitted to a job order, the submitting recruiter records explicit, scoped consent — what it covers, and when it expires. There's no submitting a candidate 'just to see.'
- Consent is scoped to a specific job order, not open-ended
- Expiration dates keep stale consent from being reused
- The consent record is attached to the submission permanently
Consent captured
Job-specific · scoped · expires automatically
Ownership claim filed
Timestamped, with supporting evidence
No conflicting claim
Checked against the network before submission
Dispute resolution
Conflicts are surfaced early, and decided by people
When two recruiters may be working the same candidate, the system flags it before submission rather than after money has moved — and anything material is routed to a structured human review process, not an automated ruling.
- Duplicate warnings never expose another recruiter's candidate
- Evidence and challenge trails are attached to every claim
- Material disputes go to human review with a recorded decision
Evidence submitted by both parties. Decision pending structured review.
How it's protected
Privacy-preserving by design
Keyed identity hashing
Candidate identifiers are compared cryptographically — raw personal data never leaves its owner's control.
Full audit trail
Every consent, claim, challenge, and decision is timestamped and retained for reference.
Human review for disputes
Material ownership questions are decided by structured human review, never resolved silently by an algorithm.
FAQ
Candidate ownership questions
Protect the relationships you've already built
Consent, ownership claims, and duplicate detection on every candidate you submit.