Skip to content
Jakub Skowronski

Privacy

No cookies, no analytics, no trackers, no advertising. What is recorded, why, and for how long.

In short

This site sets no cookies and loads nothing from other companies: no analytics, no trackers, no advertising, no social-media buttons, no fonts or scripts from a CDN. Every file comes from the site's own address. Links to journals, DOIs or GitHub take you elsewhere only when you click them.

What the server records

The web server keeps an access log, for security (spotting attacks and abuse) and for finding faults. Each request records:

  • your IP address, shortened before it is written: the last of its four numbers is removed (IPv4), or everything after the first 48 bits (IPv6), so the log never holds a full address; and the port number your device used for the connection;
  • the date and time; the request (its method, the site name, the address requested with anything after the “?” and the protocol); the answer's status and size, the size of what you sent and how long it took;
  • the headers your browser sends with the request, with cookies and credentials removed: among them its identification (user agent), the page you came from (referrer), your preferred languages (Accept-Language) and, in Chromium-based browsers, the browser's brand, version and platform (the sec-ch-ua headers);
  • the details of the encrypted connection: the TLS version and cipher, and the site name your browser asked for (SNI);
  • the headers of the server's answer.

The log is deleted automatically after 14 days. The calculation server (the R-matrix evaluations) logs the method and address of each request, without anything after the “?”, with the same shortened IP address and the time; its log is overwritten as it grows and cleared whenever the server is updated. When the web server cannot answer a request (for example while the calculation server restarts), it logs the error with the same details as the access log, the IP address shortened in the same way, in its console log, which is also overwritten as it grows. Nobody else has access to either log, and they are not used to identify visitors or to build profiles. The legal basis is my legitimate interest in running the site securely (Art. 6(1)(f) GDPR).

When you open an evaluation, the server starts a calculation for you and keeps it in memory while the page is open; it is closed, with the parameters you tried, shortly after you leave. To stop one visitor from taking all the calculation capacity, the server also counts, in memory only, how many calculations each address has open; these counts are never written down and are forgotten within minutes.

What your browser keeps

Only for your convenience, on your device, never sent anywhere:

  • your colour theme, if you chose one (theme, local storage);
  • your recent searches in the site's search (search-recent-en, search-recent-it, local storage);
  • for the open tab only, which optional calculation-server features are missing (azure2-api-absent, session storage);
  • for the open tab only, the WebDAQ demo's simulated state, the progress of its guided tour, its language and the notes you closed (keys starting with webdaq-demo:v1:, session storage; the demo's “Reset demo” clears them). In Safari and other WebKit browsers that do not let the demo redirect WebDAQ's own keys (such as authToken, set to demo), those keys stay in local storage instead, beyond the open tab, until you clear this site's data in the browser (“Reset demo” does not remove them);

Clearing this site's data in your browser's settings removes all of it.

Contact

The site is run by Jakub Skowronski, who is responsible for it. For any question about your data, or to exercise your rights under the GDPR (access, erasure, objection), write to jakub.skowronski@unipd.it; you may also complain to your data-protection authority. How the site was made is on the about page.