ReMatter

Privacy Notice

Updated

This notice covers the ReMatter website at rematter.asakuro.net and the ReMatter app’s requests for access, downloads and updates, as well as optional app analytics.

Who is responsible for your data?

Tom Scheumann
c/o Online-Impressum 1272
Europaring 90
53757 Sankt Augustin
Germany

For privacy questions and requests, email texploderyolo@gmail.com, call +49 1577 3602526, or write to the address above. Legal notice (Impressum)

Website, downloads and updates

When your browser or the ReMatter app connects, the server processes the IP address, the requested resource and technical request information needed to return the page or file over HTTPS. This applies to app and module downloads and requests for update manifests or the module catalog. You can turn automatic app update checks on or off in ReMatter Settings.

These technical details are needed to respond to requests. Without them, the server cannot deliver the requested resource. The legal basis is Article 6(1)(f) of the General Data Protection Regulation (GDPR). Our legitimate interests are delivering the service, maintaining its availability and protecting it from abuse.

App access and moderation

Starting with ReMatter 1.4.0, the official Windows app requires an internet connection at startup and checks its access status before loading modules. It checks again every five minutes while open and when you request a connected module download. If it cannot verify access for 15 minutes after the last successful check, it locks until it can check again. The app creates a random access key in your Windows profile’s local app data and sends it over HTTPS to verify access for this copy of ReMatter. The server derives a support reference from the key.

The service keeps one entry per support reference with the UTC calendar date of the most recent successful online check and any display name you choose to share. Each newer date replaces the previous one. A check that returns an active restriction can also update this date. Only authorized administrators can see this list and use it to find an installation for support or moderation. The list shows the last 30 UTC calendar days. Older entries are removed during hourly cleanup. The list starts when the feature is enabled and does not import past activity. It is separate from optional app analytics.

The service keeps no copy of the key and no log of individual checks. It does not collect hardware identifiers, Windows account details, running processes or network activity for these checks. Your connection’s IP address is used to deliver the service, as described above. The installation list and moderation records contain no IP addresses.

An administrator can review a credible report of harmful use of ReMatter modules and use the associated support reference to issue a warning or restrict access to the official app and connected module downloads. A report can come from someone who contacts us about a specific incident. A moderation record contains the support reference, the decision, the reason and any expiry date. The server applies the administrator’s decision when ReMatter checks access.

Moderation records have separate retention periods and can remain after the installation entry expires. Warnings expire after 30 days. Temporary restrictions expire after the stated period. Expired records are removed during hourly cleanup. Indefinite restrictions remain on record until an administrator lifts them. When an administrator clears a warning or lifts a restriction, the corresponding record is removed.

We process this information to verify app access, find relevant installations for support or moderation, deliver warnings and prevent harmful use of ReMatter modules. Our legitimate interests under Article 6(1)(f) GDPR are operating and protecting the service and enforcing access restrictions following human review. The app stores and reads the local key for its access check under section 25(2)(2) TDDDG.

To ask about a warning or request review of a restriction, use the contact details in the legal notice and include your support reference. Keep your access key private.

Optional ReMatter display name

In ReMatter, open Settings → Online access to choose and save a display name for this installation. We suggest using a nickname. You enter the name yourself. ReMatter does not read your Windows username for this feature. Only authorized ReMatter administrators can see the name in the installation list. The server also returns it to your app when it verifies access for this installation.

We process the name with your consent under Article 6(1)(a) GDPR so administrators can recognize your installation during support or moderation. You can change it or select Remove display name in Settings → Online access. You can also remove it from the access screen if a restriction locks the app. Removing the name withdraws your consent and deletes it from the installation entry. Withdrawal does not affect processing before you removed it. The name stays on the entry until you change or remove it or the entry expires under the 30 UTC calendar-day rule above. Your display name choice is separate from optional app analytics and does not affect access checks or moderation decisions.

Optional app analytics

App analytics are off unless you choose to enable them. With your consent, ReMatter sends a signal after a successful app launch or when you open the Processes or Network Monitor module. The signal contains only the event type. The server stores daily totals for the last 30 calendar days and removes older totals during hourly cleanup. The analytics data contains no access key, support reference, hardware identifier, raw IP address or information about your Windows account, files, processes or network activity. The service uses your IP address to handle the HTTPS request and does not include it in the stored counts. The service does not retain individual analytics events.

You can leave the Share optional usage statistics box unchecked when first offered, or turn it off at any time in ReMatter Settings. Turning it off withdraws your consent and stops future analytics requests. Existing aggregate counts cannot be linked to you. Your choice does not affect app access checks. The legal basis is your consent under Article 6(1)(a) GDPR. Withdrawal does not affect processing carried out before you withdrew consent.

Website analytics

We count GET requests for the ReMatter homepage, app installers and updates, and module DLL downloads. These counts show which resources are requested and whether downloads are delivered successfully. The server stores a filtered record with the request timestamp, the public resource path, the HTTP response status and the number of response bytes. These records exclude IP addresses, URL query parameters and request headers. The analytics use no cookies, browser storage, fingerprints or visitor identifiers.

The private dashboard shows aggregate activity for the last 30 calendar days in the Europe/Berlin time zone. The figures count requests and do not identify or count individual people. Access is restricted to authorized administrators. Requests for the dashboard, project backups, update manifests and the module catalog are excluded from analytics.

Analytics log files rotate daily or sooner if they reach the file size limit. Archived log files are configured to expire after 30 days. Older files can be removed sooner when the archive reaches its file count limit.

Our legitimate interest is understanding public usage and monitoring delivery of the site and downloads while collecting as little data as possible. The legal basis for any personal data processed in preparing these statistics is Article 6(1)(f) GDPR.

Protected areas and service providers

To use the admin area or download a private project backup, you must provide credentials. The server processes them over HTTPS to verify access. The legal basis is Article 6(1)(f) GDPR. Our legitimate interest is protecting the dashboard and backup files from unauthorized access.

Only the private admin area uses strictly necessary cookies. They keep an authorized administrator signed in and protect the login and password setup forms from forged requests. The cookies are restricted to the admin area and are separate from analytics. The sign-in session lasts up to eight hours. Signing out ends the session. The administrator sets their password during a one-time setup. The server stores a password hash, and the private project backup uses separate HTTP authentication. The necessary admin cookies are used under section 25(2)(2) TDDDG.

Hosting and network infrastructure providers process technical connection data as needed to deliver the service. Authorized operators may access the protected service as needed to maintain it. External sites, including the linked legal notice, handle visits under their own privacy notices.

Contacting us

If you contact us, we use your contact details and message to respond and handle your request. Google provides the email service for the address above. Google may process email data outside the European Economic Area. It describes the EU-U.S. Data Privacy Framework and standard contractual clauses in its data transfer information. We keep correspondence for as long as needed to handle the request and for any applicable legal retention period. The legal basis is Article 6(1)(f) GDPR for our legitimate interest in responding to inquiries, or Article 6(1)(c) GDPR where processing is necessary to comply with a legal obligation.

Your rights

Under the GDPR, you can request access to your personal data, correction, erasure or restriction of processing. You can also request data portability where the conditions for that right apply. We do not use this data for automated decisions that have legal or similarly significant effects on you.

Right to object. Under Article 21 GDPR, you can object to processing based on legitimate interests on grounds relating to your particular situation. Use the contact details above to exercise your rights.

You can lodge a complaint with a data protection supervisory authority, including the authority where you live or work, or where the alleged infringement occurred. North Rhine-Westphalia data protection authority