Kolačići i lokalna pohrana
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
Pregledano
DUEL koristi neophodnu pohranu za igru, pristup i odabrane postavke. Nema reklamnih kolačića ni skripti analitike koja nije obavezna; obavezno prihvatanje uslova te ne uključuje u praćenje.
Šta se čuva
Brauzer zasebno čuva postavke uređaja, predmemoriju provjerenog računa i zapise iz ranijih verzija. Neophodni kolačići potvrđuju tvoj vlastiti račun ili pristup sobi. Pohrana podržava tražene funkcije i ne pravi reklamni profil.
Računi koriste __Host-duel_session za API pristup: najviše 7 dana ili do odjave, opoziva sesije ili brisanja računa. Kolačić je HttpOnly, Secure, SameSite=Strict i nedostupan JavaScriptu stranice. Zaseban lokalni test koristi duel_session i nije javni način prijave.
Ulazak u sobu gosta na mreži pravi neophodni kolačić __Host-duel_guest: najviše 7 dana, HttpOnly, Secure, SameSite=Strict. On provjerava mjesto igrača pri ponovnom povezivanju. Lokalna pohrana drži samo link posljednje sobe; kolačić je nedostupan JavaScriptu. Brisanje podataka stranice uklanja pristup s uređaja, a soba na serveru ističe po rokovima čuvanja iz politike privatnosti.
Nova lokalna sesija gosta ne čuva profil ni poziciju između ponovnih učitavanja. Postavke, predmemorije računa i stari profili iz ranijih verzija mogu ostati u brauzeru bez automatskog isteka. Stare kopije prethodnih stanja ne brišu se automatski. Predmemorirani podaci računa i oznaka odjave pomažu da se vrati stanje interfejsa.
Tehnologije koje nisu obavezne
Reklamni pikseli i analitika ponašanja nisu povezani. Google prijava nije obavezna: njen izbor preusmjerava na Google i koristi neophodne privremene podatke za taj tok; ne povezuje reklamnu analitiku DUEL-a. Nema unaprijed odabranih pristanka koji nisu obavezni.
Ako se takve tehnologije pojave, njihove svrhe, pružaoci i rokovi čuvanja biće objavljeni prije uključivanja. Gdje treba pristanak, odbijanje će biti dostupno pod istim uslovima kao prihvatanje, kategorije zasebno, a povlačenje jednako lako. Skripte koje nisu obavezne ne smiju se učitati prije nego se izbor napravi.
Upravljanje podacima
Tema, zvuk, animacija i koordinate mogu se promijeniti u postavkama igre. Odjava završava pristup na uređaju, ali sama ne briše historiju ni račun. Za brisanje računa postoji zasebna stranica.
Lokalni napredak možeš obrisati kroz postavke brauzera: otvori podatke stranice, odaberi duel64.com i obriši njegove podatke. Ovo može obrisati profile gostiju i lokalne profile te stranice, trenutnu partiju i postavke. Prije brisanja zapamti da je vraćanje bez zasebne kopije nemoguće.
Blokiranje neophodne pohrane može spriječiti nastavak partije i prijavu. Tehnički zahtjevi prema Cloudflareu nastaju kad se stranica otvori, bez obzira na lokalnu pohranu; opisani su u politici privatnosti.
Tvoja privatnost
Samo ono što je potrebno za mogućnosti koje odabereš.
Nema dugmeta „Prihvati sve“ za neophodne podatke. Brisanje podataka stranice može ukloniti postavke uređaja, lokalne predmemorije i zapise iz ranijih verzija. Napredak računa na serveru briše se kroz zaseban obrazac. Tehnički zahtjevi hostinga opisani su u politici.