Privacy policy

Data controller

The following operator is responsible for the personal data described in this privacy policy.

Legal name

Saeed Chegini

Address

Geiavej 4, 2680 Solrød Strand, Denmark

[email protected]

View the legal notice and operator details

Data we process

• Account data: guest, Google, Apple, or demo account identifiers; email and name supplied during sign-in, including an Apple private-relay email address when provided; provider or uploaded profile images; authentication records and linked sign-in methods; your chosen public nickname and avatar; your confirmation that you are 18 or older and declaration history; age groups and birth years previously declared by existing accounts and their retained history; chosen country and a coarse country hint inferred from network location; preferred language; and optional gender/profile choices. For new profiles, setup suggests an editable nickname from Google or Apple when a usable name is available, and a generated nickname otherwise. You can keep or replace the suggestion; the suggested name becomes public only after you confirm it. During first setup, your sign-in picture is selected by default when Google or Apple supplies one. You can keep it or choose an avatar before saving. Only the picture you confirm is shown to other players, and you can change it later in Settings. Later sign-ins preserve your saved choice. By continuing first-time setup, you confirm that you are 18 or older. Age declarations stay private and are not included in account-setup analytics. Connecting a sign-in method associates it with this account; it does not merge two existing accounts.
• Account contact data: a provider-supplied email is stored in encrypted form with its verification and private-relay status. It can be viewed only by separately authorized Durna Ludo support administrators for account support and future communication readiness; it is not sent to product analytics providers.
• Uploaded profile images: when this feature is enabled and you choose an image, Durna Ludo stores server-generated 128px and 512px WebP renditions plus lifecycle and moderation metadata. The active image is publicly retrievable through an unguessable URL. Replaced or reset images can remain public for the configured match-history retention period (currently 31 days); images removed by moderation or account deletion are quarantined immediately.
• Apple authorization data: when Apple sign-in is enabled, Durna Ludo encrypts and retains a server-side refresh credential only to validate or revoke the Apple authorization. It is never placed in browser or app storage and is not used by Google sign-in.
• Profile discovery data: social search uses a one-way hash of the normalized email address for exact-email lookup and can match text against public display names. Search results never return email addresses. New writes do not persist the normalized address; older profile records may retain it until the documented operational cleanup is completed.
• Gameplay data: game choices, match state, results, history, room membership, invitations, and private-room moderation records.
• Social and communication data: profile settings and images, friends and close friends, direct messages including pictures or GIFs you choose to send, chat, reactions, invitations, reports, and connection and participation data for live rooms and calls. Durna Ludo does not record live voice, video, or call media. Community features and stored Club voice notes are unavailable in this release.
• Economy and purchase data: account-bound Gold, Diamonds, other virtual balances, cosmetic ownership, loadout, progression, Google Play product and subscription status, purchase-token and transaction references, entitlements, grants, refunds/revocations, and reconciliation records. Durna Ludo does not receive payment-card details from Google Play. Virtual value can be granted, earned, spent, or purchased where eligible, but it is not cash and has no prize value.
• Technical data: IP and request records handled by hosting infrastructure, device and browser details, logs, security signals, and approved performance or product events.
• Account activity data: Durna Ludo can retain coarse server-side times for sign-in, matchmaking, match outcomes and duration, reconnects, purchases, and profile or moderation-summary changes. This activity does not include moves, cards, message contents, private social graphs, room credentials, provider subjects, or authentication tokens.

How we use data

• Authenticate accounts, preserve sessions, run matches, reconnect players, and deliver owned cosmetics.
• Operate matchmaking, rooms, social tools, moderation, abuse prevention, support, and service diagnostics.
• Provide an access-controlled support directory and aggregate game dashboards. Low-priority activity collection is best effort and may be incomplete during overload or service interruption.
• 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.

Services involved

This release uses Google and Apple sign-in where offered; Google Play for available purchases, subscriptions and purchase-status notifications; Firebase for optional push and incoming-call notifications when allowed; Cloudflare and the application host for delivery and protection; PostgreSQL on the application host in Berlin for active application data, including structured behavior history; configured media infrastructure for live calls; and configured content providers. Pre-migration Azure Cosmos DB data and separate encrypted Azure backups remain subject to their retention and deletion rules. The former optional measurement stack is off and screen/session recording is removed. Historical Firebase Analytics and PostHog records remain subject to provider retention and deletion processes. Community features, stored voice notes and server-side PostHog event export remain disabled.

Retention and security

Records are retained for the period needed to provide the service, meet configured operational or legal requirements, resolve disputes, and prevent abuse. Retention differs by record type. Durna Ludo uses technical and organizational safeguards, but no online service can promise absolute security.

The encrypted account contact and captured account activity are retained while the account exists. Account deletion removes this identifiable data and requests deletion of the corresponding PostHog identity. Anonymous daily game aggregates can be retained without an expiry, and privacy-safe administrative security records can be retained for up to three years. Backup copies expire under the backup schedule and deletion is reapplied before a restored system serves data.

Direct messages are retained for no more than 90 days and only the newest 500 messages in a conversation are available. Removing a friend makes retained history read-only. Blocking in either direction hides the conversation and prevents reads and sends; unblocking does not restore sending unless the friendship is accepted again. Message operations are measured without storing message text, previews, or participant identifiers in operational telemetry.

Stored Club voice notes are unavailable in this release. If older voice-note records exist, their audio and metadata normally expire together 90 days after creation. A moderation-evidence reference can extend retention for the configured evidence period, and a separately authorized legal hold can suspend ordinary deletion. Reads remain subject to current access controls. Live voice, video, and calls are not recorded or retained as media by Durna Ludo.

Your choices and requests

The following deletion rules also cover any stored voice notes from an earlier configuration, if those records exist. Signed-in players can permanently delete their Durna Ludo account in Settings. Once the request is durably accepted, every account session is fenced and background cleanup removes profile and social data, including every direct-message conversation involving the account, coins, virtual items, loadout, progression, and other mutable account data. Owner-scoped Club voice notes are deleted unless an authorized evidence or legal-hold policy requires a retained-by-policy result; purchase-receipt replay fences can remain only with account ownership anonymized. Removing a conversation also removes its retained history from the other participant. Active matches and rooms may be modified so play or settlement can continue. Direct identity is removed from completed shared-match and required audit records. Where integrity requires a non-empty reference, a random alias remains pseudonymous while its deletion mapping exists; when deletion completes, that mapping is scrubbed so the alias is no longer linkable to the deleted account. A limited one-way deletion receipt expires after 90 days.

Deleting your Durna Ludo account does not delete your Google or Apple account or records controlled by those providers. Manage or cancel your Google Play subscriptions in Google Play; deleting your app account does not cancel them. For Apple sign-in, account deletion also requests revocation of Durna Ludo’s Apple authorization. Revocation runs separately and continues if new Apple sign-ins are disabled.

You can change language, media permissions, privacy-related profile settings, and optional analytics choices where offered. Applicable law may provide rights to access, correct, delete, restrict, or object to processing. Use the verified contact route shown on this site to make a request.

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.