Skip to content
GlobalGamer

Privacy policy

Controller and contact for privacy questions

The controller for the processing of personal data on this website is:

Global-Gamer
222 33-34 Moo 7 Pakhlok
83110 Phuket
Thailand

For privacy questions and requests for information: info@global-gamer.net

Hosting

This website and the application GG Hub are operated by Global-Gamer, location: Phuket 83110, Thailand.

What data GG Hub stores

GG Hub stores, as far as the respective feature is used:

  • Member: display name, internal identifier, preferred language and time zone, an image (avatar) if one is set.
  • Account (sign-in): email address, time of the confirmation of the email address, the password only as a hash (no plain text), a four-digit confirmation PIN only as a hash, an internal counter with which sessions can be invalidated.
  • Linked Discord account: the Discord identifier and the Discord name, if you sign in with Discord or link your account.
  • Administration log (audit log): which action a member performed when, on which object, and the IP address of the request (see "Logs and IP addresses").
  • Team presentation: public name, role title and short text per language, the link to the member and the consent (see "Team presentation and consent").
  • Read confirmation: which member confirmed which version of which rule set as read, and when (see "Read confirmation for rule changes").
  • Access statistics: per post, calendar day and language the number of views, without any link to a person (see "Access statistics").
  • Discord bot comparison: per linked member and Discord server the Discord identifier, the identifiers of the roles on the server, the last comparison and the decision to reject a role suggestion (see "Discord bot and role comparison").
  • Discord announcements: per message the delivery state and, for an announcement triggered by hand, the internal identifier of the triggering member; for an announced role assignment the identifiers of member, role and assigning member with the time (see "Discord bot and role comparison").

Cookies and local storage

The public website sets no cookies.

In the sign-in area (panel) the application sets the technically necessary cookies __Host-gghub_session (session; it expires after 120 minutes without activity) and __Host-XSRF-TOKEN (protection against forged requests). The cookie locale stores the chosen language.

The browser stores locally, without sending the data to the server: the chosen appearance (light or dark) under the key gghub.theme and, for editors only, unsaved draft texts (at most 30 days; signing out deletes them).

Logs and IP addresses

The web server logs requests, typically with IP address, time and requested address. Retention: 365 days.

If you use the search of the site, your search term is part of the requested address (/en/search?q=…) and therefore in the web server log. The application itself does not store search terms: not in the database and not in a cache. The result page is not cached, and search engines do not index it. Your browser may, however, keep the address including the search term in its history and in the address bar suggestions; you can delete that in the browser or avoid it with a private window.

To protect against overload the application counts requests per IP address (counter in Redis, time window 60 seconds).

When an account holding the right "skip the password confirmation" skips a confirmation prompt, the application writes the member ID, the route called and the IP address to the security log (log file); retention equals the rotation of the log files.

The audit log holds the IP address of the request. It is removed from the entry after 90 days. Entries of failed sign-ins are deleted after 30 days. The other entries (without IP address) are kept.

Error messages of the application (log files) can contain values from database queries, for example name, role title or short text of a person on the team page.

Contact, Discord and third parties

Whoever signs in with Discord is redirected to Discord; Discord Inc. receives data under Discord's terms. GG Hub passes no data on for advertising or analysis. The public site loads no external resources (no fonts, scripts, images or maps from third parties).

Team presentation and consent

The team page shows a person only with their own consent, which can be withdrawn at any time. The withdrawal is available in the member area under "Public presentation" (/settings/public-profile). From the next request of the page the person is no longer shown; a request that was already loaded can be up to 30 seconds old in the browser or a proxy cache.

When the consent is withdrawn, the application sets the entry back to a draft. The editors see that the entry is no longer public; the audit log shows authorised staff the entry, the time and the member who withdrew.

When an editor releases the link between an entry and a member, the log holds the entry, the time and the acting editor, but not which member was linked.

Read confirmation for rule changes

Signed-in members with a verified email address can confirm in the member area under "Confirm the rules" (/settings/rules) that they have read the points of the current version of a rule set. The proof refers to the points of the version; the title, the summary and the introduction of the rule set are not part of it, they are not kept per version. Stored are the member (internal identifier), the rule set, the version and the time of the confirmation; this table holds no IP address (the audit log stores it) and no browser details. A confirmation cannot be withdrawn. When a new version is published, the rule set is open again for the member; the earlier confirmation stays as proof, even if the member is anonymised later.

The editors see only the number of confirmations per version, no names. The audit log shows the event with the confirming member, the rule set, the version number and the time (for the IP address see "Logs and IP addresses"). Without signing in no confirmation is stored and no cookie is set.

Access statistics

GG Hub counts for the editors how often the page of a post (news, free page, rule set) was viewed. Only the number of views per post, calendar day and language of the page is stored. No cookie is set for this, and neither an IP address nor a browser string (user agent), a referring address (referrer) or an identifier of the visitor is stored. Visitors are not recognised: views are counted, not persons. The count itself means no permanent storage of personal data: the web server and PHP process the IP address and the browser string only briefly in memory, to answer the request and to count it or not; they do not reach Redis, the database or the application log.

Not counted are requests for the headers only (HEAD), prefetches by the browser, error pages, the preview of the editors, requests without a browser string and requests whose browser string points to a known search engine, preview or monitoring service or to a command line tool. A view also counts when the browser only asks whether the page is unchanged (answer 304, "not modified"). For this the application compares the browser string with a list only while the request runs, in memory; it does not store, log or pass it on (for the web server log see "Logs and IP addresses").

The counter lives in Redis first (only the number per page, day and language) and is moved into the database regularly. Only staff with the read right for the respective posts see the numbers, and only as numbers per post. The rows are deleted after 730 days; this period holds only while the deletion command hub:community:prune-stats runs regularly. If Redis writes its data to a persistence file (append-only file), that file holds the stream of the counting commands (page, day, language, without a time stamp) until the file is rewritten.

Discord bot and role comparison

The network includes a Discord server that a GG Hub bot looks after. The bot queries GG Hub over a secured interface and reports what it observes; it has no access to the database. For this it reads the members of the server and their roles and sets or removes roles that GG Hub derives from memberships, ranks and the confirmed email address.

Only for members who linked their Discord account with GG Hub, and who are neither anonymised nor merged, GG Hub stores per Discord server: the Discord identifier, whether the member is on the server, the identifiers (IDs) of the roles the member holds there, the time of joining (if known), the time of the bot's last report and the result of the last comparison (roles match, changed, failed, skipped). GG Hub does not store messages, online status, names or images from Discord. GG Hub discards server members without a link: their details are not stored, only their number is counted. The stored details are seen only by staff with the rights for the members page of the Discord area. If such a person rejects a role suggestion for a member, GG Hub stores the member, the mapping, the rejecting person and the time; the audit log then names the member concerned (internal identifier).

The recipient is Discord Inc.: the bot sets the roles at Discord, and Discord receives the identifier of the member and the role that is set or removed. The roles on the server are visible to its members according to the settings of the server. GG Hub transmits no email address and no name.

Retention: the stored details about the member (Discord identifier, roles, result of the comparison) stay as long as the link exists. When a member removes the link with Discord, GG Hub removes them with the next clean-up run at the latest, that is within a day (all servers, including the role suggestions rejected for this member); usually this happens when the link is removed. This does not include the record of which staff member rejected a role suggestion: it stays stored after that person's own link is removed, until the member concerned removes the link or the staff member is anonymised (this deletion on anonymisation is not built yet). The bot removes the roles on the Discord server at the next comparison, because GG Hub no longer names the member; this holds only while the comparison of the server runs in the mode "live", the bot is reachable and the emergency stop is not triggered, otherwise the roles stay until that is the case again or they are removed by hand. The history of the comparison runs (time, number of changes and errors, without a link to a person) is deleted 90 days after it was received. These periods apply only as long as the clean-up command hub:discord:prune-runs runs regularly (daily). For the comparison runs the audit log holds only numbers (changes, errors), no names; the section "Logs and IP addresses" applies to its retention.

Announcements: the bot also publishes news and rules of the website as messages in Discord channels. The content is public; the recipient is Discord Inc., and everyone who can see the channel can read it. GG Hub stores the delivery state of each message (channel, times, identifier of the message at Discord, error code), not the text; the text is read from the content of the website when it is sent. If a member triggers an announcement by hand, GG Hub stores that member's internal identifier with the announcement.

Role assignments: when a global role is assigned to a member with "Announce in Discord" ticked, the bot publishes the display name of the member and the name of the role ("NAME is now ROLE") in a channel of its own, without the member having to agree. The recipient is Discord Inc., and everyone who can see the channel can read it. The member is not mentioned; no email address and no internal identifier is sent. GG Hub stores permanently only identifiers (member, role, assigning member) and the time of the assignment, no name and no text; the text is read when it is sent. For a short time GG Hub keeps the answers of its interface for the bot, for a role announcement therefore also the display name and the role name, in the cache for 24 hours, so that the bot receives the same answer when it repeats a request after a transmission error; after that they are discarded; when a member is anonymised they cannot be deleted early, they expire by themselves. The identifiers stay when a member is anonymised (they name nobody); the message itself is at Discord and GG Hub does not delete it.

Rights of data subjects and right to lodge a complaint

Competent supervisory authority: Global-Gamer

Join GlobalGamer

Find a server, read the rules and meet the team.

Servers Rules Team