SAP Knowledge Base Article - Public

2080965 - Candidate Anonymization - Recruiting


  • Ability to control what data is anonymized when a candidate record is purged.


  • Recruiting Management.


   Change Type: Opt-In; Requires engaging a Partner consultant . This feature is used in conjunction with the Data Privacy Consent 2.0 tool: 2341240 .

   Previous Behavior: Information from purged profiles is deleted from system.

   New Behavior: Information from purged profiles can be anonymized based on business rules, allowing statistical reporting to remains intact while honoring the candidate’s privacy.


  • What system actions cause a candidate to be anonymized?
  • Declining DPCS



  • Requesting to be deleted (“Deleted On Demand By Candidate” or "Deleted On Demand By Admin").
  • Scheduled data purge (DRM 2.0) - for more information please refer to the following Knowledge Base Article: 2088065.
  • What happens in the system after a candidate is flagged for anonymization?
    • The candidate will not return in search results.
    • The candidate / applications can no longer be actioned (statused).



  • Outstanding Interview and Offer To-Dos are marked completed.
  • Agencies will not see the candidate available for submission.
  • If the candidate returns, they are treated as a brand new candidate and must recreate their account.
  • In Ad-hoc reporting, you can elect to include or exclude anonymized data.


Use cases:

  1. Clients who change their DPCS can now enforce their candidates to accept the newest version when they return to the site.
  2. Candidates who decline the DPCS will have their profile information purged.
  3. Candidates can self-purge their profiles on demand.
  4. To maintain statistical reporting, profiles are anonymized (not deleted) based on client specified business rules.
  5. Routine data purging will now honor the anonymization business rules.


KBA , sf candidate , sf data privacy , LOD-SF-RCM , Recruiting Management , How To


SAP SuccessFactors HCM Core all versions