Privacy

What Pitrig records

Pitrig counts how its site and its apps are used, so that the next fix goes where it helps most. It never stores your name, your files or your network address, and it sets no cookies.

Last updated 20 November 2026.

Who runs Pitrig

Pitrig is a personal open-source project run from Poland by Illia Lukashchuk, the data controller under the GDPR: the person who decides what is recorded and why. Questions and requests about your data go to contact.pitrig@gmail.com.

This website

The site stores nothing in your browser: no cookies, no local storage, no third-party scripts. For each page you open, a download, or a flash from the web flasher, the server records:

  • the page or file, and the time;
  • a visitor code: a one-way hash of your network address and browser together with the month, so visits within a month can be counted without storing either;
  • the country your address belongs to, the name of your operating system and browser, and the site you came from (its domain only), or the tag in a ?ref= link;
  • how long the page stayed on screen and how far it was scrolled, which part of the landing page or which outside link was clicked, and the answer if you choose one under “Where did you hear about Pitrig?”;
  • for the web flasher, whether the flash finished or failed.

A second hash of your network address, keyed by a secret the database keeps, is stored with page views and configurator downloads and erased after 15 days. It lets a new configurator install be matched to an earlier visit from the same network. Your network address itself is never stored. Automated visitors such as search engines are recorded with their user-agent string so they can be told apart.

The contact form

When you send the contact form, the site passes your email address, the topic and your message to Resend, an email delivery service in the United States, which delivers them as one letter to the Pitrig mailbox at Gmail. The site itself keeps no copy. Resend keeps its log of the letter for 30 days; the letter stays in the mailbox while the conversation needs it and is deleted when you ask.

The message is used only to answer you, a legitimate interest under Article 6(1)(f) GDPR. To stop floods, the site counts the messages from each network for one hour under the keyed hash described above, and erases the count within a day.

The configurator and the SimHub plugin

Official releases send short usage reports to this site. They are on by default and one switch on the configurator’s Info page turns them off for both apps. A report carries:

  • a random install number created on your PC, the app version, and the operating system and processor type;
  • that the configurator started, that a board was found (its model and firmware version), that a save to the board finished, that the SimHub plugin delivered data (and its version), or that a part of the app crashed (its type and the reason the system gave);
  • from the plugin: once a day that it runs and the SimHub version, which game is running, and which board model it feeds;
  • whether Pitrig was already installed before.

Reports carry no names, file paths, dashboards or serial numbers. To match a new install’s first report to a visit, the site uses the network hash described above (erased after 15 days) and keeps the matched visitor code with the report.

The configurator also asks GitHub for new releases, and downloads a Google font from Google when you add one. Those requests go straight to GitHub and Google under their own privacy terms.

Why, and on what basis

The records answer a few questions: which pages help, whether downloads lead to a working board, which boards and games to support first, and whether people come back. The legal basis is a legitimate interest in understanding and improving Pitrig (Article 6(1)(f) GDPR). Nothing is sold or used for advertising.

Where the data lives and for how long

The site runs on Vercel and the records are kept in a Neon Postgres database, both in the United States, under their data processing terms. The network hash is erased after 15 days; the other records have no fixed end date and are kept for comparing trends over time.

Your choices

  • Switch the usage reports off on the configurator’s Info page at any time.
  • Ask for the reports of your install to be shown or deleted: send the install number from usage.json in the Pitrig folder of your user data.
  • Ask for your contact messages, and the answers to them, to be deleted from the mailbox.
  • Object to any of this processing, or ask a question, by email.
  • Complain to the Polish data protection authority, UODO (uodo.gov.pl), or the one where you live.

Website records hold no name or network address, so they cannot be found for a person who asks.