Cookies e almacenamento 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
Revisado
DUEL usa o almacenamento necesario para o xogo, o acceso e os axustes seleccionados. Non hai cookies de publicidade nin scripts de analítica opcional; a aceptación obrigatoria dos termos non te inscribe no seguimento.
O que se almacena
O navegador almacena por separado as preferencias do dispositivo, a caché da conta verificada e os rexistros de versións anteriores. As cookies necesarias autentican a túa propia conta ou o acceso á sala. O almacenamento serve para as funcións solicitadas e non crea un perfil de publicidade.
As contas usan __Host-duel_session para o acceso á API: ata 7 días ou ata o peche de sesión, a revogación da sesión ou a eliminación da conta. A cookie é HttpOnly, Secure, SameSite=Strict e inaccesible para o JavaScript da páxina. A proba local separada usa duel_session e non é un método público de inicio de sesión.
Entrar nunha sala en liña de convidado crea a cookie necesaria __Host-duel_guest: ata 7 días, HttpOnly, Secure, SameSite=Strict. Verifica o asento do xogador ao reconectarse. O almacenamento local só contén a ligazón da última sala; a cookie non está dispoñible para JavaScript. Limpar os datos do sitio quita o acceso do dispositivo, mentres que a sala do servidor caduca segundo os períodos de conservación da política de privacidade.
Unha sesión local de convidado nova non garda o perfil nin a posición entre recargas. Os axustes, as cachés da conta e os perfís antigos de versións anteriores poden permanecer no navegador sen caducidade automática. As copias antigas dos estados anteriores non se eliminan automaticamente. A información da conta na caché e un marcador de peche de sesión axudan a restaurar o estado da interface.
Tecnoloxías opcionais
Os píxeles de publicidade e a analítica de comportamento non están conectados. O inicio de sesión con Google é opcional: seleccionalo redirixe a Google e usa datos temporais necesarios para ese fluxo; non conecta a analítica de publicidade de DUEL. Non hai consentimentos opcionais preseleccionados.
Se aparecen esas tecnoloxías, as súas finalidades, os provedores e os períodos de conservación revelaranse antes da activación. Cando se precise o consentimento, rexeitar estará dispoñible en igualdade de condicións coa aceptación, as categorías por separado e a retirada igual de doada. Os scripts opcionais non deben cargarse antes de que se faga unha elección.
Xestión dos datos
O tema, o son, a animación e as coordenadas pódense cambiar nos axustes do xogo. Pechar a sesión remata o acceso no dispositivo, pero por si só non elimina o historial nin a conta. Proporciónase unha páxina separada para a eliminación da conta.
Podes eliminar o progreso local a través dos axustes do navegador: abre os datos do sitio, selecciona duel64.com e elimina os seus datos. Isto pode eliminar os perfís de convidado e locais dese sitio, o xogo actual e os axustes. Antes de eliminar, ten en conta que a restauración sen unha copia separada é imposible.
Bloquear o almacenamento necesario pode impedir a continuación dun xogo e o inicio de sesión. As solicitudes técnicas a Cloudflare prodúcense cando se abre o sitio, independentemente do almacenamento local; descríbense na política de privacidade.
A túa privacidade
Só o necesario para as funcións que escolles.
Non hai un botón “Aceptar todo” para os datos necesarios. Limpar os datos do sitio pode quitar as preferencias do dispositivo, as cachés locais e os rexistros de versións anteriores. O progreso da conta no servidor elimínase mediante un formulario separado. As solicitudes técnicas de aloxamento descríbense na política.