Skip to content
Hypamoon

For teams that run on RecruitNow

RecruitNow GDPR candidates to remove each month

Cockpit anonymises a candidate when the retention period ends without a reply. For rejected and inactive candidates RecruitNow advises removing them by hand, because as long as they stay in the pool they keep getting extension requests that no longer make sense.

How it goes today

  1. Search Cockpit for candidates with a rejected or inactive status.
  2. Open each candidate to see whether a match or placement is still running.
  3. Remove the candidate so their details are anonymised.
  4. Keep a note of who was removed and why.

How it can go

Rejected and inactive candidates on one list each month, removed after your check.

On the first of each month you get a list per branch of candidates who are rejected or inactive, have no open match or running placement, and have not changed for the period you set. Next to each name you see the status, the last change and when consent for mediation was given. For each one you approve, the recruiter gets a task in Cockpit to remove the candidate, so the anonymising and the audit log stay in Cockpit.

Say this in ChatGPT, Claude or Copilot

Your chat gets connected to Hypamoon first, with this request filled in. RecruitNow first switches on access for your company when you ask them, which can take a few business days. After that you get the key, or create it yourself, and paste it in the portal, never in the chat.

Your request

With Hypamoon, on the first of each month, list the candidates in RecruitNow Cockpit who are rejected or inactive, have no open match or running placement, and have not changed in twelve months. Show me per branch their status, the last change and when they gave consent. For each one I approve, create a task in Cockpit for their recruiter to remove the candidate.

RecruitNow creates an API key for your company and your Cockpit environment when you ask your implementation manager or support, and tells you the address of your environment. The key stays valid until RecruitNow revokes it. It stays yours.