General: Update privacy statement

[rabeatwork]

Checklist

General

• I tested all changes and their related features with all corresponding user types.
• Language: I followed the guidelines for inclusive, diversity-sensitive, and appreciative language.
• I chose a title conforming to the naming conventions for pull requests.

Motivation and Context

Update Privacy Statement according to Feedback from the Data Privacy Tool

Description

Specified the specific sections we are citing in connection with Article 6(1)(e) of the GDPR in the privacy policy statement. In addition, added the contact information for TUM’s Data Protection Officer.

Steps for Testing

Prerequisites:

1. Log in to DocApply
2. Navigate to Privacy Statement
3. Veriry that specific section for Article 6(1)(e) of the GDPR and the contact information for TUM’s Data Protection Officer was added

Review Progress

Code Review

• Code Review 1

Manual Tests

• Test 1

Screenshots

Test Coverage

No code changes detected - test coverage not required for this PR.

Last updated: 2026-08-24 09:27:48 UTC

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}

[az108]

Generally good change, was just wondering if we should state something about AI or if the seperate ai consent page is enough and if we should use the term controller or something more natural.

[az108]

clarified