Koekies en plaaslike berging
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
Hersien
DUEL gebruik nodige berging vir spel, toegang en gekose instellings. Daar is geen advertensiekoekies of opsionele analiseskripte nie; verpligte aanvaarding van die bepalings teken jou nie vir nasporing in nie.
Wat gestoor word
Die blaaier stoor afsonderlik toestelvoorkeure, die kas van die geverifieerde rekening en rekords van vroeëre weergawes. Nodige koekies outentiseer toegang tot jou eie rekening of kamer. Berging ondersteun versoekte funksies en skep nie 'n advertensieprofiel nie.
Rekeninge gebruik __Host-duel_session vir API-toegang: tot 7 dae of tot afmelding, sessieherroeping of rekeninguitvee. Die koekie is HttpOnly, Secure, SameSite=Strict en ontoeganklik vir bladsy-JavaScript. Die afsonderlike plaaslike toets gebruik duel_session en is nie 'n openbare aanmeldmetode nie.
Om 'n gas-aanlynkamer binne te gaan, skep die nodige __Host-duel_guest-koekie: tot 7 dae, HttpOnly, Secure, SameSite=Strict. Dit verifieer die speler se sitplek by herverbinding. Plaaslike berging hou slegs die skakel na die laaste kamer; die koekie is nie vir JavaScript beskikbaar nie. Die skoonmaak van werfdata verwyder toegang vanaf die toestel, terwyl die kamer op die bediener onder die privaatheidbeleid se retensietydperke verval.
'n Nuwe plaaslike gassessie stoor nie die profiel of stelling tussen herlaaie nie. Instellings, rekeningkaste en ou profiele van vroeëre weergawes kan in die blaaier bly sonder outomatiese verval. Ou kopieë van vorige toestande word nie outomaties uitgevee nie. Gekaste rekeninginligting en 'n afmeldmerker help om die koppelvlaktoestand te herstel.
Opsionele tegnologieë
Advertensiepixels en gedragsanalise is nie gekoppel nie. Aanmeld met Google is opsioneel: die keuse daarvan herlei na Google en gebruik nodige tydelike data vir daardie vloei; dit koppel nie DUEL-advertensie-analise nie. Daar is geen vooraf gekose opsionele toestemmings nie.
As sulke tegnologieë verskyn, sal hul doeleindes, verskaffers en retensietydperke voor aktivering bekendgemaak word. Waar toestemming nodig is, sal weiering op gelyke voet met aanvaarding beskikbaar wees, kategorieë afsonderlik en onttrekking net so maklik. Opsionele skripte mag nie laai voordat 'n keuse gemaak is nie.
Bestuur van data
Tema, klank, animasie en koördinate kan in spelinstellings verander word. Afmelding beëindig toegang op die toestel, maar vee nie op sigself die geskiedenis of die rekening uit nie. 'n Afsonderlike bladsy word vir rekeninguitvee voorsien.
Jy kan plaaslike vordering deur blaaierinstellings uitvee: maak werfdata oop, kies duel64.com en vee die data daarvan uit. Dit kan daardie werf se gas- en plaaslike profiele, huidige spel en instellings uitvee. Voor uitvee, let daarop dat herstel sonder 'n afsonderlike kopie onmoontlik is.
Die blokkering van nodige berging kan die voortsetting van 'n spel en aanmeld verhoed. Tegniese versoeke aan Cloudflare vind plaas wanneer die werf oopgemaak word, ongeag plaaslike berging; hulle word in die privaatheidbeleid beskryf.
Jou privaatheid
Slegs wat nodig is vir die funksies wat jy kies.
Daar is geen “Aanvaar alles”-knoppie vir nodige data nie. Om werfdata skoon te maak, kan toestelvoorkeure, plaaslike kasse en rekords van vroeër weergawes verwyder. Rekeningvordering op die bediener word deur 'n aparte vorm uitgevee. Tegniese gasheerversoeke word in die beleid beskryf.