DayzHUBConsole
Rechtliche Hinweise

Datenverarbeitung

Datenschutz, Datenverarbeitung, Aufbewahrung, Sicherheit und Cookies der DayzHUB Console.

Entwurf, Prüfung ausstehend Entwurf vom 2026-10-02

Entwurf, Prüfung ausstehend. Dieser Text ist ein englischer Entwurf. Er wurde noch nicht geprüft, kann sich ändern und ist keine Rechtsberatung. Der Text dieser Seite ist vorerst nur auf Englisch verfügbar.

Roles

For the data of the players on a community's game servers, the community owner decides why and how it is used, and the Console processes it on the owner's behalf. For the Console accounts and payments, DayzHUB decides.

This page is a short summary of how that processing works. It is a draft pending review and not a signed agreement.

What is processed

  • Categories of data: Steam IDs, player names, join and leave times, bans and notes, in-game logs (chat, kills, deaths, placements and similar), account sign-in details, plan and payment references.
  • Purpose: showing and moderating the owner's servers and running the Console features they switched on.
  • No special categories of data are intended to be stored. Free-text fields (notes, chat) are written by people; owners should not put sensitive information into them.

Providers that take part

The providers below process data for the Console. The list will be kept up to date here.

  • Discord: sign-in with Discord, and posts to the Discord servers and channels the owner connects (webhooks, the Hub bot link).
  • Steam (Valve): sign-in with Steam (OpenID) and public Steam profile information used for checks the owner switches on.
  • PayPal: payment processing for paid plans. PayPal handles card and account details; the Console only receives the result.
  • Hosting provider: the servers that run the Console and its database, and the backups of that database.
  • E-mail delivery provider: sends sign-up, password, billing and downtime e-mails.
  • Cloudflare: network protection and delivery in front of the website.
  • Plausible: privacy-friendly site statistics, only if you accept the optional cookie setting (see Cookies).

Security of processing

See Security. Secrets are encrypted at rest, traffic is encrypted in transit, staff access follows roles, and the database is backed up regularly.

Deletion and return

When an owner erases a server or an account, the data attached to it is deleted from the live database. Backups age out on their own schedule. History is also deleted automatically after the period of the owner's plan, see Data retention.

Sub-processors and changes

New providers are added to this list before they start handling data. Questions: [email protected].

Betrieben von DayzHUB · Kontakt: [email protected] · Zurück zur Console