Privacy & data protection
The operating entity, jurisdiction and legal contact details have not yet been confirmed. This document is a draft for review, not a finalized legal notice. Identity verification remains unavailable. Email sending also remains disabled until sender and legal configuration is complete.
Updated 24 September 2026. This notice describes the data DECIDER uses and the rights tools available in the service. Items explicitly marked CONFIRMAR still require the controller’s legal decision; this notice does not certify legal compliance.
1. Data controller
[[CONFIRMAR: nome legal e morada da entidade]]
Privacy contact: [email protected]. DECIDER and decider.gg are the service name and domain, not the legal identity of the controller.
2. Data we use
- Account: email, username, profile, password hash, account status, preferences, terms acknowledgement and consent history.
- Steam: Steam identifier, public profile name and avatar, and linking time. Steam authentication does not disclose your Steam password to DECIDER.
- Play and community: rosters, parties, friend relationships, messages, tournament entries, scores, ratings, gameplay events, support conversations, attachments and moderation decisions.
- Purchases: Stripe customer and transaction references, amount, fulfilment, subscriptions, virtual coin movements, inventory and prizes. Card numbers and security codes are entered on Stripe’s hosted pages; DECIDER does not store them.
- Security: session times, access and error logs, IP-based rate-limit identifiers, verification status, encrypted authenticator secrets and hashed recovery codes.
- Desktop: random installation/runtime identifiers, version, foreground/background presence, connection times and usage duration. The presence feature does not capture your screen or files.
3. Purposes and legal bases
We use data necessary to provide accounts, requested matches, social features and purchases to perform the service agreement. Security and proportionate moderation protect players and the platform under legitimate interests, subject to balancing and safeguards. Applicable financial obligations and legal claims may require limited record retention. Optional marketing requires separate consent; it is unchecked by default and can be withdrawn in settings or through an email unsubscribe link. Accepting terms is not marketing consent.
[[CONFIRMAR: bases legais aplicáveis, avaliação de interesses legítimos e prazos de conservação fiscal na jurisdição da entidade]]
4. Providers and recipients
- Cloudflare: DNS, reverse proxy, HTTPS edge delivery and abuse protection. Network and request metadata (including IP address, headers and requested URL) pass through this service; configured browser network-error reports may also reach Cloudflare.
- Stripe: hosted checkout, subscription management, payment processing and billing. Stripe receives the payment details you submit to it, plus transaction and customer references. Its role may include independent-controller obligations.
- Brevo: individual account, verification, recovery and opted-in marketing emails; recipient email, message content and delivery metadata. Authentication mail does not enable application tracking pixels.
- Valve / Steam: Steam OpenID sign-in, account linking, public profile API and Steam-hosted avatar/map assets. This is an external identity/platform service, not automatically a DECIDER processor.
- Discord: when a platform or organizer webhook is configured, critical tournament alerts include tournament and match references, team names, reason and a control-room link. The configured channel’s authorized members can see them.
- Infrastructure: the production host operates the web applications, PostgreSQL, Redis, game servers and locally hosted support model. Encrypted recovery copies also go to a separate, access-restricted DECIDER operator computer. [[CONFIRMAR: entidade contratada para hosting, localização contratual e acordos de tratamento/transferência dos fornecedores]]
- Optional legacy integrations: Rankacy highlight-rendering code and an Allstar trial script remain in the repository. They are not part of the active production service inventory verified on this date. If re-enabled, gameplay uploads and their processing arrangements must be reviewed and this notice updated first.
GitHub and Node.js are used for software distribution/deployment, rather than as the account database. Staff access is limited by duties; public profiles and competition results are visible through their respective features. Support inference runs on the platform host. Linked third-party sites have their own policies.
5. Retention
The following schedule separates existing automated limits from proposed organizational limits. Proposed periods must not be mistaken for already-enforced automatic deletion.
- Accounts and profiles: for the account’s lifetime; deletion requests remove operational identity and social data after active competition dependencies are resolved. Proposed inactivity review: 24 months, with notice before closure.
- Messages: proposed maximum 12 months for ordinary community/private messages; messages belonging to a deletion request are removed or redacted by the account workflow. Reports and shared evidence require separate review.
- Sessions: expire after 8 hours of inactivity; account removal revokes sessions. Redis presence/rate-limit data uses short-lived keys; restored systems do not reinstate old sessions.
- Technical/security logs: proposed 30 days for ordinary diagnostics and 90 days for security investigations, extended only for a documented incident or legal hold.
- Payments and ledger: proposed restricted retention for 6 years after the relevant financial year, subject to the applicable local accounting/tax rules. Transaction identifiers and financial amounts remain; credentials and profile data are not needed for this purpose.
- Consent evidence: proposed 3 years after withdrawal or closure, restricted to demonstrating the choice; email marketing remains disabled after withdrawal.
- Email: existing cleanup removes expired verification/reset tokens after 7 days, delivery records after 90 days and daily budgets after 100 days; queued encrypted content is cleared at completion. Campaign messages expire after 7 days.
- Gameplay demos: existing retention is 30 days, extended to at most 180 days for an investigation or appeal. Demos are restricted to authorized review and access is logged. Statistical signals support human review.
- Backups: completed daily snapshots rotate after 14 days locally and at the external recovery destination. External cleanup runs when the recovery computer is available. A separate deletion ledger must be replayed before a backup can return to service.
Financial obligations, unresolved disputes and other lawful exceptions require a documented category, reason and review date. The deletion request is not labelled complete until remaining provider/evidence obligations have been reviewed. Data linked only to an internal identifier is pseudonymized, not necessarily anonymous.
6. Your rights
Account settings → Security → Your data provides a JSON download and a confirmed account-deletion request. The download includes your messages, consent records, Steam details, session metadata, purchases, wallet and competition data held by DECIDER. It excludes secrets and other people’s confidential information. Provider-held invoices/card data, shared demos and restricted reports can require a separately scoped request.
You can request access, correction, erasure, restriction, portability, objection or consent withdrawal at [email protected] or through Support. The normal response period is one month; any lawful extension or refusal must be explained. Identity verification must be proportionate. Account deletion requires a recent sign-in and explicit confirmation. Download your data before requesting deletion. Your verified reply email is kept separately for handling the request and removed 30 days after completion.
We preserve references needed to keep financial and competition records consistent while removing identifying account fields. Backups are not used as live databases; deletion instructions are reapplied before recovery. Remaining third-party copies and legal holds are reviewed operationally rather than silently claimed to be erased.
You may complain to the supervisory authority where you live, work or consider a breach occurred; in Spain this is the AEPD. The controller’s establishment and lead authority depend on the confirmed legal identity.
7. Security, age and changes
HTTPS, bcrypt password hashing, role checks, optional MFA, single-use verification codes, restricted recovery keys and encrypted backup archives reduce risk; they cannot guarantee that an incident will never occur. Account recovery does not bypass enabled MFA. See the cookie notice for session and preference storage.
[[CONFIRMAR: idade mínima, territórios servidos e eventual autorização parental]]
KYC remains inactive: the verification page does not collect identity documents or biometrics. Material changes to this notice should be communicated; a new marketing purpose cannot silently reuse previous consent.
Questions
Existing players can use DECIDER support for service questions. Do not submit identity documents there. A dedicated legal and privacy contact will be published before the verification service launches.