Revisions to DPIA Handbook Page

Why is this change being made?

Privacy is iterating on the content within both the public handbook and the internal handbook as it related to Data Processing Impact Assessments. This MR specifically updates the DPIA Page and moves over some content from the DPIA Policy page, which will be deprecated and removed from the handbook. The bulk of the content on the existing DPIA Policy page will reside within the Internal Handbook.

The rational for these changes is two-fold.

1. The DPIA Policy page is not required as a controlled document. See the discussion in this Issue on controlled documents, beginning at this comment. GitLab's requirements and process for conducting DPIAs is not a 'policy' and this MR, in conjunction with deprecating the DPIA Policy page corrects this in our transparent and public documentation.
2. How GitLab conducts DPIAs, including the details of why, when, how is best suited for internal reference only. Through edits on this page and additional content which will be added to the internal handbook, the Privacy Team is aligning the need to simplify the content on multiple handbook pages and make it easier for Team Members to reference instructions and guidance on DPIAs.

CHANGEME - add the details saying why, not just what.

• Revisions to DPIA Handbook Page

Author and Reviewer Checklist

Please verify the check list and ensure to tick them off before the MR is merged.

• 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, and the content is SAFE
• 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
  • The when to get approval handbook section explains the workflow in more detail
• For transparency, share this MR with the audience that will be impacted.
  • Team: For changes that affect your direct team, share in your group Slack channel
  • Department: If the update affects your department, share the MR in your department Slack channel
  • Company: If the update affects all (or the majority of) GitLab team members, post an update in #whats-happening-at-gitlab linking to this MR
    • For high-priority company-wide announcements work with the internal communications team to post the update in #company-fyi and align on a plan to circulate in additional channels like the "While You Were Iterating" Newsletter

---