Strictly necessary uses
- Authentication, guest-room access, security, and session continuity.
- Language, accessibility, sound, game, and interface preferences saved on the device.
- Rejoin and private-room metadata that helps restore an active match without exposing private credentials in public pages.
- Versioned offline caches for approved public assets and fallback pages.
Optional measurement
The former optional product analytics, crash and error reporting, advertising measurement, Google Analytics, and acquisition and performance measurements are turned off. Screen and session recording have been removed. The app no longer shows consent controls for that former measurement stack, and earlier consent cannot restart it. The independent structured behavior history described in this policy is collected separately.
Managing storage
Browser or operating-system controls can clear local data and permissions. Clearing necessary storage may sign you out, remove preferences, or prevent automatic match reconnection. Clearing device storage does not delete server-side account or structured behavior history; use account deletion or the privacy contact to request deletion.
Optional measurement
The former optional product analytics, crash and error reporting, advertising measurement, Google Analytics, and acquisition and performance measurements are turned off. Screen and session recording have been removed. The app no longer shows consent controls for that former measurement stack, and earlier consent cannot restart it. The independent structured behavior history described in this policy is collected separately.
Essential account, gameplay, purchase, security and operational records remain necessary to provide the service. Historical measurement records remain subject to the existing retention and deletion rules. Account deletion still requests removal of registered Firebase Analytics and PostHog data; provider processing may take time. Contact the privacy address on this page to request access or deletion.
Structured behavior history
Durna Ludo collects its own structured history of app interactions and committed game facts to understand player journeys, investigate problems and improve the game. It records screens and controls that are shown, available or used, approved choices such as game or cosmetic options, training and game actions and their outcomes, gesture start/end positions relative to the board, including positions beyond its edges, timing and waits, startup and recovery, connection failures, and the app version. Visibility and the time a control is visible or usable can be recorded even when you do not activate it. This history is linked to your account after verified sign-in; eligible observations from before sign-in may be associated with that account. Collection is controlled centrally by Durna Ludo and starts enabled. This release has no personal collection switch.
This history does not capture screenshots, screen or session recordings, continuous pointer paths, text entered in fields, chat contents, audio, video, passwords or payment proofs. It does not restart Firebase Analytics, Crashlytics, Google Analytics or PostHog. Interaction and game-history entries expire 90 days after the server first receives them; derived reports do not extend that lifetime. Minimal account-generation and deletion safeguards may remain longer to prevent old or deleted history from returning. Account deletion requests removal of account-linked behavior history. Shared game facts can remain without your account linkage. Backups follow separate retention schedules and can retain older bytes until those backups expire. Contact the privacy address on this page to request access or deletion.
Live audience and store reports
Durna Ludo counts current foreground app and browser sessions using short-lived server records and the reported runtime platform. Verified signed-in accounts are counted once across platforms; anonymous sessions are counted separately and can include several tabs or devices used by one person. Session tokens stay in memory, and presence expires within 90 seconds without renewal. The presence store uses keyed account and network hashes rather than raw account identifiers or IP addresses; account deletion requests removal of linked presence. Durna Ludo also imports aggregate Google Play installation, store, quality and financial reports for its private administrator dashboard. Google Play user totals are not linked to individual Durna accounts. These reports and foreground counts do not restart optional analytics SDKs or screen/session recording.