Privacy.

We measure only what helps us improve the civic initiative and Hockey Atlas. We do not sell data or use advertising pixels. We do not build personal or political profiles from reach analytics.

This notice covers arena.hockey, kreuzberg.arena.hockey, bbhl.arena.hockey and atlas.arena.hockey, and the Hockey Atlas city pages we operate on the city subdomains listed in Atlas, including berlin.arena.hockey.

Hockey Atlas for iOS and Android

Optional Atlas community on the website, iOS and Android

Optional private profile details

Hockey Atlas: delete your account and shared data

Current choice: No choice yet

Optional Atlas web analytics

After separate, revocable consent on each Atlas website, we count landing and map visits, selected catalogue venues, map loading outcomes, fixed filter categories, community opens, confirmed sign-ins, profile saves, game proposals, participation changes and app-test link clicks. The basis is consent under GDPR Article 6(1)(a) and TDDDG section 25(1). A click is not an installation; a sign-in is not necessarily a new account.

Records contain random event and tab-session identifiers, server time, Atlas hostname, language, a broad viewport-size class and source group, and optionally a public city/venue identifier and predefined action status. No account, team or game IDs, names, emails, passwords, search text, profile contents, private family data, invitation links, full URLs or GPS coordinates enter this analytics store. Sessions are not joined across hosts and are not a count of unique people.

Data is stored in separate analytics tables on our Hetzner server. The web infrastructure necessarily processes connection data; analytics does not store IP addresses. Abuse protection keeps only a short-lived salted IP hash in memory. Detailed events expire after 90 days and daily aggregates after 730 days; dedicated maintenance removes expired data every six hours plus a small scheduling delay. A deletion backlog raises an operational failure requiring follow-up. Backups have separate retention periods.

The choice is stored as arena_atlas_analytics_consent_v1 in the current host's local browser storage; the random session identifier stays in tab storage. “Analytics settings” in the Atlas footer changes the choice for that website only. Refusal stops future measurement and removes the local analytics-session identifier, but does not retroactively erase stored events. Campaign-site settings are separate. This first-party statistics feature is separate from the Google Analytics option described below; it does not use advertising and does not cover native apps.

Google Analytics for Hockey Atlas — only with consent

You can allow Google Analytics 4 independently of our own statistics. The provider is Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland. Its purpose is to understand map, community and app-test-link usage and improve Atlas. Google loads only after consent. The basis is GDPR Article 6(1)(a) and TDDDG section 25(1); refusing does not restrict Atlas.

Google receives predefined usage events, the selected catalogue city, language, a sanitised page address and technical connection/browser data. It uses its own pseudonymous cookie/session identifiers. We do not forward Atlas account, team, game, event or session IDs, names, emails, search text, profile contents or invitations. URL queries and fragments are excluded. Google signals, advertising personalisation, automatic form/search measurement and granular location/device collection are disabled. This is pseudonymous analytics, not anonymous counting.

Separate analytics cookies prefixed arena_atlas_ga4 are restricted to the current host, expire after at most 60 days and are not renewed on every visit. GA4 event and user retention is set to two months without activity-based extension; aggregated standard reports are not fully covered by that setting. Google may process data outside the EU, including in the US. Google states that applicable US transfers rely on the EU-US Data Privacy Framework, supplemented by the contractual Standard Contractual Clauses where applicable.

The separate Google choice is stored as arena_atlas_google_analytics_consent_v1 in this host's local browser storage. Use “Analytics settings” in the Atlas footer to refuse Google independently of our statistics or withdraw consent. This stops new measurement and removes the associated local cookies, but does not retroactively delete data already sent. Contact the controller identified above for access or deletion requests. This integration does not cover native apps or the campaign site.

Google: privacy and international transfers · Data processing terms

Controller

Sergey Terekhov · arena.hockey initiative · c/o Rechtsanwaltskanzlei Jablukov & Kollegen · Kurfürstendamm 132 A · 10711 Berlin · Deutschland · s.terekhov@me.com

Technical operation

The site runs on a server operated by Hetzner Online GmbH and is delivered through Cloudflare. Cloudflare processes technically necessary connection data for delivery, security and attack prevention. The origin server logs only Cloudflare connections; Nginx logs rotate daily. Up to 14 archive files are retained alongside the current file. Empty files are not rotated; no additional age-based deletion is configured. Archives may therefore remain for more than 14 days.

Recipients and international transfers

Hetzner processes data in Germany. Cloudflare acts as a processor and may handle data through its global infrastructure. Transfers outside the European Economic Area are subject to Cloudflare's contractual and statutory safeguards, in particular the EU Standard Contractual Clauses and, where applicable, the EU-US Data Privacy Framework.

Reach analytics with consent

Only after consent do we create random identifiers for this page view and browser session. We measure page views, broad acquisition channel, language and device class, scroll depth, visible sections, clicks, video and upload steps, and Web Vitals. We do not store names, email addresses, filenames, exact file sizes, full referrers or query strings, or IP addresses in the analytics database.

Outbound links

Visits to our own redirect routes for WhatsApp and evidence sources are counted as daily aggregates. No visitor or session identifier is stored. The destination provider processes the subsequent visit under its own terms.

Organisation links to the Wahlcheck

For individually issued organisation links, we count server-side per organisation-linked random code the request for the question overview (link_requested) and the deliberate continuation (wahlcheck_opened); we store neither an IP address nor a browser or session identifier, use the counts only internally for delivery follow-up under Art. 6(1)(f) GDPR, and delete them after 60 days; the values do not feed into the public assessment.

Hockey Atlas and local data

In the local area of “My Hockey”, the site stores the profiles, teams, game plans, attendance, visibility settings, local access rights and report drafts you create only in this browser's storage on your device. These local contents are not automatically uploaded to our servers; a local visibility setting does not publish anything. The optional community with a server account is a separate area, described below. You can delete individual entries or all local hockey data in Atlas. They are also removed when you clear this site's data in your browser. This does not delete a community account.

Atlas invitation and response links

When you prepare a local game invitation or response, Atlas encodes the game and schedule details, the chosen display name and, where applicable, the response status in the generated URL fragment, the part after the # character. A normal page request does not send this fragment to our web server. The data leaves your device only if you copy or share the link yourself, and it is read in the recipient's browser. A messenger or other service used to share it may process the complete link under its own rules. Atlas does not send these links automatically.

Map, OpenFreeMap and OpenStreetMap

The interactive map is rendered in your browser with MapLibre GL JS. To display it, your browser loads the map style, vector tiles, fonts and symbols directly from tiles.openfreemap.org, a service operated by Hyperknot Software Kft. The map data comes from OpenStreetMap and is provided using the OpenMapTiles schema. For technical delivery, OpenFreeMap receives in particular your IP address, the time, requested tile coordinates and zoom levels, and standard browser and connection data. Local profiles, teams, game plans and invitation contents from “My Hockey” are not included in these requests. OpenFreeMap's published privacy policy applies to this processing.

Watching videos

Thumbnails and the player are delivered by Cloudflare Stream. The player loads only after an explicit action. If analytics is allowed, we record starts, progress milestones, completion and technical errors by video, not by person.

Submitting videos

A submitted video is transferred directly to Cloudflare Stream. Cloudflare processes the file and technical metadata as our processor. Once technical processing is complete and valid consent is recorded, the video is currently published automatically on arena.hockey without prior editorial review. We may review, hide or delete published videos afterwards. We store a random Stream identifier plus the consent version and time, but no name, email address, filename, IP address or free-text message with the video.

Consent, rights and minors

Before choosing a file, the submitter must actively give explicit consent to automatic public publication after technical processing and without prior editorial review (Art. 6(1)(a) GDPR and, where political opinions or other special-category data may be visible, Art. 9(2)(a) GDPR). Submitters confirm the necessary image, voice, personality and usage rights; videos involving minors require consent from a parent or legal guardian. Consent may be withdrawn at any time for the future by emailing s.terekhov@me.com. Include the video ID shown after upload, the public link or, if neither is available, a short description of the video so that we can identify and hide it without delay.

Retention and deletion

Unpublished submissions, for example after failed processing, are automatically deleted from Cloudflare Stream and our video database by a protected maintenance job once they reach 30 days. If we subsequently withdraw a published video or consent is withdrawn, we remove it from every public selection without delay. If Cloudflare is temporarily unavailable, it remains hidden and the next maintenance run retries deletion. Published videos otherwise remain online until consent is withdrawn or the project ends. A technical publication and moderation log contains only a hashed video identifier, action, status and time and is deleted after 180 days. Analytics events are deleted after 90 days and daily aggregates after at most 24 months. Nginx logs rotate daily. Up to 14 archive files are retained alongside the current file. Empty files are not rotated; no additional age-based deletion is configured. Archives may therefore remain for more than 14 days.

Other legal bases and rights

Optional reach analytics is based on consent under Art. 6(1)(a) GDPR and Section 25(1) TDDDG. Technically necessary operation, security and the minimal moderation log are based on Art. 6(1)(f) GDPR. You can change your analytics choice below at any time and request access, correction, deletion or restriction by email. You may also complain to the Berlin Commissioner for Data Protection and Freedom of Information.

Hockey Atlas for iOS and Android

Sergey Terekhov, at the address stated above, is also responsible for the mobile app. The following information describes the current app. The sections about browser storage, website analytics and videos describe the website instead; those features are not part of the mobile app.

Local app data

In local mode, the app stores your profiles with display names and hockey details, personal sessions, attendance, saved invitations, responses, and language and city settings in a local SQLite database on your device. This mode needs no account. These contents are not automatically uploaded to our servers or synchronised between devices. The separate, optional community with a server account is described below; it does not automatically import your local profiles or plans. Local profiles are not published publicly. Depending on your device settings, operating-system backups or device transfers may include app data; this is not Atlas synchronisation.

Deliberate sharing

An invitation or response is passed to an app you choose only when you initiate sharing. Invitation links contain game details such as the title, venue and time, and the organiser's display name. Response links contain identifiers linking the invitation, session and responding profile, plus that profile's display name, response status and response time. Sharing also passes the session title as message text. The details in the link are encoded, not encrypted: anyone who receives the link can read and forward them. The selected messenger or other service processes the link under its own rules. Atlas does not send it automatically.

Map and external requests

To display the map, MapLibre Native loads the map style, vector tiles, fonts and symbols directly over HTTPS from tiles.openfreemap.org (Hyperknot Software Kft.). These requests transmit, in particular, your IP address, the time, requested map areas and zoom levels, and technical connection data. The app does not access your device's GPS location. Local profiles, sessions and invitation contents are not included in map requests. OpenFreeMap describes indefinitely retained anonymised server logs, possible temporary IP logging during security incidents, and possible use of Cloudflare. See the provider's privacy policy linked below for details.

Optional reminders

The reminder option for new sessions is enabled by default and can be switched off before saving. If it stays enabled and system permission is granted, the app schedules a local notification two hours before the start, provided that time is still in the future. No push token is registered with us and no session is sent to a notification server for this. The session title may appear on the lock screen. You can disable the app's notifications in system settings; the other features remain available.

Retention and removal

For local data, the app has no automatic deletion period and currently has no built-in function to delete all local data. On Android, you can delete app data in system settings using “Clear storage” or “Clear data”; clearing the cache alone is not enough. On iOS, “Delete App” removes the app and its local SQLite database; “Offload App” keeps the data. Archiving on Android does not delete the data either. This does not remove links already shared or recipients' copies. System backups may retain data and bring it back during a restore; manage them separately in your backup service's settings. We cannot view or remotely erase the local database on your device. Uninstalling or clearing local data does not delete a community account; use the account-deletion section below.

OpenFreeMap privacy policy

App support and privacy enquiries: s.terekhov@me.com

Optional Atlas community on the website, iOS and Android

The community is separate from local mode. It requires a configured service and connects only when you deliberately open this area. To publish or participate, you sign in and confirm that you are at least 18 when creating your community profile. Local profiles, family details, plans and invitations are not imported automatically.

Purposes and legal bases for the Atlas community

The service you request

For sign-in and account setup you request (including delivery and verification of the email code), session management, the necessary basic profile with display name and adult confirmation, and the team, game and attendance functions you choose, we process the objectively necessary information under Article 6(1)(b) GDPR: steps at your request before a contract and performance of the service contract. Free use can still involve a contract. The code is authentication, not marketing. Without the information necessary for a particular account function, we cannot provide that function; the public catalogue remains accessible without an account.

Optional visibility

Publishing your additional player card in the directory requires your separate active choice under Article 6(1)(a) GDPR. You can turn visibility off without deleting your account. A public card is not required to join games or apply to teams. Publishing the team and game details you create is, by contrast, the function you request and relies on Article 6(1)(b) GDPR for that purpose. Analytics, videos and other optional purposes have their separately described rules; accepting terms is not a substitute for consent.

Safety and reports

Abuse prevention, security logs, examination of reports and necessary documentation of moderation decisions serve our legitimate interests and those of affected members in a safe, functioning service (Article 6(1)(f) GDPR). We limit processing to what is necessary and consider the rights of those affected. You may object on grounds relating to your particular situation; we then assess whether compelling legitimate grounds override the objection. If a specific legal obligation requires processing, Article 6(1)(c) GDPR applies; this is not a general justification for retaining everything.

Existing accounts and changes

This clarification does not assign new consent or retrospective acceptance of terms to earlier activity. Existing accounts are expressly offered the current terms for future use. Previous optional consent choices are not replaced; withdrawal remains effective. The storage and deletion rules described below continue to apply.

Read the full terms

Evidence of accepting the terms

On explicit acceptance, we store the document version, language, SHA-256 hash of the immutable full text and first server-recorded acceptance time for each account identifier and version. Later versions do not overwrite this history. Submitting the same version again does not change the first entry. No extra IP address or device fingerprint is stored for this. The link records and implements the agreed service (Article 6(1)(b) GDPR); where a concrete dispute requires legal defence, we assess limited retention under Article 6(1)(f) GDPR. In normal operation the history stays with the account without automatic age-based deletion and is removed from the active database when the account is deleted. The encrypted-backup exceptions below still apply. Immutable terms texts without an account link remain as public documents.

Account and sign-in

For email-code sign-in, the service processes your email address; the mail provider receives the recipient address and code for delivery. A code is valid for at most ten minutes. The service also processes the connection's IP address; authentication rate limits store a hash derived from it, not the raw address. Stored records include account and sign-in identifiers, timestamps, verification hashes for codes and sessions, and hashed email and connection identifiers to limit sign-in attempts. Your email address is not shown to other users. Server sessions expire after at most seven days. In the central area at atlas.arena.hockey, sign-in can persist in this browser for up to seven days. For this purpose, api.atlas.arena.hockey sets a secure, HttpOnly session cookie valid only for that API host; JavaScript cannot read the credential inside it. The session is restored only when you deliberately open or refresh the community. The cookie is not sent to the city sites and is not used for analytics. Sign out when you finish on a shared device. Only confirmed sign-out ends the session; if the connection fails, the website offers a retry. The app keeps it in the operating system's secure storage, separately from the local SQLite database. On iOS, this credential may remain in Keychain across uninstalling and reinstalling the app; do not rely on uninstalling to end access, but use confirmed sign-out or account deletion. Server-session expiry and revocation still apply. Signing out does not delete an account.

Optional password

Email codes remain the default sign-in method. In app builds where this feature is enabled, you can optionally set a password for your existing community account. Setting or resetting it requires a fresh, unused email code. Both actions revoke all previous sessions and create a new session on this device lasting at most seven days. For password verification, the service stores a scrypt hash with a random salt, not a plaintext password. Password attempts use separate hashed email and connection identifiers in the existing sign-in history; records older than 24 hours undergo the technical cleanup described in this notice. The password verification record remains until replaced or the account is deleted; the stated backup exceptions still apply.

Shared data and visibility

The service stores your chosen display name, adult confirmation, team and game details you publish, participation states, and associated identifiers and timestamps. Active teams and visible games, including account-association identifiers and attendance counts, can be read without signing in. Participation is synchronised for the same account across devices. The organiser and participants marked as going can see the display names and states of interested and attending players in the roster, subject to blocks; the roster is not public. A profile alone is not published in a public people directory. Confirmation of access to a playing surface is the organiser's statement, not a booking or verification by Atlas.

Reporting and blocking

A submitted report about a team or game is stored on the server with its reason, target, reporting account and review status, and can be read by the responsible moderator. It is not public and is not resolved automatically. A block is stored between accounts and restricts shared discovery and new interactions. It does not automatically withdraw existing participation. Include only the information needed to review a report.

Retention and technical records

Shared profiles, teams, games, participation and reports currently have no automatic age-based deletion. Expired sessions, sign-in attempts older than 24 hours and codes expired for more than 24 hours are removed during technical cleanup, triggered by later accepted code requests or a maintenance run, not necessarily at expiry. A separate moderation log contains operation and target identifiers, an operator identifier, action and time, but no email addresses, display names or report text. This log survives account deletion and currently has no automatic deletion period.

Operating status and hosting

The community service at api.atlas.arena.hockey is reachable over the internet and runs on a server provided by Hetzner Online GmbH. Publishing and participating require sign-in and your own profile with confirmation that you are at least 18. Website access is separate from the availability of iOS and Android test builds. API access logging is disabled; technical error logs may contain connection and request data. Daily rotation retains up to 14 archive files alongside the current error log. Empty files are not rotated and there is no additional age-based removal, so older archives may remain for more than 14 days. The website's retention periods above do not automatically apply to the community.

Email delivery through Resend

Sign-in codes are delivered through Resend using accounts.arena.hockey and the Ireland (eu-west-1) sending region. Resend receives the recipient address and code message; TLS is enforced and open/click tracking is not enabled. The sending region is not the storage location: Resend stores email content, metadata and logs in the US. For our Free plan, Resend specifies 30 days for email and logs and seven days for its backups. Its data-processing agreement includes EU Standard Contractual Clauses.

Server backups

The community database is backed up daily with encryption. Cleanup removes valid backup files whose filename date and modification time are both more than seven days old, only after a successful new backup. If a backup is missed or fails, older files may remain longer. Account deletion does not immediately erase data from existing backups; intervening deletions must be reapplied before a restored database returns to service.

Player cards and one account across cities

The player area uses the same server account across all 14 configured cities and on your signed-in devices. A player card is separate from the community profile and remains unlisted unless you explicitly choose and save publication. The service stores your selected cities and disciplines, discovery setting, moderation status, version number, and creation and update times linked to your account identifier. The display name comes from your community profile. Only signed-in users who have confirmed that they are adults in their community profile can search published, non-hidden cards and see the account identifier, display name, selected cities and disciplines, subject to blocking. People who are not signed in cannot access this player directory. Email addresses and local family profiles are not part of the card. Switching discovery off removes the card from subsequent searches but does not delete its stored settings.

Team applications and membership

An application links your account to a team and stores its current state, version number and timestamps. Applying shares your display name with the team owner even if you have not published a player card. Application and membership details are accessible only to you as the applicant and the team owner, not as a public membership list or to other team members. You can withdraw a pending application or leave the team; the owner can accept or decline applications and remove members. Acceptance is Atlas team membership, not organiser authority, game attendance or publication of your player card.

Player reports and blocking

You can also report a player card or someone involved in your team relationship; the reporting disclosures above apply. Moderation can hide a player card and store a non-discoverable moderation marker for someone who has not published a card. This does not publish a card or end membership. Blocking hides your player cards from each other and withdraws pending applications between the applicant and team owner. Existing membership remains until the player leaves or the owner removes them; game participation is still managed separately.

Storage of player settings and team actions

Saved player cards, including unpublished settings, current application and membership states, and technical receipts for repeatable team actions currently have no automatic deletion period. These receipts prevent duplicate execution of repeated commands. They contain identifiers for the acting account, team and applicant account, a command identifier, a request hash and timestamp, but no copies of names, email addresses, free text or earlier profile views. Withdrawing, leaving or removing a member changes the current state rather than erasing the relationship and its receipts. Account deletion below and the existing exceptions for backups and the separate moderation log also apply to these data.

Community Rules acknowledgment

When you explicitly accept the Community Rules and save your profile, the service stores the latest accepted rules version and server timestamp linked to your account identifier. An existing profile does not count as acceptance. The first acknowledgment time is retained for the same version; accepting a later version replaces this record without a separate version history. The record is not visible in the player directory and has no automatic deletion period. Account deletion removes it from the active database; the stated backup exceptions still apply. This acknowledgment concerns conduct rules, not consent to data processing.

Resend: sending regions and data storage

Resend: processing, transfers and retention

Optional private profile details

In website and app versions with this feature, you may optionally save your first name, last name, gender, date of birth and a self-assessed hockey level. Every field may be left empty. These form a private profile you manage and can access on your devices when signed in with the same account. A provided birth date is checked against the adult age requirement; this is not independent age or identity verification. These details are not automatically imported from local or family profiles.

The details are stored with your account identifier in the community database, not in your public player card. Other players and team owners cannot see them through this feature. They are not currently used for automatic game matching, ratings, advertising or notifications. Saving does not change your visible player name or player-card visibility and does not enable analytics or push messages. The community-hosting information above applies to technical operation; the controller remains the operator named above.

These optional details rely on your consent under Article 6(1)(a) GDPR. A separate short notice appears before saving. The save action described there authorises processing of the fields you choose to fill in for this private profile. You may skip the step without losing account, team or game functions. Accepting the service terms or Community Rules does not replace this consent.

Each successful save containing at least one detail stores the version and language of the notice confirmed for that save, together with a server-recorded time, alongside the current record. This documents the current choice; no separate account history of earlier details or consent versions is created. A technical version counter and last-change time also help reconcile changes across devices. No extra IP address or device fingerprint is stored for this.

You can edit the details at any time or use “Clear private details” in the same profile area to withdraw consent and remove all five details. Evidence of the current consent is also removed from the active record. Your account, player name, player card and game attendance remain unchanged; the technical account link, version counter and last-change time remain until account deletion. There is no automatic age-based deletion: data remain until replaced, cleared or the account is deleted. Account deletion removes the entire private record from the active database. Withdrawal does not affect the lawfulness of processing before withdrawal.

The details and current consent record may be included in the encrypted server backups described above. Clearing details or deleting an account does not immediately erase existing backups. Cleanup after a successful new backup removes valid backup files whose filename date and modification time are both more than seven days old; missed or failed backups may leave older files for longer. Intervening deletions and withdrawals must be reapplied before a restored database returns to service.

You can also request access, correction, withdrawal or deletion through the privacy contact. Do not send passwords or sign-in codes.

s.terekhov@me.com · Account-deletion information

Hockey Atlas: delete your account and shared data

Open “My Hockey”, then “Teams & shared games”, sign in and select “Delete shared account”. Confirm permanent deletion. Only the success message confirms that the server completed deletion; a failed connection or simply signing out does not confirm it.

You can also request deletion by emailing s.terekhov@me.com without the app, reinstalling it or signing in. Name Hockey Atlas and the email address of the account to delete; write from that address if possible. Do not send sign-in codes or passwords. We need to verify that you are entitled to make the request; sending it is not yet confirmation of deletion.

Request account deletion by email

Account deletion removes the account email, community profile, password hash and salt, sessions, associated code requests, owned teams and games, and linked participation, blocks and reports from the active community database. Your games consequently disappear for others too. The separate technical moderation log remains as described above. Local profiles and plans, links already shared and recipients' copies are not deleted. Conversely, deleting the app or its local data does not delete a community account. Immediate deletion of all server backups is not promised. Deleting an Atlas account does not automatically delete Resend's delivery records either; the provider retention periods above apply.

This also removes your player card, linked team applications and memberships, and their technical command receipts from the active community database. Merely taking a card out of search or withdrawing an application is not account deletion.

Full provider details: Imprint
Updated: 15 September 2026