Privacy policy

Note: This text is an automatic translation of the German original. In case of doubt, only the German version is legally binding.

This statement applies to the website https://reaktionsgleichung.de/ in all language versions. The controller within the meaning of the General Data Protection Regulation (GDPR) is the person named in the imprint, where you will also find the contact details.

General

Only data that is technically necessary to run the website, or that you yourself explicitly send to the server, is collected.

  • No cookies: This website does not set any cookies.
  • No analytics and no tracking: There are no visitor statistics, no tracking pixels and no advertising.
  • No third-party content: Fonts, scripts and images are loaded exclusively from this server. References to other sites (for example to substance databases) are plain links; only when you click such a link do you leave this website.

Server logs

The website's hosting provider automatically creates an entry in the server log for every request. The hosting provider's settings have been adopted unchanged. The logs are kept for 60 days and then deleted. They serve to secure operation, find errors and fend off attacks (legal basis: Art. 6(1)(f) GDPR). They are not combined with any other data.

An entry in the server log looks like this, for example (the values are made up):

192.0.2.44 - - [14/Sep/2026:10:12:05 +0200] "GET /infopage HTTP/1.1" 200 48213 "https://reaktionsgleichung.de/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:143.0) Gecko/20100101 Firefox/143.0" reaktionsgleichung.de

The individual parts mean:

  • 192.0.2.44 – the (usually dynamically assigned) IP address of the requesting device.
  • - – the identity according to RFC 1413 ("identd"). It is easy to forge and practically no longer used; the dash means "not present".
  • - – the user name, if the page were password-protected. That is not the case here.
  • [14/Sep/2026:10:12:05 +0200] – the standardised time stamp of the request.
  • "GET /infopage HTTP/1.1" – the request: which resource (page, image, file …) was retrieved.
  • 200 – the HTTP status code of the server's response (200 means: everything is fine).
  • 48213 – the size of the delivered data in bytes.
  • "https://reaktionsgleichung.de/" – the referrer: the page whose link the request came from. A "-" in this place stands for a direct request.
  • "Mozilla/5.0 (…) Firefox/143.0" – the self-description of the requesting program (user agent), here a browser. A search robot (crawler) may also appear here.
  • reaktionsgleichung.de – the requested domain. It is recorded because a web server usually hosts many domains.

Storage in the browser (localStorage)

The reaction equation form stores your entries in the localStorage of your browser, that is, on your own device. This includes your experiment records, templates for subforms you have created yourself and the chosen display (light/dark). In addition, small auxiliary values are kept in the sessionStorage for the lifetime of a browser tab. This data is not transmitted to the server; the operator cannot see it.

It remains stored until you delete it in the form or clear the site data in your browser. Please note: anyone with access to your device and browser can see these entries. You can back up your entries yourself at any time as a ZIP file on your device.

Voluntary storage on the server

Only if you explicitly choose "Save to server" in the form is your experiment sent to the server (legal basis: Art. 6(1)(b) GDPR – you are using the storage function). The following is then stored:

  • an archive with the complete content of the form as you entered it – including the server recognition data (place, institution, name, experiment, version, password) and the details of the people working on it (initials, name, editing history), as far as you have filled them in, and, where applicable, a second archive with the attached files;
  • in the database: two check values (hash values) calculated from the server recognition data (place, institution, name, experiment, version, password) and a secret key, the title of the experiment, the storage location of the archives and, where applicable, the chosen deletion period;
  • an access log with the time and IP address of every saving and loading of this record. It serves to trace misuse and is deleted together with the record.

In the database, place, institution, name and password appear only as hash values; in the stored archive they are contained like all other entries. The software does not open the archives on the server; technically, however, the operator has access to them. Anyone who knows all six items of server recognition data can load the record; there is no user account. Therefore choose a password that nobody can guess, and pass the details on only to people who are allowed to see the experiment.

If you tick the deletion period when saving, the record is deleted automatically once this period has expired. Without this tick it remains stored until it is deleted; you can request deletion using the contact details in the imprint.

When you use "Check combination" to see whether a record exists, a hash value of your IP address is stored together with the time for 20 minutes. This makes it possible to limit the number of checks per caller and makes it harder to try out passwords (legal basis: Art. 6(1)(f) GDPR). The IP address itself is not stored in the process.

Requests and error reports

You can report a ticket via the menu item "New request". The title and description you enter are stored, as well as – only if you provide them – your e-mail address and uploaded screenshots. The details are used exclusively to handle your request; the e-mail address only to reply to you. They are deleted as soon as they are no longer needed for this purpose.

Your rights

You have the right to information about the data stored about you, to rectification, erasure and restriction of processing, to data portability and the right to object to processing. To do so, please contact the address given in the imprint. You can also lodge a complaint with a data protection supervisory authority.

Last updated: September 2026