Cookies y almagazenamiento local
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
Revisau
DUEL usa almagazenamiento necesario pa o chuego, l'acceso y os achustes triaus. No bi ha cookies de publicidat ni scripts d'analítica opcional; l'acceptación obligatoria d'as condicions no te incluye en o seguimiento.
Qué s'almagazena
O navegador almagazena deseparadament as preferencias de l'aparato, a caché d'a cuenta verificada y os rechistros de versions anteriors. As cookies necesarias autentican a tuya propia cuenta u l'acceso a una sala. L'almagazenamiento sostiene as funcions demandadas y no crea un perfil publicitario.
As cuentas usan __Host-duel_session pa l'acceso a la API: dica 7 días u dica salir, a revocación d'a sesión u a eliminación d'a cuenta. A cookie ye HttpOnly, Secure, SameSite=Strict y inaccessible pa o JavaScript d'a pachina. A preba local deseparada usa duel_session y no ye un metodo publico d'encete de sesión.
Dentrar en una sala en linia de convidau crea a cookie necesaria __Host-duel_guest: dica 7 días, HttpOnly, Secure, SameSite=Strict. Verifica a plaza d'o chugador en a reconexión. L'almagazenamiento local guarda nomás o vinclo d'a zaguera sala; a cookie no ye disponible pa JavaScript. Borrar os datos d'o puesto saca l'acceso de l'aparato, mientres que a sala d'o servidor caduca seguntes os periodos de conservación d'a política de privacidat.
Una sesión nueva de convidau local no alza o perfil ni a posición entre recargas. Os achustes, as cachés d'a cuenta y os perfils antigos de versions anteriors pueden permanecer en o navegador sin caducidat automatica. As copias antigas d'estaus anteriors no se borran automaticament. A información d'a cuenta en caché y un marcador de salida aduyan a restaurar l'estau d'a interficie.
Tecnolochías opcionales
Os pixels publicitarios y l'analítica de comportamiento no son connectaus. L'encete con Google ye opcional: triar-lo redirige ta Google y usa datos temporals necesarios pa ixe flujo; no connecta l'analítica publicitaria de DUEL. No bi ha consentimientos opcionales preseleccionaus.
Si apareixen ixas tecnolochías, se comunicarán as suyas finalidaz, os suyos proveyedors y os plazos de conservación antes de l'activación. Cuan calga o consentimiento, a negativa será disponible en as mesmas condicions que l'aceptación, as categorías por separau y a retirada igual de fácil. Os scripts opcionals no han de cargar antes que se faiga una triga.
Chestión d'os datos
O tema, o son, a animación y as coordenadas se pueden cambiar en os achustes d'o chuego. Zarrar a sesión remata l'acceso en o dispositivo, pero no borra por sí mesmo ni l'historial ni a cuenta. Se facilita una pachina separada ta borrar a cuenta.
Puetz borrar o progreso local a traviés d'os achustes d'o navegador: ubre os datos d'o sitio, tría duel64.com y borra os suyos datos. Isto puet borrar d'ixe sitio os perfils d'invitau y os perfils locals, a partida actual y os achustes. Antes de borrar, ten en cuenta que a restauración sin una copia separada ye imposible.
Bloqueyar l'almacenamiento necesario puet impedir continar una partida y iniciar sesión. As peticions técnicas enta Cloudflare se producen cuan s'ubre o sitio, sin depender de l'almacenamiento local; se describen en a política de privacidat.
A tuya privacidat
Nomás lo que cal pa as funcions que trias.
No bi ha un botón “Acceptar tot” pa os datos necesarios. Borrar os datos d'o puesto puet sacar as preferencias de l'aparato, as cachés locals y os rechistros de versions anteriors. O progreso d'a cuenta en o servidor se borra con un formulario deseparau. As demandas tecnicas d'alochamiento se describen en a política.