Updates to Recruitment Privacy Policy

Why is this change being made?

The Recruitment Privacy Policy is being updated to bring it in line with language used in GitLab's public facing Privacy Policy (personal data instead of personal information). This update also reflects a change in the process and workflow for candidates and applicants to submit a data subject request (changing from an email contact to a form submission). This new workflow will allow both the privacy team and the People Team to more efficiently manage applicant/candidate requests to delete their personal data and access the personal data which has been collected as part of the recruitment process while also providing needed oversight and reporting capabilities pursuant to data privacy laws.

Author Checklist

• Provided a concise title for this Merge Request (MR)
• Added a description to this MR explaining the reasons for the proposed change, per say why, not just what
  • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added.
• Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI)
  • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the Maintained by section on the page being edited
  • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
• If the changes affect team members, or warrant an announcement in another way, please consider posting an update in #whats-happening-at-gitlab linking to this MR
  • If this is a change that directly impacts the majority of global team members, it should be a candidate for #company-fyi. Please work with internal communications and check the handbook for examples.

---