Cookieak eta biltegiratze lokala
For a connected DUEL account, we retain sign-in platform records. Separate usage events require new optional consent; their collection is off by default.
Aggregate website counters · 18 November 2026
Submission starts only after your separate optional permission for website statistics. Declining does not restrict play. The browser stores only your choice and its expiry for up to 180 days, without a visitor identifier; withdrawal stops new submissions. DNT/GPC block submission even with saved permission. This choice does not enable separate personal analytics-v2 events. New counters in the native iPhone/Android clients are off.
When DUEL counters are enabled, the browser sends a page-opening or known-link click type, section category, language and bounded public campaign labels. The server increments separate daily totals per category; the approximate request country comes from Cloudflare infrastructure. These counters retain no full URLs, search parameters, IP addresses, cookies, device or account identifiers, or persistent guest IDs. Visits are not linked into a person’s history and data is not shared with advertising networks. Totals are available to the owner for the last 90 days; repeat openings count separately and coverage is incomplete. DNT=1 disables browser submission. This does not enable advertising pixels, purchases or personal analytics-v2 events, which continue to require separate optional consent.
Platforms and optional analytics · addendum dated 16 November 2026
platform-source-privacy-v1-2026-11-16
This dated addendum updates platform records and optional events. Earlier statements below about disabled analytics describe the base edition; this addendum governs these two topics. The other base provisions remain applicable.
For a connected account, the shared DUEL server on Cloudflare stores the registration source when known, first known and most recent recorded launch, first/last dates per platform and how the source was established. An older account’s registration source can remain unknown; a new observation does not become its early history. A verified publisher session differs from an app-declared PWA, native or desktop runtime. These records support sign-in and cross-platform play and help us understand use of the shared service; they do not substitute for optional-event consent.
Permitted UTM source and medium values become bounded known labels, and campaign becomes a public DUEL slug. Only an external hostname is retained from a referral. Full URLs, paths, query strings, advertising IDs, search queries, launch proofs and tokens do not enter these records. Do not put names, contacts or sensitive information in campaigns. These records do not become an advertising profile and are not sent to a third-party analytics service.
The current platform does not replace the first known source. The DUEL owner can view these records in the protected administration panel. Completed-game and real-purchase counters use server results and payment receipts; test payments are excluded and refunds are counted separately. A payment channel is not treated as the acquisition source. A participant’s platform is recorded by the server; where it was not observed, cross-platform history remains unknown.
Separate optional analytics is off by default in DUEL. Even when that feature is enabled, the server accepts events only after your explicit current analytics-v2 choice. Earlier analytics-v1 consent, mandatory terms acceptance and publisher sign-in do not enable these events. Declining does not restrict play; you can withdraw in account settings. This analytics is not enabled for the closed family/learning mode.
Only app, Academy, collection and Premium opening events are permitted. A record contains a link to your DUEL account UUID, a technical event UUID, event type, platform and how it was established, time and consent version. Events contain no arbitrary text, contacts, moves, voice, medical or other sensitive data. Third-party pixels and analytics SDKs are not connected.
First/last launch and per-platform dates remain until account deletion. Match-platform snapshots are available for up to 100 days and optional events for up to 90 days; expired records are deleted in bounded technical batches. Optional events are capped at 100 per day and 1000 per account, and match snapshots at 2000 per account. Limits and absent consent mean incomplete coverage, not absent activity.
These records are included in your own paginated account export. Deleting the account removes linked records from the main database; the base policy’s backup limits still apply. For access, correction or deletion, contact support@duel64.com. Guests receive no persistent visitor ID for this analytics. This addendum does not enable purchases, advertising or promotional email.
Unchanged base edition · privacy-v15-2026-10-21
Berrikusita
DUEL-ek beharrezko biltegiratzea erabiltzen du jokorako, sarbiderako eta hautatutako ezarpenetarako. Ez dago publizitate-cookierik edo analitika-script aukerakorik; baldintzen onarpen nahitaezkoak ez zaitu jarraipenean sartzen.
Zer gordetzen den
Arakatzaileak gailu-hobespenak, kontu berretsiaren cachea eta aurreko bertsioen erregistroak bereizita gordetzen ditu. Beharrezko cookieek zure kontu propioa edo gelarako sarbidea autentifikatzen dute. Biltegiratzeak eskatutako funtzioak sostengatzen ditu eta ez du publizitate-profilik sortzen.
Kontuek __Host-duel_session erabiltzen dute API sarbiderako: gehienez 7 egun edo saioa amaitu, saioa indargabetu edo kontua ezabatu arte. Cookiea HttpOnly, Secure, SameSite=Strict da eta orriko JavaScript-entzat atziezina. Proba lokal bereiziak duel_session erabiltzen du eta ez da saio-hasiera publikoaren metodo bat.
Gonbidatuaren lineako gela batera sartzeak beharrezko __Host-duel_guest cookiea sortzen du: gehienez 7 egun, HttpOnly, Secure, SameSite=Strict. Jokalariaren eserlekua egiaztatzen du berriro konektatzean. Biltegiratze lokalak azken gelarako esteka soilik gordetzen du; cookiea JavaScript-entzat ez dago erabilgarri. Gunearen datuak garbitzeak sarbidea kentzen du gailutik, eta zerbitzari-gela pribatutasun-politikaren atxikipen-epeen arabera iraungitzen da.
Gonbidatu-saio lokal berri batek ez du profila edo posizioa gordetzen birkargatzeen artean. Ezarpenak, kontu-cacheak eta aurreko bertsioen profil zaharrak arakatzailean gera daitezke iraungitze automatikorik gabe. Aurreko egoeren kopia zaharrak ez dira automatikoki ezabatzen. Cachean dagoen kontu-informazioak eta saioa amaitu izanaren markatzaile batek interfazearen egoera berrezartzen laguntzen dute.
Teknologia aukerakoak
Publizitate-pixelak eta portaera-analitika ez daude konektatuta. Google saio-hasiera aukerakoa da: hautatzeak Google-ra birbideratzen du eta fluxu horretarako beharrezko datu behin-behinekoak erabiltzen ditu; ez du DUEL-en publizitate-analitika konektatzen. Ez dago aurrez hautatutako baimen aukerakorik.
Teknologia horiek agertzen badira, haien helburuak, hornitzaileak eta atxikipen-epeak aktibatu aurretik jakinaraziko dira. Baimena behar denean, uko egitea onarpenaren baldintza berdinetan egongo da erabilgarri, kategoriak bereizita eta kentzea onartzea bezain erraz. Script aukerakoak ezin dira kargatu aukera bat egin aurretik.
Datuak kudeatzea
Gaia, soinua, animazioa eta koordenatuak joko-ezarpenetan alda daitezke. Saioa amaitzeak gailuko sarbidea amaitzen du, baina ez du berez historia edo kontua ezabatzen. Kontua ezabatzeko orri bereizi bat dago.
Aurrerapen lokala arakatzaile-ezarpenen bidez ezaba dezakezu: ireki gunearen datuak, hautatu duel64.com eta ezabatu haren datuak. Honek gune horren gonbidatu- eta profil lokalak, uneko partida eta ezarpenak ezaba ditzake. Ezabatu aurretik, kontuan izan kopia bereizirik gabe berrezartzea ezinezkoa dela.
Beharrezko biltegiratzea blokeatzeak partida bat jarraitzea eta saio-hasiera galaraz ditzake. Cloudflare-rako eskaera teknikoak gunea irekitzen denean gertatzen dira, biltegiratze lokala edozein dela ere; pribatutasun-politikan deskribatzen dira.
Zure pribatutasuna
Aukeratzen dituzun eginbideetarako behar dena soilik.
Ez dago “Onartu dena” botoirik beharrezko datuetarako. Gunearen datuak garbitzeak gailu-hobespenak, cache lokalak eta aurreko bertsioen erregistroak ken ditzake. Zerbitzariko kontu-aurrerapena formulario bereizi baten bidez ezabatzen da. Ostalaritza-eskaera teknikoak politikan deskribatzen dira.