@@ -29,7 +29,7 @@ The IT portfolio planning & prioritization process has 6 steps:
### IT Portfolio of Projects
The inventory of all committed and planned projects for the quarter in IT Operations and Enterprise Applications. The [IT Portfolio: Quarterly Commits](https://docs.google.com/spreadsheets/d/1ojnTFGB2iYJz9kNPYdoLc4PeyDqAN60gu9cQBrKpHJQ/edit?pli=1#gid=1316376797) is available for internal team members to track IT planned initiatives. All projects on the IT Portfolio have a Team & Corporate Stack Ranke to align with the overall [global optimization](https://about.gitlab.com/handbook/values/#global-optimization).
The inventory of all committed and planned projects for the quarter in IT Operations and Enterprise Applications. The [IT Portfolio: Quarterly Commits](https://docs.google.com/spreadsheets/d/1ojnTFGB2iYJz9kNPYdoLc4PeyDqAN60gu9cQBrKpHJQ/edit?pli=1#gid=1316376797) is available for internal team members to track IT planned initiatives. All projects on the IT Portfolio have a Team & Corporate Stack Ranke to align with the overall [global optimization](/handbook/values/#global-optimization).
### IT Project Prioritization
@@ -178,7 +178,7 @@ To better organize and manage their work, the IT teams have different label cate
## Compliance Documentation
The IT PMO team supports project stakeholders in gathering all the essential information required for SOX (Sarbanes-Oxley Act) and compliance purposes throughout the project's lifecycle. We have developed multiple templates following the [guidelines](/handbook/business-technology/pmo/pmo-governance/#clear-documentation-for-compliance) provided by the [IT Compliance team](https://about.gitlab.com/handbook/business-technology/it-compliance/). These templates aid in creating comprehensive and well-structured documentation, facilitating the gathering of essential information.
The IT PMO team supports project stakeholders in gathering all the essential information required for SOX (Sarbanes-Oxley Act) and compliance purposes throughout the project's lifecycle. We have developed multiple templates following the [guidelines](/handbook/business-technology/pmo/pmo-governance/#clear-documentation-for-compliance) provided by the [IT Compliance team](/handbook/business-technology/it-compliance/). These templates aid in creating comprehensive and well-structured documentation, facilitating the gathering of essential information.
The IT PMO team collaborates with project stakeholders to create these documents and ensures that all necessary approvals are captured within them.
@@ -297,7 +297,7 @@ The request must include the start and scope of the reduced working hours.
For expecting non-birthing parents, team members can apply for a state benefit (Basiselterngeld, ElterngeldPlus or Partnerschaftsbonus). If a team member is [eligible for Parental Leave](/handbook/total-rewards/benefits/general-and-entity-benefits/#parental-leave), GitLab will supplement Parental Leave pay for up to 16 weeks of Parental Leave or pay the team member's full salary for the 16-week Parental Leave, when used prior to the child’s first birthday. Please notify the Absence Management team at `leaves@domain` which state benefit you are applying for and how much you will be receiving so that payroll can process the appropriate supplementary amount. Team members can find further information on Parental Leave benefits via the [Federal Ministry for Family Affairs, Senior Citizens, Women and Youth](https://www.elterngeld-digital.de/ams/Elterngeld).
@@ -137,7 +137,7 @@ the Professional Services and/or Products as agreed to in the applicable Transac
### 18. DATA PRIVACY
18.1 To the extent Vendor collects, records, organizes, alters, accesses, consults or transmits personal data for which GitLab is responsible and as it relates to the provision of the Products or Professional Services, Vendor shall process such personal data in accordance with the GitLab Data Processing Addendum ("DPA") and Standard Contractual Clauses found at https://about.gitlab.com/handbook/legal/Vendor-DPA. The terms of the DPA are valid upon the Effective Date of this Agreement, and as may be updated by GitLab from time to time, provided any such updates are required by applicable law. In order to comply with applicable law and as provided for in Section 6.2 of the DPA, Vendor shall provide to GitLab its current Sub-processor List(s), prior to completing and/or providing any Services.
18.1 To the extent Vendor collects, records, organizes, alters, accesses, consults or transmits personal data for which GitLab is responsible and as it relates to the provision of the Products or Professional Services, Vendor shall process such personal data in accordance with the GitLab Data Processing Addendum ("DPA") and Standard Contractual Clauses found at https://handbook.gitlab.com/handbook/legal/Vendor-DPA. The terms of the DPA are valid upon the Effective Date of this Agreement, and as may be updated by GitLab from time to time, provided any such updates are required by applicable law. In order to comply with applicable law and as provided for in Section 6.2 of the DPA, Vendor shall provide to GitLab its current Sub-processor List(s), prior to completing and/or providing any Services.
