Kukis da ajiyar gida
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
An yi bita
DUEL yana amfani da ajiya da ta wajaba don wasa, shiga da saitunan da aka zaɓa. Babu kukis na talla ko rubutun nazari na zaɓi; karɓar sharuɗɗa tilas ba ta saka ka cikin bin diddigi ba.
Abin da ake ajiya
Burauza tana ajiye zaɓuɓɓukan na'ura, ajiyar asusun da aka tabbatar da rikodi daga sigogi na baya daban. Kukis da suka wajaba suna tabbatar da asusunka ko shigar ɗaki. Ajiya tana goyon bayan ayyukan da aka nema kuma ba ta ƙirƙirar bayanan talla ba.
Asusu suna amfani da __Host-duel_session don shigar API: har zuwa kwanaki 7 ko har fita, soke zaman ko goge asusu. Kukis ɗin HttpOnly ne, Secure, SameSite=Strict kuma ba za a iya shiga shi daga JavaScript na shafi ba. Gwaji na gida daban yana amfani da duel_session kuma ba hanya ta shiga na jama'a ba ne.
Shiga ɗakin yanar gizo na baƙo yana ƙirƙirar kukis ɗin __Host-duel_guest da ya wajaba: har zuwa kwanaki 7, HttpOnly, Secure, SameSite=Strict. Yana tabbatar da wurin ɗan wasa a sake haɗawa. Ajiyar gida tana riƙe mahaɗin ɗaki na ƙarshe kawai; kukis ɗin ba ya samuwa ga JavaScript. Share bayanan shafi yana cire shiga daga na'ura, yayin da ɗakin uwar garke ke ƙarewa a ƙarƙashin lokutan ajiyar manufar sirri.
Sabon zaman baƙo na gida baya ajiye bayanan kai ko hali tsakanin sake lodi. Saituna, ajiyar asusu da tsoffin bayanan kai daga sigogi na baya na iya zama a burauza ba tare da ƙarewa da kanta ba. Ba a goge tsoffin kwafin tsoffin halaye da kansu ba. Bayanan asusu da aka ajiye da alamar fita suna taimakawa dawo da halin fuska.
Fasahohi na zaɓi
Ba a haɗa pikisal na talla da nazari na hali ba. Shiga ta Google na zaɓi ne: zaɓar shi yana tura zuwa Google kuma yana amfani da bayanan ɗan lokaci da suka wajaba don wannan hanya; baya haɗa nazari na talla na DUEL. Babu yardodi na zaɓi da aka riga aka zaɓa.
Idan irin waɗannan fasahohi suka bayyana, za a bayyana manufofinsu, masu samarwa da lokutan ajiya kafin kunnawa. Inda ake buƙatar yarda, ƙi zai kasance a samu daidai da karɓa, rukunoni daban kuma janyewa da sauƙi iri ɗaya. Rubutun na zaɓi ba za su loda ba kafin a yi zaɓi.
Kula da bayanai
Ana iya canza jigo, sauti, raye-raye da alamomin murabba'i a saitunan wasa. Fita tana ƙare shiga a na'ura amma ba ta goge tarihi ko asusu da kanta ba. An bayar da shafi daban don goge asusu.
Kana iya goge ci gaban gida ta saitunan burauza: buɗe bayanan shafi, zaɓi duel64.com ka goge bayanansa. Wannan na iya goge bayanan kai na baƙo da na gida na wannan shafi, wasan yanzu da saituna. Kafin gogewa, lura cewa dawowa ba tare da kwafi daban ba ba zai yiwu ba.
Toshe ajiya da ta wajaba na iya hana ci gaba da wasa da shiga. Buƙatun fasaha zuwa Cloudflare suna faruwa idan an buɗe shafi ko da ajiyar gida; an bayyana su a manufar sirri.
Sirrinka
Abin da ake buƙata kawai don fasalolin da ka zaɓa.
Babu maɓallin “Karɓi duka” don bayanan da suka wajaba. Share bayanan shafi na iya cire zaɓuɓɓukan na'ura, ajiyar gida da rikododin sigogi na baya. Ana goge ci gaban asusu na uwar garke ta fom daban. An bayyana buƙatun saukarwa na fasaha a cikin manufar.