What data a match needs
Data-processing policy for the Stack5 app and website.
About your data in Stack5 and account deletion.
Contents
Who is responsible for processing
Data processing is organized by the Stack5 project. As of this publication, the project has no registered legal entity. For data questions and deletion requests, use support@stack5.org.
What data is processed
- Account data: profile identifier, name, interface language, verified email and, for email sign-in, a password hash. Stack5 never stores the original password. Apple or Google sign-in uses the identifier and information supplied by the selected provider.
- Player profile: game nickname, avatar, city, Premier/FACEIT ratings, manually set skill level, and verified SteamID64 after Steam sign-in.
- Participation and communication data: lobbies, teams, readiness, invitations, map decisions, match results, game statistics, event history, chat messages and reports. User-uploaded profile and team images are also processed.
- Event data: some organized events retain payment status, amount, currency and an operational note. These records are not a club PC tariff catalogue: the club sets its on-site prices and conditions. Stack5 does not process bank cards or payment credentials; club services are paid for at the club.
- Security data: hashes of QR codes and browser-session tokens, session lifetime, blocks, reports, and operational events used to protect sign-in and investigate incidents.
- Notification and reward data: device token and notification settings when push notifications are enabled; S5 Points balance and transactions, reward requests and, if provided for delivery, a private Steam Trade Offer URL.
- When temporary club game accounts are used: credentials supplied by the club for individual player assignment.
Why it is needed
- To create and protect an account, lobby, and access to Stack5 Play.
- To assemble a roster, assign teams, run map selection, and prepare a match.
- To give server access, a temporary game account, or a team room only to the required participant.
- To show results, statistics, and event history and keep the service operating safely.
- To deliver selected notifications, record S5 Points and handle reward requests; to review reports and limit abuse.
Who may see the data
Other players and organizers see only data needed for a specific event: game nickname, participation, team, readiness, results, and statistics. Profile identifiers and SteamID64 are not shown in ordinary public game views.
Choosing Apple, Google or Steam sign-in uses the relevant authentication service; permitted push notifications use Apple Push Notification service on iOS or Firebase Cloud Messaging on Android. If an event includes a managed server, Stack5 sends the match provider only the configuration data it needs, including SteamID64 and game nickname. In the current setup, such components may include DatHost and MatchZy.
Temporary club account credentials are never shown on public screens and are transmitted only to the assigned player through a protected channel.
Country, city and map providers
Your manually selected country and city are saved to your profile to show relevant clubs, events and city sections. This is not GPS: the app does not request device location, and browsing another map area does not change your profile city.
When you open the map, its images are loaded directly from CARTO if configured in the build, otherwise from OpenStreetMap. The provider receives your IP address, the app's technical User-Agent, the requested tile coordinates and request times. These coordinates describe the map you browse, not your precise location. Stack5 does not send your game-account identifier, email or SteamID in tile requests.
These requests serve map rendering, secure operation and abuse prevention. Under CARTO's terms dated 29 September 2026, IP addresses are truncated on ingestion and technical request logs are retained for 30 days in the United States; CARTO processes them as Stack5's service provider. OpenStreetMap's policy describes requests to its services. Contact support@stack5.org for data requests.
Website analytics
The public Stack5 website uses Google Analytics to assess traffic and page performance in aggregate. Google may process technical browser data and page interactions under its own privacy policy.
Analytics is not used to manage a game account, a lobby roster, server access, or match decisions.
Storage and deletion
Data is retained while needed for the account and events, match and reward history, security, and handling requests. After account deletion, personal data is removed or anonymized; necessary match, transaction, and incident records may remain without a public link to the deleted profile.
Delete your account in the app under Profile → Account & Safety → Delete account. For additional personal-data requests, contact support@stack5.org. Active-event participation and open reward requests are handled as part of account deletion.
Changes to this policy
The current policy version is stack5-privacy-2026-10-03. If the data categories, processing methods, or operator status change materially, we will update this page and request renewed consent in the app.