Spielepause

Privacy Policy

Introduction

This privacy policy informs you about the types of personal data (hereafter also "data") we process, for what purposes and to what extent, within our online offering Spielepause. Spielepause is a free, non-commercial daily-puzzle site that runs entirely in your browser. There are no user accounts, no sign-up and no advertising; we process as little data as possible.

Last updated: 29 October 2026.

Controller

Christian Götze, Rathenaustr. 3, 16761 Hennigsdorf, Deutschland

E-mail: spielepause@post.christiangoetze.de

Phone: +49 33022015238

Imprint: https://spielepause.de/impressum

A data protection officer is not legally required (§ 38 BDSG).

Overview of processing

The following overview summarises the types of data processed and the purposes of their processing.

Types of data processed: meta/communication data (e.g. IP addresses — in full in the server log files, only briefly in memory in the audience measurement — access times, browser type); game usage data (counter values by game, game mode, result and number of guesses — with no identifier); competition data (first name or nickname and results, only if you take part in a competition); content data (only if you contact us by e-mail); image data (photographs of real places in which people may appear incidentally).

Categories of data subjects: users (visitors and players of this site); communication partners (people who write to us by e-mail); people appearing in photographs.

Purposes of processing: provision of the online offering and web hosting; IT security; audience measurement and game statistics; responding to enquiries.

Relevant legal bases

We process personal data on the basis of the General Data Protection Regulation (GDPR); additionally, national requirements in Germany apply, in particular the Federal Data Protection Act (BDSG) and the Telecommunications-Digital-Services Data Protection Act (TDDDG).

Legitimate interests (Art. 6 (1) (f) GDPR): processing is necessary to safeguard our legitimate interests, provided the interests or fundamental rights and freedoms of the data subject do not override them.

Pre-contractual enquiries (Art. 6 (1) (b) GDPR): when responding to contact enquiries.

Photographs in the game "Reiseigel"

The game "Reiseigel" shows photographs of real places. The photographs come from Wikimedia Commons under free licences (CC0, CC BY or CC BY-SA). We did not take them ourselves.

Some photographs may show people — passers-by in a street, visitors at a viewpoint. We select photographs so that no person is the subject of the picture; anyone shown is always incidental to the place itself. We do not use photographs in which individual people are recognisably the subject, nor photographs of religious ceremonies, processions, demonstrations or assemblies.

The legal basis is Art. 6 (1) (f) GDPR. Our legitimate interest is running a free puzzle game about real places; the photograph shows the place, not the person.

Information under Art. 14 GDPR: this data did not come from the people shown but from the publicly accessible media collection Wikimedia Commons (commons.wikimedia.org). We know neither the identities nor the contact details of the people shown. Informing them individually would therefore be impossible within the meaning of Art. 14 (5) (b) GDPR, so we make the information publicly available here instead.

Retention: the photographs remain part of the game for as long as the game is offered. They are not analysed, not combined with other data, and no facial recognition takes place.

Objection and erasure: if you appear in one of the photographs and do not want it shown here, write to us — we will remove it without question and without you having to give a reason. Photo credits with author, licence and source are at https://spielepause.de/bildnachweise.

Security measures

In accordance with legal requirements, we take appropriate technical and organisational measures to ensure a level of protection appropriate to the risk.

TLS encryption (https): to protect the data transmitted via our online offering we use TLS encryption, recognisable by the "https://" prefix in your browser's address bar.

Automated decision-making: there is no automated decision-making within the meaning of Art. 22 GDPR. The automatic blocks set by our attack detection (see "Provision of the online offering and web hosting") are used for IT security and only affect whether our servers can be reached from a blocked address. If you email us about a block as described there, we will review it by hand and lift it where appropriate.

Transfer to recipients and processors

To operate this online offering we use a hosting provider that acts for us under a data processing agreement (Art. 28 GDPR; see below). In addition, as part of our IT security measures, IP addresses and other details of detected attacks and of addresses blocked by hand are transmitted to CrowdSec SAS in France (see "Provision of the online offering and web hosting"). E-mails to our contact address arrive in a mailbox operated by Proton AG in Geneva, Switzerland; Switzerland is covered by an adequacy decision of the EU Commission (Art. 45 GDPR). No further transfer to third countries outside the EEA takes place.

Provision of the online offering and web hosting

We operate this online offering on a server in a data centre in Falkenstein, Germany.

Collection of access data and log files: when our online offering is accessed, access data is recorded server-side in server log files (incl. the full IP address, date and time of the request, URL accessed, HTTP method, amount of data transferred, status message, browser type and version, referrer URL). This serves secure, fault-free operation, IT security and error analysis. The log files are stored exclusively on our own server in Germany and — apart from the reports to CrowdSec SAS described below — are not transmitted to any external provider. The access log is rotated daily and deleted automatically; an entry is gone after 31 days at the latest. Further application log output is deleted from the logging system after 30 days. On the server itself it is, as a rule, deleted automatically the next time the server restarts or after several updates of the site; there is no fixed period for this. If a specific security incident is being investigated, the entries concerned may be kept until it is resolved.

Defence against attacks: for this, security software for attack detection runs on this site's server. It automatically analyses the server's access log and recognises patterns in it such as repeated intrusion or abuse attempts. It also checks requests to this site for the characteristics of known attacks; the check covers the requested address, the headers and content sent along — this includes, for example, the first name you give for a competition. This check runs automatically and in memory only; requests that raise no alert are neither stored nor passed to third parties in the process.

Requests showing the characteristics of an attack may be rejected immediately. If an attack is detected, whether in the access log or in this check, the attack detection blocks the IP address it originates from, or a suspicious address range, as a rule for four days at most; during a block, this site cannot be reached from the address concerned. For each detected attack, the attack detection stores a record (incident) with the IP address, the time, the type of attack and details from the triggering requests (such as the requested address and the browser identification). Stored incidents are deleted after seven days at the latest; if a block belonging to an incident is still running, the incident may be kept until that block expires. Messages about detected attacks, with the IP address, also appear in the log output of the attack detection. It is deleted from the logging system after 30 days. On the server itself it is, as a rule, deleted automatically the next time the server restarts or after several updates of the software; there is no fixed period for this. Individual addresses or address ranges from which abuse originated may additionally be blocked by hand for a longer period or permanently; such a block lasts at most until it expires or until it is lifted. If you consider a block unjustified, please write to the email address given in the section "Controller".

For detected attacks, the attack detection reports in particular the attacker's IP address, the type of attack detected and the time to CrowdSec SAS (France, EU), together with details from the triggering requests such as the requested address and the browser identification; there, such reports feed into a shared list of attacker addresses for collective abuse prevention. Addresses and address ranges that are blocked by hand (see above) are reported as well, with the time and the details of the block, even if the occasion was not an attack. No other IP addresses are reported; normal use of this site is not reported. In addition, the attack detection regularly receives blocklists of IP addresses from CrowdSec SAS; requests from addresses on them are blocked as well, for as long as the address is on one of the lists and, as a rule, for up to seven days after that. Legal basis: legitimate interests (Art. 6 (1) (f) GDPR — IT security). Privacy policy of CrowdSec SAS: https://www.crowdsec.net/privacy-policy.

DNS resolution: the DNS zones of our domain are hosted by Hetzner Online GmbH, Industriestr. 25, 91710 Gunzenhausen, Germany; the authoritative name servers are operated in Germany. No transfer to third countries outside the EEA takes place in this context. Legal basis: legitimate interest in the reliable availability of our online offering (Art. 6 (1) (f) GDPR).

Hosting provider used: Hetzner Online GmbH, Industriestr. 25, 91710 Gunzenhausen, Germany (servers in Falkenstein/Germany); privacy policy: https://www.hetzner.com/de/rechtliches/datenschutz.

Backups: every night a backup of the server's data is stored with our hosting provider in Germany. It includes the daily totals of the audience measurement (without IP addresses and without daily identifiers; see "Audience measurement with tally"), the competition data (see "Competitions (Wettkampf)") and the database of the attack detection (with the stored incidents, the IP addresses of detected attackers, the addresses blocked by hand and the addresses from the blocklists received from CrowdSec SAS). Each backup is kept for 14 days and then deleted automatically; it is used only to restore the service after a fault. A record already deleted from the live database may therefore remain in a backup for up to 14 more days, and for the audience measurement up to 16 days, because it makes a copy of its database for the backup every night and keeps the last three. The server access log and the application log output are not backed up.

Audience measurement with tally

To see how many people visit and which pages are read, this site uses tally, analytics software written by the site's operator and run on self-operated infrastructure, on a server of Hetzner Online GmbH in Germany (address t.cgoetze.de). No third-party service is involved, and the audience-measurement data is not passed on to any third party. Hetzner provides the server as a processor (see "Provision of the online offering and web hosting").

When you open a page, your browser loads a small script from t.cgoetze.de and then sends a short report there, plus one more for every page change within this site. The report contains only: the short name of this site; the path of the page you opened, without parameters or anchor (for example "/impressum", never the part after "?" or "#"); the address of the site you came from, without any path (for example "https://www.google.com"), and only as far as your browser discloses it; and, only if the address you opened contains them, the campaign values "utm_source" and "utm_campaign". The script sets no cookies, stores nothing in your browser's storage, reads nothing from it and queries no features of your device, such as screen size, fonts or extensions.

As with every request, your IP address and your browser identification (user agent) reach the server along with the report. The audience measurement uses the IP address in memory only, and only for three purposes, described below: the country, the daily identifier and protection against overload. The audience measurement itself never writes the IP address, the browser identification or the daily identifier to disk and never logs them; for the server's access log, see below.

The country is determined from the IP address with a country database ("IP to Country Lite" by DB-IP) that is kept as a file on the same server. No request goes to DB-IP or any other third party in the process, and only the country is derived, neither region nor town.

From the IP address, the browser identification and the site's short name, the audience measurement forms a daily identifier. This identifier is a keyed hash, built with a secret random value; the random value exists only in memory and is replaced by a new one every night when the day changes (midnight German time) and whenever the service restarts. Through this identifier, a visit therefore cannot be linked to a visit on another day, and without the random value, which never leaves memory, the identifier does not lead back to your IP address. The daily identifier serves only to avoid counting you twice within a day, whether for the whole site or for a single page, to tell which page views belong to the same visit (a visit ends after 30 minutes without a page view), and to show the number of visitors in the last five minutes, a number that is never stored. For this, the audience measurement holds in memory the daily identifier, the time of your last page view, the number of page views in the current visit and, for each page you open, a further keyed hash of the daily identifier and the page; all of it is discarded together with the random value.

To protect the service against overload, it accepts only a limited number of reports per internet connection within a given period. This limit, too, works in memory only and only with a keyed hash of the IP address (for IPv6 addresses, of their front part, which identifies the connection), formed with the same random value and discarded with it, never with the address itself.

The browser identification is reduced to coarse classes (browser family such as Firefox, operating-system family such as Android, and device type: computer, smartphone or tablet) and checked for whether a program rather than a person is making the request; reports from such programs are discarded. Of the previous page's address only the domain name remains (for example "google.com"); if it is this site itself, it is discarded entirely.

Only daily totals are stored: for the whole site, the number of page views, visitors, visits and visits with a single page, plus breakdowns by page, entry page, referring domain, kind of origin (direct, search engine, social network, other website, campaign), campaign value, country, browser family, operating-system family and device type. Parts of a page address that look like an automatically generated identifier (such as a long string of digits and letters) are replaced by a placeholder before counting. There are no individual records, no row per visitor, no IP addresses, no daily identifiers and no times of day; the smallest unit is the calendar day. Someone who comes on two days therefore counts as two visitors: the audience measurement forms no identifier that lasts beyond the day. On days with very few visits, however, a daily total can describe a single visit; someone who knows that you were here on that day could, for example, read from it which pages you opened.

The identifier of a competition in the address ("/wettkampf/…") is replaced by a placeholder before counting.

If your browser sends "Do Not Track" or "Global Privacy Control", the script sends no report (it is still loaded; see the access log below); should a report with one of these signals arrive anyway, the server discards it. In local development and on hosts other than the production addresses, the script is not loaded.

Not every browser offers these signals. You can also switch the measurement off by blocking the address t.cgoetze.de, for example with a content or ad blocker; the site keeps working unchanged.

Right to object: you may object to the audience measurement at any time under Art. 21(1) GDPR, informally, by email or by post to the contact details given in the imprint. Because the audience measurement forms no identifier that lasts beyond the day, an objection cannot be recorded for your browser; the measurement is reliably switched off by the signals mentioned above or by blocking t.cgoetze.de. The daily totals already stored contain no identifier, so it cannot be determined which figures stem from your visits (Art. 11 GDPR).

Loading the script and each report are ordinary requests to this server and therefore appear in the server's access log like any other request, with IP address, browser identification and time (see "Provision of the online offering and web hosting"). In these entries the referring page is only this site's address, without a path, and the path of the page you opened does not appear.

Storage period: the audience measurement uses the IP address and the browser identification only while it processes a report. The daily identifier, the hashes and the time of the last page view are discarded when the day changes, a few seconds after midnight at the latest. The breakdowns (by page, entry page, referring domain, kind of origin, campaign value, country, browser family, operating-system family and device type) are deleted after 25 months: every day, all entries for a day more than 25 months back are removed. The daily totals for the whole site (page views, visitors, visits and visits with a single page) are kept for as long as the site is operated, so that its use can be compared over the years; if the site is discontinued, they are deleted too. These totals contain nothing about pages, origin, country or device. The entries in the server's access log (IP address, browser identification, time, this site's address) are deleted after 31 days at the latest; only entries needed to investigate a specific security incident may be kept longer, until it is resolved.

Legal basis: Art. 6(1)(f) GDPR (legitimate interest in privacy-friendly statistics on the use of the site and in protecting this measurement against overload and distortion; for the access log, the legitimate interest in secure and trouble-free operation, see "Provision of the online offering and web hosting"). No consent under § 25(1) TDDDG is asked for, because it is not considered necessary here: the script stores nothing on your device. It reads only what your browser transmits with the page request anyway (the address requested, the previous page and, where set, the "Do Not Track" and "Global Privacy Control" signals); apart from that, it checks whether the page is being preloaded in the background, so that it is counted once you actually open it. That information does not leave your device.

Until 21 October 2026, Matomo was used for audience measurement. From the data recorded with it, daily totals and breakdowns of the kind described above, covering up to twelve months before the switch, were transferred to tally (no IP addresses, no visitor identifiers and no individual visits). Since then, the storage periods above apply to the transferred figures. This departs from the earlier statement that after twelve months only monthly and yearly figures of the daily reports would have been kept; the figures were transferred so that the statistics stay comparable across the switch. The Matomo data itself was deleted on 30 October 2026 at the latest: the individual visits with truncated IP address, daily changing visitor identifier, time, pages viewed with their address and title, approximate location, browser and device type, language setting, referring domain and campaign values; the recorded clicks on outbound links and downloads; the interaction events from a fixed list; and the reports derived from them. Backup copies that still contain it will be deleted by 14 November 2026 at the latest. Older versions of this site running in a tab that is still open may keep trying to send reports to the former Matomo address (matomo.cgoetze.de); that address has not existed since 24 October 2026, so such reports do not reach the server and are not recorded.

Local storage and game statistics

Local storage in the browser (localStorage): your game progress, statistics and settings (e.g. light/dark mode) are stored solely in your browser ("localStorage") and never transmitted to us — the only exceptions being your results in a competition you joined, together with the participant identifier that belongs to them (see "Competitions (Wettkampf)"), and the short report sent when a game ends (see below). This storage is strictly necessary under § 25 (2) no. 2 TDDDG to provide the game you requested and therefore takes place without consent. You can delete this data at any time by clearing this site's data in your browser.

Game statistics (separate from the audience measurement): when a game ends, the site sends a short report to our server. It contains only the game, the game mode (daily puzzle, practice or competition), whether it was won or lost, and the number of guesses — no identifier and no cookies. The server then only increases the matching counters by one; it does not store the report itself. In the same way it counts how often competitions are created (ordinary competitions and specials separately), joined and results submitted, how often a question in "Märchenmietze" (per tale), a case in "CyberCapybara" or a product in "PfennigPanda" (per game) is reported, and how often a server-side error occurs in the process. The counters serve solely the aggregated analysis of game usage and the monitoring of operations.

Your browser's report is an ordinary request to our server and therefore appears in the server's access log like any other request, with IP address and time (see "Provision of the online offering and web hosting"). Our monitoring system reads the counter values at short intervals and keeps them with the time of each reading; they are deleted automatically after 17 days at the latest. They are not backed up. Because this shows fairly precisely when a counter rose, a single event could, together with the access log, be matched to a request and thus to an IP address. Legal basis: legitimate interests (Art. 6 (1) (f) GDPR).

Competitions (Wettkampf)

If you start or join a "Wettkampf" (an optional competition over one to six games that runs for seven days from the day it is started), we process the first name you enter together with your game results for those games. This data is stored on our own server in Germany so that the shared leaderboard can be shown to the other participants who have the competition link. When you join, the server also assigns you a random participant identifier, which it stores together with this data. Your browser keeps it in localStorage and sends it along with every result and every throw in "Rutschrobbe", so that the server can match results and throws to your participation; it does not appear on the leaderboard. We do not ask for or store your surname, e-mail address or any other contact data, and we create no user profiles.

Visibility: the first name and results you submit are visible to everyone who has the link to that competition. Please therefore use only a first name or nickname and no further personal data.

Storage period: competition data is ephemeral. A competition runs for seven days, counting the day it is started. Its data is deleted automatically from the live database at the latest about one day after it ends, i.e. about eight days after it was started (technically via an expiry set on each entry). It can remain in the nightly backups for up to 14 more days and is then deleted there too; the backups are used only to restore the service after a fault (see "Provision of the online offering and web hosting").

Abuse protection: so that the competition function cannot be misused automatically, the server counts requests per IP address — when a competition is created, joined, viewed or a result is submitted, on every throw in "Rutschrobbe", when a question in "Märchenmietze" is reported as wrong, when a case in "CyberCapybara" is reported, and when a product in "PfennigPanda" is reported (the report itself contains only the identifier of the question, case or product). For this, your IP address (for some requests together with the competition code) is stored as a counter key for at most one hour and then deleted automatically; like all competition data it can remain in a nightly backup for up to 14 days. Legal basis: legitimate interest in the security and availability of the offering (Art. 6 (1) (f) GDPR).

Legal bases: the processing is carried out to provide the competition function you actively requested and in our legitimate interest in offering this social feature (Art. 6 (1) (b) and (f) GDPR). Participation is entirely voluntary; if you do not start or join a competition, no first name and no results are processed.

Contact

If you contact us by e-mail, we process the information you provide to the extent necessary to respond to your enquiry. The information is deleted as soon as it is no longer required for the purpose, generally no later than 6 months after the enquiry has been dealt with, unless statutory retention obligations apply. Legal bases: pre-contractual enquiries (Art. 6 (1) (b) GDPR) and legitimate interest in answering enquiries (Art. 6 (1) (f) GDPR). No contact form or external e-mail dispatch service is used.

Your e-mail arrives in a mailbox operated by Proton AG, Geneva, Switzerland. Switzerland is covered by an adequacy decision of the EU Commission (Art. 45 GDPR).

Cookies and similar technologies

Spielepause uses no cookies. Local browser storage (localStorage) is used for game progress, statistics, your settings and your participation in competitions; which of this is transmitted to us is described in "Local storage and game statistics". The audience measurement with tally uses no cookies (see "Audience measurement with tally"). No tracking in the sense of cross-device recognition or profiling takes place.

Deletion of data

The data we process is deleted in accordance with statutory requirements as soon as the permissions required for processing cease to apply (e.g. when the purpose of processing no longer applies). If data is not deleted because it is required for other legally permissible purposes, its processing is restricted to those purposes.

Changes and updates to this privacy policy

Please review the content of our privacy policy regularly. We adapt the privacy policy as soon as changes to the data processing we carry out make this necessary.

Rights of data subjects

Right to object (Art. 21 GDPR): you have the right to object at any time, on grounds relating to your particular situation, to the processing of personal data concerning you that is carried out on the basis of Art. 6 (1) (f) GDPR.

Right of access (Art. 15 GDPR): you have the right to obtain confirmation as to whether data concerning you is processed and to access that data.

Right to rectification (Art. 16 GDPR): you have the right to request the rectification or completion of data concerning you.

Right to erasure (Art. 17 GDPR) and to restriction of processing (Art. 18 GDPR).

Right to data portability (Art. 20 GDPR).

Complaint to a supervisory authority (Art. 77 GDPR): the authority responsible for us is the Landesbeauftragte für den Datenschutz und für das Recht auf Akteneinsicht Brandenburg, Stahnsdorfer Damm 77, 14532 Kleinmachnow; e-mail: poststelle@lda.brandenburg.de.

Definitions

Personal data: any information relating to an identified or identifiable natural person.

Controller: the natural or legal person that alone or jointly with others determines the purposes and means of processing personal data.

Processing: any operation involving personal data, whether collecting, analysing, storing, transmitting or deleting it.

Processor: a person that processes personal data on behalf of the controller (e.g. a hosting provider).

← Back to the home page