Privacy policy

1. Controller

Heinrich Janzen
Höhenweg 16, 49124 Georgsmarienhütte
Email: kontakt@rigmint.de
Phone: +49 163 5106212

2. Overview of processing

Rigmint processes personal data in particular in the following cases:

• Registration and login (email address and password)
• Storage of profile data, in-game IDs and privacy settings
• Use of the Squadfinder matching system
• Reports about content (report function for squad posts, themes and builds)
• Published builds, themes and calculator setups together with who created them, and for builds the indication of which account adopted a build
• Paired devices and measurement sessions of the Windows application, if you have consented there
• Price alerts by email and optionally by browser push
• Participation in giveaways including a separate consent to name publication
• Warnings, account suspensions and the admin log of moderation decisions
• Technically necessary cookies and entries in the browser's local storage

3. Hosting and infrastructure

This website is hosted by Vercel Inc., the database runs at Neon (Postgres hosting). Data processing agreements with both providers are in place. When you visit the site, these providers process technically necessary server log data (including IP address, time, requested page) to ensure operation. The legal basis is Art. 6(1)(f) GDPR (legitimate interest in secure and stable operation).

Vercel Inc. is based in the USA; this may involve a transfer of personal data to a third country. This transfer is based on the European Commission's Standard Contractual Clauses (Art. 46(2)(c) GDPR). For the database, an EU region is chosen so that stored user data remains within the EU.

4. Registration with email and password

For a user account we store your email address, optionally a display name of your choice, and your password exclusively in hashed form (method: scrypt with a random salt). The plaintext password itself is never stored. The login state is managed via an encrypted session cookie (JWT). The legal basis is Art. 6(1)(b) GDPR (performance of a contract to provide the user account).

5. In-game IDs and visibility

In-game IDs (e.g. Steam, Epic, Riot ID) are not shown publicly by default (isPublic: false). They become visible to another user only after a mutual squad request has been accepted by both sides. The legal basis is the user's consent or Art. 6(1)(b) GDPR.

6. Reports about content

When you report a squad post, we store the reported content ID, your user ID, the selected report reason, an optional short note of at most 300 characters and the time of the report, in order to prevent abuse and to meet the legal obligation to handle reports (Art. 16 Digital Services Act). The legal basis is Art. 6(1)(c) GDPR (legal obligation) in conjunction with (f) (legitimate interest in a platform free from abuse).

For reports about themes and builds we store no report reason, only the reported content ID, your user ID and the time. We do not ask for a reason there, because an additional free-text field would be another channel for user content. Exactly one report is possible per account and piece of content. The legal basis is, as above, Art. 6(1)(c) in conjunction with (f) GDPR.

6a. Price alert and browser push

When you set a price alert, we store your user ID, the product key, optionally a target price, and whether the notification should go by email and/or browser push. An alert email is sent only after you have clicked the confirmation link in the email. The legal basis for the alert itself is Art. 6(1)(b) GDPR (service requested by you); sending to your address is based on your consent under Art. 6(1)(a) GDPR, which you give with the confirmation link and can withdraw at any time with one click in the email.

For browser push we store the endpoint address supplied by the browser and the related keys, linked to your account if you are signed in. Delivery goes to your browser's push service (including Google, Mozilla, Microsoft or Apple). These services are partly located outside the EU; transferring the technical address is necessary for delivery. You can end the subscription in the browser settings or via the site; we remove invalid endpoints automatically.

6b. Giveaways

When you take part in a giveaway, we store your user ID, the time of participation and acceptance of the terms of participation. The separate consent to publish your display name if you win is stored separately (timestamp of consent and, where applicable, of withdrawal). Without this consent you still take part; if you win, only a ticket number is shown. The legal basis for participation is Art. 6(1)(b) GDPR, for name publication Art. 6(1)(a) GDPR. You can withdraw name publication on the giveaway page while the giveaway is running.

6c. Warnings, suspensions and admin log

When a post is removed, we store a warning with the removed text, the reason, an explanation to you and the time. This implements Art. 17 and Art. 20 of the Digital Services Act: without the text and the explanation there would be no path to contest. Three open warnings can lead to an account suspension; the suspension carries a reason and an end date. In addition, every moderation decision by an admin writes a line to the admin log (who, what, when). The log is currently not deleted automatically.

7. Cookies and local storage

Technically necessary cookies and storage entries:

• NEXT_LOCALE: your language choice. No personal reference, required for multilingual output.
• Login session cookies (JWT): keep you signed in. Legal basis Art. 6(1)(b) GDPR.
• battlehub-theme: chosen colour scheme, so the page does not briefly flash another theme after loading.

The browser's localStorage may also hold: confirmation of the privacy notice, the arrangement of the home page, local drafts and, if you set it, the entry plausible_ignore to disable reach measurement. These entries do not leave your computer by themselves; they only control what this site does on your device.

8. Reach measurement (Plausible Analytics)

We use Plausible Analytics for aggregated evaluation of page views. Plausible does not set its own cookie and, according to the provider, does not store IP addresses. When you visit, your browser loads the script from plausible.io; the script can read the entry plausible_ignore in your local storage if you have set it, and reports the requested address together with technical details (including referrer and screen width) to Plausible. Whether this is permissible without consent under section 25 TDDDG is not finally settled in law; we therefore treat the use cautiously and disclose it fully here. Further information: plausible.io/data-policy.

Withdraw or grant consent: under Article 7(3) GDPR withdrawing must be as easy as giving consent. You can do it right here, at any time, without an account.

8a. Live monitoring in the Windows application

The Rigmint application for Windows (still named BattleHub in older installations) can, at your express request, measure performance values of your computer: load of processor and graphics card, temperature and clock of the graphics card, occupied system and graphics memory, the process name of the game in the foreground and, where measurable, frames per second. For game recognition it also reads the locally installed Steam and Epic library as well as the names of running processes. Screen contents, keyboard or mouse input, files or browsing history are not collected.

Measurement takes place exclusively on your device. Without your separate consent, no measured value leaves your computer. The legal basis of the measurement itself is performance of the function you requested; for that purpose it is necessary within the meaning of section 25(2) no. 2 TDDDG.

Transmitting a completed measurement session to us is voluntary and happens only on the basis of your consent under Art. 6(1)(a) GDPR, which you give in the application with a separate switch. The purpose is improving FPS predictions: measured values from real computers are more reliable than calculation models. What is transmitted are the measured values named above, the duration of the session and your hardware, linked to your user account. There is no disclosure to third parties.

Retention: The detailed history of a session (the time-related number series) is cleared automatically no later than 90 days after the session. Start, end, duration and the process name of the game are also reset then, so that the row no longer shows when you played which program for how long. What remains are the hardware details and the averaged frame rates for the predictions, as well as the note in your history that the session existed.

Withdrawal and deletion:You can withdraw consent at any time with the same switch in the application; the lawfulness of processing carried out until then remains unaffected. You delete sessions already transmitted completely in your profile under “My measurements” with a button.

9. Retention period

Profile data is stored for as long as a user account exists. If you delete your account, it is deleted immediately and irrevocably, unless statutory retention obligations prevent this.

Reports about themes and builds as well as the indication of which account adopted a build are deleted automatically after 12 months. A daily job does this; the period is a single number in the source code that the job and this page both follow. What remains are only the counters, that is how often a piece of content was adopted or reported. They no longer relate to a person.

Reports about squad posts (see section 6) are deleted by the same job 12 months after they are handled. Open reports remain until a person has handled them: deleting an unhandled report after the deadline would mean closing it by lapse of time.

Exception for builds: if you delete your account, builds you published remain and are anonymised. Other users have adopted them, and their copies should not disappear. Your name is removed, but the title and note you entered remain publicly readable. If something there points to you, change or delete the build before you delete your account.

10. Minimum age

Rigmint is aimed at users aged 18 and over. Registration is only permitted with a truthful statement that you are at least 18 years old.

11. Your rights

You have the right of access, rectification, erasure, restriction of processing, data portability and objection under Art. 15-21 GDPR. Contact the address given above for this. You also have the right to lodge a complaint with a data protection supervisory authority, e.g. the State Commissioner for Data Protection of Lower Saxony (LfD Niedersachsen), which is competent for Lower Saxony.