Privacy policy

Controller

The operator named in the imprint is the controller for this website. Use the contact address there for any data protection request.

[email protected]

Visiting the site

Our hosting infrastructure records technical request data such as IP address, time, requested address, referrer and browser identification. This is needed to deliver pages and to detect abuse. Legal basis: Art. 6 (1) (f) GDPR, our legitimate interest in a secure, functioning service. These records are kept only for a short operational period.

Signing in with Discord

Sign-in is optional and only needed to manage listings. If you use it, Discord sends us your Discord account identifier, display name, email address and avatar address. Access and refresh tokens are stored encrypted. We never post on your behalf and request no further Discord permissions. Legal basis: Art. 6 (1) (b) GDPR.

Session cookie

After sign-in we set one strictly necessary cookie holding a session token, and store that session's IP address, browser identification and expiry so it can be listed and revoked. Google Analytics may set analytics cookies after you consent.

Listing content

Text and addresses you enter for an organisation, community or server are stored as your private draft. Once a listing is approved it becomes publicly visible, including its name, description, tags, region, language and connection address. Do not enter personal data you do not want published.

Ownership verification

To verify that you control a server, we store a hashed one-time token and, at your request, make a single outbound request to exactly the address you entered. We record the time, result and address of that attempt. No other connection to your server is made and no gameplay data is collected.

ServerRoam Connect

When enabled, our worker retrieves aggregate player counts from the public Cfx listing for the configured join code. Cfx receives that code and the worker’s network address, not your browser address through this feature. Counts and retrieval times are public: individual observations are retained for 30 days, hourly aggregates for up to 90 days. Optional txBridge connections send signed status and restart events. We retain only the selected status fields, event identifiers and content digests; no player identities, resource inventories or administrative payloads are stored. Event identifiers and digests remain for the lifetime of the connection to prevent duplicate processing. Connection secrets are encrypted. Changing the source hides its previous history until it expires; replacing the bridge removes its old receipts, and revoking it clears the secret.

Moderation record

Approval, rejection and suspension decisions are recorded with the deciding account, the time and the stated reason. This record keeps moderation accountable and reviewable. Legal basis: Art. 6 (1) (f) GDPR.

Reviews, invitations and developer access

Reviews store your rating, text, display name and moderation status; edits require another moderation decision. Reports record the subject, reason and decision. Organization owners can invite a verified email address and manage membership roles. Invitation and API credentials are stored as hashes and their plaintext is displayed only once. API keys grant read access to published catalogue data and can be revoked. A shared per-account request budget protects the service. For ownership disputes we store the endpoint, your chosen destination server draft, your written statement and the moderation decision. Only you and independent moderators see your claim. Do not enter passwords, tokens or private documents. Decisions can transfer endpoints, remove previous proofs and Connect access, and suspend the former community. Decided claims are deleted after 90 days; the transfer remains documented in the moderation audit. Your export includes your claims. Account deletion removes your claim statements and account association. Affected organizations can see the transfer decision in the moderation audit.

Unclaimed listings and listing claims

Moderators may add unclaimed listings using only public information about publicly advertised servers: community and server name, game, address, region, language, tags, a short description and the source page. These listings contain no personal data about players, are labelled as unclaimed and are not indexed by search engines. If you claim a listing, we store the listing, the receiving organization, your written statement, a claim code and the moderation decision. Only you and independent moderators see your claim; moderators also see your display name. Do not enter passwords, tokens or private documents. Decided claims are deleted after 90 days; an accepted transfer remains documented in the moderation audit. Your export includes your claims, and account deletion removes them.

Boost payments

When you choose a paid boost, Stripe hosts checkout and processes your payment details. We send an internal order reference, price and return address, not your game-server credentials. We store the purchasing account reference, organisation, server, price, currency, duration, payment references and status. Signed notifications and reconciliation control the advertising entitlement. Test payments never create public advertisements. Closed local order records and notification identifiers are removed 90 days after the order end or creation date; these records are not a statutory accounting archive. Account deletion removes the account link while the organisation’s order remains until retention expires.

For live purchases, Stripe also collects the billing name and address, an optional VAT ID and the email address for the invoice, calculates VAT and keeps invoices and payment records for the statutory retention periods under its own privacy policy (stripe.com/privacy).

Visitor reports

When enabled, we count profile views and join actions in daily aggregates for 90 UTC calendar days. We store the listing, day, action and a broad source category, not referrer URLs, IP addresses, browser details, cookies or persistent visitor identifiers in this reporting system. Signed page tickets expire after 30 minutes; hashed replay receipts expire within 25 hours and are removed by hourly maintenance. Reports are available to the listing’s organisation. Actions do not prove a game connection. Hosting access logs are handled separately as described above.

Google Analytics

We load Google Analytics 4 (measurement ID G-G314YVFZPH) only with your voluntary consent. Google then receives technical request data such as your IP address, browser details and pages viewed. Analytics may set cookies such as _ga. Our manually sent page views exclude URL query parameters and private account or administration pages. Google advertising signals are disabled. We use this to understand and improve the website. Legal basis: Art. 6 (1) (a) GDPR; non-essential cookie access additionally requires consent under Section 25 (1) TDDDG. You can withdraw consent for the future at any time through Analytics settings in the footer. See Google’s privacy policy for its processing.

Umami audience measurement

We use self-hosted Umami to count known public page paths. Pages with query parameters or URL fragments, private account pages and unverified dynamic details are excluded. The measurement payload contains only the website ID, fixed hostname, public path, fixed title and an empty referrer; no form contents or account identifiers. Browser Do Not Track, Global Privacy Control and the Umami visitor opt-out are respected before loading and sending. The tracker and collection endpoint are served through rpcrate.com to our Umami instance on OVH. The script request has no HTTP referrer; collection can send only the website origin under the existing referrer policy. Technical request data is processed to produce aggregate usage statistics; no tracking cookies or session recordings are enabled.

Vote rewards

Optional vote rewards store a claim linked to the vote, account and server, hashed claim code, creation/expiry times and redemption/acknowledgement times for up to 90 days. Codes expire after seven days. On redemption, the server supplies a server-salted recipient hash; no player name or Discord identity is sent to the integration. It receives only the stable claim event ID, state and expiry. Reward keys are stored hashed and stop working after revocation or loss of the issuer’s owner/admin authority. Account deletion removes claims and keys issued by that account. The game operator controls its own reward processing.

Votes and saved servers

If you vote for a server we store your account identifier, the server, the time, and a shortened, salted hash of your network address, so that one vote per account per server per 24 hours can be enforced. The hash covers a whole network rather than a single address, cannot be reversed back to one, and is cleared after 30 days; the vote itself is kept only as a number and is never published with your name. A saved server is visible to you alone and is counted nowhere. Legal basis: Art. 6 (1) (f) GDPR, our legitimate interest in a directory that automated voting cannot distort.

Abuse protection on the vote control

Where it is configured, the vote control and the e-mail sign-in form load Cloudflare Turnstile from challenges.cloudflare.com. Cloudflare then receives your IP address and technical browser data in order to tell a person from a script, and returns only a pass or a fail to us. It is loaded on those two controls alone, never on the rest of the site, and it sets no advertising or analytics cookie. Legal basis: Art. 6 (1) (f) GDPR.

What we do not do

No data sales or automated decisions with legal effects. The optional visitor reports described above use no cookies or persistent visitor identifiers. Paid placements are labelled as advertisements. Third-party code is loaded for the described vote abuse protection; a purchase opens Stripe-hosted Checkout. Google Analytics loads only after your consent.

Recipients

Hosting and Cloudflare process delivery data. Cloudflare R2 stores uploaded images in private quarantine and serves approved images publicly. Cloudflare Turnstile checks voting and e-mail sign-in challenges. Discord receives data when you sign in. Public profile content, approved reviews and author display names are visible to visitors and through the public catalogue API. With consent, Google receives website-use data as described in the Google Analytics section.

Retention and deletion

Account settings provide a personal-data export and deletion after a recent sign-in. Organization owners must transfer ownership first; moderators and recorded verification actors contact the operator for deletion review. Deletion removes sessions, linked provider credentials, favorites, votes and authored reviews. Audit references remain for accountability. Rejected review bodies and decided reports are removed after 90 days. Invitation codes expire after seven days and old invitation records are removed after another 90 days. Deleted media is removed by the worker with retries; public caches can retain copies for up to 60 seconds after removal.

Your rights

You have the right to information, correction, deletion, restriction of processing, data portability and objection under Art. 15 to 21 GDPR. Write to the contact address in the imprint.

Supervisory authority

You may lodge a complaint with a data protection supervisory authority. The authority responsible for the operator is the State Commissioner for Data Protection and Freedom of Information of Baden-Württemberg.