Kûkî û hilanîna herêmî
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
Hat nirxandin
DUEL hilanîna hewce ji bo lîstin, gihîştin û mîhengên hilbijartî bi kar tîne. Kûkiyên reklamê an skrîptên analîtîkê yên bijartî nînin; qebûla mecbûrî ya mercan te nake nav şopandinê.
Çi tê hilanîn
Gerok bi cuda tercîhên cîhazê, depoya hesabê piştrastkirî û tomarên guhertoyên berê diparêze. Kûkiyên hewce hesabê te yê bi xwe an gihîştina odeyê piştrast dikin. Hilanîn fonksiyonên xwestî pişt digire û profîleke reklamê çê nake.
Hesab ji bo gihîştina API __Host-duel_session bi kar tînin: heta 7 rojan an heta derketinê, vekişîna danişînê an jêbirina hesabê. Kûkî HttpOnly, Secure, SameSite=Strict e û ji JavaScript a rûpelê re negihîştî ye. Ceribandina herêmî ya cuda duel_session bi kar tîne û ne rêbazeke têketinê ya giştî ye.
Têketina odeyeke serhêl a mêvan kûkiya hewce ya __Host-duel_guest çê dike: heta 7 rojan, HttpOnly, Secure, SameSite=Strict. Ew di girêdana ji nû ve de cihê lîstikvan piştrast dike. Hilanîna herêmî tenê girêdana odeya dawî digire; kûkî ji JavaScript re ne berdest e. Pakkirina daneyên malperê gihîştinê ji cîhazê radike, lê odeya serverê li gorî heyamên hilanînê yên polîtîkaya nepeniyê diqede.
Danişîneke mêvan a herêmî ya nû profîl an pozîsyonê di navbera nûbarkirinan de naparêze. Mîheng, depoyên hesabê û profîlên kevn ên ji guhertoyên berê dikarin bê qedandina bixweber di gerokê de bimînin. Kopiyên kevn ên rewşên berê bixweber nayên jêbirin. Agahdariya hesabê ya depokirî û nîşaneya derketinê alîkariya vegerandina rewşa navberê dikin.
Teknolojiyên bijartî
Pîkselên reklamê û analîtîka tevgerê ne girêdayî ne. Têketina Google bijartî ye: hilbijartina wê te dibe Google û daneyên demkî yên hewce ji bo wê herikînê bi kar tîne; ew analîtîka reklama DUEL girê nade. Razîbûnên bijartî yên pêşhilbijartî nînin.
Heke teknolojiyên wiha derkevin, armanc, pêşkêşker û heyamên hilanîna wan dê berî çalakkirinê werin eşkerekirin. Li ku razîbûn hewce be, redkirin dê bi heman mercan wekî qebûlê berdest be, kategorî bi cuda û vekişîn bi heman hêsaniyê. Divê skrîptên bijartî berî ku bijartinek were kirin neyên barkirin.
Birêvebirina daneyan
Mijar, deng, anîmasyon û koordînat dikarin di mîhengên lîstikê de werin guhertin. Derketin gihîştina li ser cîhazê diqedîne, lê bi serê xwe dîrok an hesabê jê nake. Ji bo jêbirina hesabê rûpeleke cuda heye.
Tu dikarî pêşketina herêmî bi rêya mîhengên gerokê jê bibî: daneyên malperê veke, duel64.com hilbijêre û daneyên wê jê bibe. Ev dikare profîlên mêvan û herêmî yên wê malperê, lîstika niha û mîhengan jê bike. Berî jêbirinê, bizane ku vegerandin bê kopiyeke cuda ne mimkun e.
Astengkirina hilanîna hewce dikare domandina lîstikê û têketinê asteng bike. Daxwazên teknîkî yên ji Cloudflare re gava malper tê vekirin pêk tên, bêyî girêdanê bi hilanîna herêmî ve; ew di polîtîkaya nepeniyê de hatine ravekirin.
Nepenîya te
Tenê tiştê ku ji bo taybetmendiyên ku tu hilbijêrî hewce ye.
Ji bo daneyên hewce bişkoka “Hemûyan qebûl bike” tune ye. Pakkirina daneyên malperê dikare tercîhên cîhazê, depoyên herêmî û tomarên guhertoyên berê rake. Pêşketina hesabê ya serverê bi formake cuda tê jêbirin. Daxwazên teknîkî yên mêvandariyê di polîtîkayê de hatine ravekirin.