Security and integrations
Each person sees their part of the search, and nothing more.
Candidate data is personal data. Access is decided by role, contact details stay with the firm, and every decision is recorded.
Sample policy text for a fictional product. Replace it with your own reviewed policies before launch.
Access
Three roles, three views.
| Role | Sees | Cannot see |
|---|---|---|
| Recruiter | Every candidate, note, scorecard and contact detail in the searches they work on. | Open searches marked confidential unless they are assigned to them. |
| Client reviewer | Only the candidates sent to them for their own roles: the recruiter's case, the scorecard and the profile summary. | See contact details, other clients, unsent candidates or internal notes. |
| Candidate | Published roles and their own application. | See any other candidate, any client feedback or recruiter notes. |
Candidate data
Handled as if the candidate were watching.
Consent at application
The application form explains who will see the candidate's details and asks for consent before submitting.
Retention by rule
Unplaced candidates are deleted 24 months after their last activity unless they renew consent. Firm plans can set their own period.
Contact details stay with the firm
Email and phone numbers never appear in the client portal. Introductions happen through the recruiter.
Every decision is logged
Stage changes, shortlists sent and client verdicts are written to an activity history the firm can export.
Integrations
Connections the product describes.
Listed for the fictional product. None of them is connected in this website.
- Sample
Job boards
Publishes roles to a hosted job board; syndication to external boards is configured per firm.
- Sample
Calendars
Reads panel availability to offer interview slots and writes confirmed interviews back.
- Sample
Email
Sends shortlist notifications to client reviewers and confirmations to candidates.
- Sample
Single sign-on
SAML and OpenID Connect for recruiter accounts on the Firm plan.
This website
What the demo you are using really does.
The workspace, client portal and job board on this site are a frontend demonstration. Here is the exact line.
Included
- Marketing pages, a hosted-style job board, a recruiter workspace and a client portal as frontend screens
- A browser-only demo: changes are kept in localStorage on this device and can be reset
- Forms with validation that send nothing unless you connect an endpoint
Not included
- Accounts, sign-in or access control — the view switcher is navigation, not security
- A database, API or server; no candidate data leaves the browser
- Email or calendar delivery, CV parsing, AI, payments or job-board syndication
Where is candidate data stored?
In the fictional product, in the region chosen at sign-up. In this website template nothing is stored on a server; the demo keeps changes in your browser only.
Can a client see another client's candidates?
Not in the product described here: each reviewer is scoped to their own roles. The demo's client switcher exists to show the screens and is not an access control.
Do you train AI models on candidate data?
The product described here uses no AI on candidate data.