Algorithmen und Datenstrukturen 2025

Data protection declaration

This page was translated automatically. The terms of the German version apply. {.p .important}

The use of this service is aimed exclusively at participants of the event/lecture. This requires access (Login) to the non-public part.

When this access is set up and used, personal data is stored.

We take strong efforts to protect this data appropriately and treat it confidentially. In addition, we will not collect more data than is necessary for the purpose of the event and for the technical Implementation of this service.

What is stored and why?

We store your master data consisting of name, user name, E-mail, matriculation number, subject and semester. These data are used for the unique assignment of persons and achievements1. Subject and semester are also used for statistical evaluations. We also store your exercise group and your tutorial, if applicable, and all settings you have made yourself (e.g. color scheme).

We also store all data resulting from performances in the semester during the semester. These are e.g. voting points. The sum of these performance ultimately results, for example, in admission to the exam Examination

We store the following timestampsWhen was the access created? When was the last time you logged in? – and count how often you logged in or submitted something submitted something. This data is used to recognize inactivity and abuse.

In addition, data is collected that is technically required and controls the service and in particular the submission. These are, for example timestamps that are required for rate limiting during submission or “one-time tokens” for resetting a forgotten password.

Submissions

The submissions contain the solutions to the tasks, a submission Submission consists of one or more files (usually source code).

We save the submitted files in all versions. The versioning is done to make incorrect submissions or accidental overwriting Accidental overwriting and to avoid data loss avoid data loss. The type of versioning is technically conditioned, we use for this purpose Git.

The submissions themselves are anonymous. We reserve the right to store the submitted files for the purpose of plagiarism control. This is because we must be able to recognize, for example, “popular solutions of recent years” as such and to sanction such plagiarism if necessary sanction such plagiarism.

Therefore, please do not include any names or student numbers in submitted files (e.g. in comments)!

Please note: Working in groups may be optionally allowed under the condition that all names are specified. In this case, the group work and thus the indication of the names is done voluntarily and in the knowledge that this data will be stored as mentioned above!

In terms of data protection and for yourselves (learning effect), we recommend that you develop and submit your own solutions and submit them.

Log files

The submission system generates so-called log files, in which events such as individual requests or their individual Individual steps or error states are recorded temporarily are recorded. The log files usually contain an IP address* and/or a user name in order to uniquely identify events and to be able to trace related events in their sequence even over several HTTP requests.

The log files are used exclusively for tracking down errors in the submission system and their traceability as well as the detection of misuse or attacks.

The log files are “rotated” regularly and old data is deleted.

As the submission system is still under development and we must expect errors. The log files are an indispensable tool in this An indispensable tool in this phase. Therefore, the data may be kept for a few weeks in order to recognize error patterns in case of doubt be able to recognize error patterns. For the same reason, the log files are not anonymized, as this is the only way we can respond to tips and complaints such as such as “This or that did not work for me. “ appropriately.

Under no circumstances are the log files used to deduce user behavior patterns!

How long is data stored?

At the end of the semester we delete all data that is no longer required Data, in particular access data (password hashes) and all remaining remaining log files.

We archive the services rendered together with the master data So that in the future it is possible to trace whether a person has fulfilled a a required condition (e.g. admission to an examination).

Archived data is no longer accessible via this service. This applies in particular to subsequent events. This means, for example, that an exercise leader of the event in the following year has no direct access to the archived data.

Archived data is deleted** after three years (6 semesters) at the latest. With these data, the submissions are also deleted. The submitted files themselves may remain stored for the For the purpose of plagiarism control or for tests, in any case, the personal assignment will be deleted. (See note in the section *Submissions)

Do you use cookies?

Yes, we use a so-called session cookie. The information stored information is encrypted and proves that you are currently logged in are logged in. Without user activity, this cookie is only valid for valid for a short time.

For technical reasons, the cookie also stores messages relating to the immediate following information retrieval (HTTP GET request) are also stored in the cookie for this stored for this one request. These are usually success or error messages Error messages. The cookie can also contain security features, which are intended to prevent misuse (e.g. session hijacking).

We do not use any other cookies and in particular no cookies (or external services) that are used by us or by third parties for user tracking (often also euphemistically “for an improved user experience”) could be used!

Do you use external services or scripts?

No, we do not use external services. All services are implemented on servers at the FIN. No data is transmitted to external Transmitted to external services. This applies in particular to the Plagiarism control! Access to our servers is strictly regulated.

We use some external fonts, which are fonts that are loaded by the browser from external sources (Google Fonts and Font Awesome).

We use MathJAX for the display of mathematical formulas. This is a Javascript library that controls the formula set and also provides fonts (fonts) are also provided.

Is the transmission of data encrypted?

Yes, all data is transmitted in encrypted form. For this purpose HTTPS and internally SSH are used.

Do you save my password?

No, we store a password hash and use bcrypt. Your password cannot be reconstructed from the hash! reconstructed!

Note on security: Nevertheless, it is generally not a good idea Idea to use the same password several times for different services! for different services!

Should I expect e-mails?

No, we do not send automatically generated e-mails or e-mails to E-mails or e-mails to groups of people. Exceptions are the initial signup and resetting a forgotten password as well as personal communication that is independent of this service.

How can I view my data?

As long as the service is active and you have access, you can (almost) all stored personal data directly and at any time in the system at any time: You can find your master data in Profile, your submissions and number of votes etc. can be found here.

This list does not include all data that is necessary for the algorithmic Control of the submission (e.g. timestamp, Git hashes).

Data that is generated in the course of plagiarism control is generally not visible. This is because submissions are always considered in pairs, so that each entry refers to at least refers to at least two persons.

What if my access is blocked?

Access to this service can be blocked by an administrator blocked by an administrator.2 On the other hand, you can log out of the event yourself within a yourself from the event within a specified period of time and lose access to the system as a result of blocking.

Users whose access is blocked are not automatically deleted. The reason is, on the one hand, that it must be possible to must be possible to remove the block without losing data (i.e. without disadvantage for the user). On the other hand, we archive the Information that a user was registered in the event was registered. This is because the resources of each event are limited, and we we reserve the right to delete those participants who repeatedly register and and thus deny others the opportunity to register or to be assigned to a particular To a specific exercise group (unintentionally but) indirectly, will not be considered for *follow-up events or will be given lower priority to be considered.

If your access is blocked, please contact a Instructor or the person responsible for the event, if you wish to request access or view your personal data would like to view. In any case, we want to avoid insecure transmission of this data, e.g. by e-mail.

Can I change my data?

You can only change your data yourself to a limited extent.

  • you cannot change master data yourself. Please contact Your trainer if something needs to be corrected. In particular the user name and e-mail address cannot be changed be changed.
  • You can only change or influence the assignment to an exercise group at the beginning of the Semester. The exact conditions for this are given elsewhere.
  • Submissions can be changed by resubmitting them, this of course only applies during the processing period.
  • You can view achievements (e.g. voting points) but not change them but not change them.
  • you can view timestamps and counters (where appropriate) but not change them not change them.
  • Personal settings in the system (e.g. color scheme) can be changed at any time.

Please check your data regularly This applies in particular to services rendered: If you notice an error in the list please contact us as soon as possible.

Small groups in tutorials

If small groups are formed in the course in the system for working on tutorials, then the members of a small group must be able to Be able to communicate with each other. To make this possible, the first name, last name and email address of the other Members can be viewed.

Working on exercises in groups

If tasks are to be worked on in groups during the course are to be worked on in groups, the names and e-mail addresses of all members of a group – the names and e-mail addresses of all members of their own group can be viewed. This is intended to facilitate communication and within the group.

As a rule, this refers to small groups, which may be put together by us and generally not to entire exercise groups Exercise groups.

Who has access to my data?

Only those persons have access to personal data, who organize the event and therefore have to work with the data in particular to collect and view data. This includes Lecturers, trainers and, if applicable, tutors. It may also be necessary that technical staff (server administrators) come into contact with data Come into contact with data. (Another exception is the organization of small groups in tutorials, see above.)

For the purpose of transferring services that have already been provided already archived data can be accessed. This is done “manually” via archived files and exclusively for participants who participate in the same event again

All persons who have access to personal data are bound to secrecy!

Contact and data protection officer

You can reach the persons responsible for the lecture as well as And tutors personally, e.g. after the lecture or during the exercise. Of course you can also reach us by e-mail. You can find the contact details in the lecture materials and in the LSF.

If you have any questions about data protection, please contact us at any time us at any time, in person or by e-mail, or contact the data protection officer.


  1. The exact conditions for the services to be provided are not the subject of this declaration and will be published separately! published separately! 

  2. The reasons for blocking access are not the subject of this declaration. Examples include misuse or inactivity. 

_flag_de