Skip to content
RecruitAPI

Security

Built for sensitive records.

Candidate and client information is personal. Here’s how the JobAdder MCP keeps it under your control.

Activity in JobAdder

Today, from your AI assistants

  • Meeting loggedDana Wright · Harbour LogisticsJess R. via Claude✓ Approved 2:14pm
  • Candidate added to jobPriya Shah → Payroll OfficerSam T. via ChatGPT✓ Approved 11:02am
  • Shortlist readFleet Coordinator · 4 candidatesJess R. via ClaudeRead only

Draft for review. This document has not been finalised and may change before launch.

Every consultant signs in

Each person connects with their own JobAdder login. No shared passwords, and we never see JobAdder passwords.

JobAdder permissions apply

The assistant can only see and do what the signed-in consultant can in JobAdder.

Approval before writing

Changes to JobAdder wait for the consultant to approve them, and you choose which write actions are on.

Recorded against the person

Every change is made as the consultant who approved it, so JobAdder’s own history stays accurate.

How we handle your data

  • We connect to JobAdder through its official API. No screen scraping or browser extensions.
  • Connections are encrypted in transit, and the tokens that let us act for a consultant are encrypted at rest.
  • We fetch records to answer a request and don’t keep copies of your JobAdder data beyond what that needs.
  • We don’t use your data to train AI models.
  • You can disconnect a consultant, or your whole agency, at any time.

Records are passed to the AI assistant you choose, under your agreement with that provider. See our privacy policy for more.

Reporting a vulnerability

If you think you’ve found a security issue, email security@recruitapi.com with the details and how to reproduce it. Please give us a reasonable chance to fix it before telling anyone else, and don’t access or change data that isn’t yours. We’ll acknowledge your report within two business days.