Privacy
Privacy, in plain language.
How Durak: Cards with Friends handles game information and player support.
Last updated September 18, 2026
Who we are
Durak: Cards with Friends is published by Yevgeniy Frid. Privacy, safety, deletion and appeal requests: support@durakwithfriends.com.
Offline play and local data
Offline games, settings, statistics, deck choices, trials, purchase entitlements and conversation history are stored on your device. Queued messages and reports are saved locally before sending. We do not collect your offline game saves. Deleting the app removes local copies; restoring an Apple backup may restore them.
Apple services and purchases
Online play uses Apple Game Center for identity, invitations, matchmaking, achievements and saved matches. Players see Game Center names and game activity. If you grant Game Center friends permission, permitted identifiers, names and profile pictures help you invite friends. This does not access your device address book. Apple services may also sync supported progress. Optional premium decks are available through Apple in-app purchases, where offered; the app checks StoreKit entitlements. Apple handles payment information. Individual deck trials never charge automatically.
Public tables
If you create or join a public table, our directory temporarily stores your verified account identifier, player name, chosen rules, seat reservation, readiness and connection timing. Other signed-in players can see the host name, rules and open-seat count; seated players see the roster and readiness. Names are display labels, not proof of identity. Waiting reservations expire after 45 seconds without a heartbeat; connection reservations expire after 90 seconds. Expired records are removed on the next directory request. These records provide matchmaking and block enforcement, not advertising. Gameplay remains on Game Center.
Chat approval and safety identifiers
Typed chat is optional. Before transmission through Game Center, each new message is sent to our safety service for English/Russian rules-based filtering. We verify an Apple-signed Game Center identity, derive an account identifier and issue a signed approval bound to the author, message and match. Ordinary message text is processed transiently; we do not keep a server conversation archive or use messages for advertising or AI training. Game Center matches and participants’ devices can retain received chat. During service outages, new messages remain queued on your device while gameplay continues.
Reports, blocks and moderation
Submitting a report sends the selected message, sender name and identifiers, match and message identifiers, reason, timestamp, signature verification details, your verified account identifier and only the nearby messages you explicitly include. Older messages are labeled unverified. Evidence and moderation decisions are stored in a private database hosted through Sites and Cloudflare, accessible to the owner moderator. Blocks are linked to your account and synchronized between devices. Restrictions, removals and abuse-prevention counters support app functionality. Reports are reviewed daily, with a target response within 24 hours; this is not an emergency service. Report counts alone do not trigger bans.
Retention and deletion
Reported evidence is retained while a report is open and for 90 days after closure, then removed by the service’s cleanup process. Active restrictions and account identifiers are retained while needed for enforcement; removal fingerprints may remain to prevent deleted messages returning. Block lists remain until unblocked or deleted on request. Short-lived authentication replay records and request counters expire automatically. Ask support to access, correct or delete developer-held information; we may need to verify account ownership and retain the minimum necessary to enforce active restrictions or meet legal obligations. Local histories and report receipts remain until you remove the app. We cannot erase copies on other players’ devices; Apple-held data is managed through Apple’s privacy controls.
Launch waitlist
If you join the waitlist, we store your email address, optional first name, chosen email language, signup time, and the version of the launch-email consent you accepted. We use these details to send the launch announcement you requested. The list is stored in our hosted website database through Sites and Cloudflare, is not displayed publicly, and is not sold or shared for other companies’ marketing. We do not send an automatic confirmation email. We retain signup details until the launch announcement is complete and they are no longer needed, or until you ask us to remove them. To leave the list or request deletion, email support@durakwithfriends.com from the address you used to sign up. We also keep short-lived aggregate signup counters to limit spam; these counters contain no names, email addresses, or visitor identifiers.
Support and TestFlight
If you contact support, we receive your email address and the information you include and use it to answer, investigate and resolve your request. Support records are retained as needed to resolve requests and related obligations; you may request deletion. Do not send passwords or unnecessary sensitive information. TestFlight provides Apple-collected crash, usage and feedback information to us to diagnose beta issues.
Your choices and tracking
Play offline without our online safety service. Chat and reporting respect Game Center communication restrictions. Block or unblock players under Safety & support; blocking hides their messages and prevents new Durak tables together, while an existing table can finish with chat disabled. Leaving is separate. We do not sell personal data, track users across other companies’ apps or websites, or add advertising or analytics SDKs. The app does not request precise location, contacts, camera or microphone access. Parents can manage Apple account and communication controls or contact support.
This website
Our hosting providers process ordinary request information, such as IP addresses, to deliver and secure this website and service. The private moderation area uses Sites sign-in and a server-side owner allowlist. The public website has no added advertising or analytics scripts. We update this policy when our practices change.