Privacy Guidance for Feature Requests

Back to "Privacy"
Privacy Guidance for Feature Requests
1 Check whether a PRIVACY.md exists
Please check whether a PRIVACY.md exists for the affected component:
2 If a PRIVACY.md exists
Compare the proposed Feature Request with the existing PRIVACY.md and determine whether the feature introduces, changes, or removes any processing of personal data.
If the existing PRIVACY.md fully covers the Feature Request:
Add a link to the respective PRIVACY.md in the “Privacy” section and state:
LINK: PRIVACY.md does not need changes.
Describe the changes in the “Privacy” section of the Feature Request and update the respective PRIVACY.md accordingly.
In particular, indicate:
- which new or additional personal data will be processed, e.g. username, first name, last name, user ID, owner information, comments, notes, grading status, timestamps, or similar data;
- which new or changed processing activities involving personal data are introduced by the feature;
- whether any personal data or processing activities described in the current PRIVACY.md will no longer be used;
- whether the feature uses the most privacy-friendly setting as the default (Privacy by Default);
- whether data minimization or pseudonymization is used wherever possible.
Please make sure that these changes are both documented in the Feature Request and reflected in the updated PRIVACY.md.
3 If no PRIVACY.md exists
If there is currently no PRIVACY.md for the affected component, please contact privacy@lists.ilias.de so that the Privacy Clinic can initiate the preparation of a new PRIVACY.md.
4 After implementation
If the Feature Request is accepted and implemented, please ensure that the component's PRIVACY.md is updated according to the implemented feature.
In the “Implementation” section of the Feature Request, indicate whether the PRIVACY.md was updated or whether no changes were necessary.
Questions
If you have any questions regarding the privacy implications of the feature, please contact privacy@lists.ilias.de.