Privacy Policy for Spy Kurdish Game

Last updated: August 12, 2026

Spy Kurdish Game ("the app") supports offline local play and optional online multiplayer. This policy describes the data used by the current implementation and how that data is processed.

1. Family and Children Standards

• The app is designed for a broad audience, including families.
• The app does not include in-app purchases.
• The app does not include social media posting features.
• The app does not use behavioral advertising SDKs in the app code.

2. Authentication in Online Mode

• Online mode uses Appwrite authentication.
• The app creates a technical Appwrite account automatically for a device/installation when needed for online play.
• This account uses credentials derived from a device/installation identifier:
• Android: Android ID is used when available.
• iOS and Web: a generated UUID is stored locally and reused.
• Users are not asked to manually register with email/password to use online rooms.

3. Data Stored on Your Device

• Game settings, language preference, selected game mode, and gameplay preferences.
• High scores, saved game data, player stats, recent words, and recent player names.
• User profile choices used in-game (such as display profile data).
• Active online session cache for rejoin support (room and player session details).
• Device/installation identifier used for online account continuity.

4. Online Multiplayer Data (Appwrite)

When online mode is used, gameplay state is stored in Appwrite database collections. The current schema includes:

• rooms: room code, host identifiers, status/phase, round/game settings, selected categories, scoring settings, and timing values.
• players: room ID, user ID, player name, role, score, vote state, and connection/ready state.
• messages: room ID, user ID, player name, and chat message text.
• join_requests: room ID, user ID, player name, and request status.
• mafia_rooms / mafia_players (for Mafia online mode when enabled): room/player state needed to run that mode in real time.

5. Suggestion Form Data

• If you send feedback from the in-app suggestion form, the app sends: optional name, optional contact, suggestion message, submission timestamp, and basic device information.
• Suggestions are stored on our Appwrite backend so the developer can read and reply to them, and are also relayed through a Discord webhook configured by the developer for notification.
• A stored suggestion is linked to your account identifier so that a reply can be delivered back to you inside the app.

6. Diagnostics and Analytics

To find crashes and understand how the games are actually played, the app records the following on our Appwrite backend:

• Crash reports. When the app hits an unexpected error, it records the error type and message, the technical stack trace, the screen you were on, a short list of the screens you visited immediately beforehand, and your app version, platform, operating system version, and language.
• Match records. When a game starts and ends, it records which game was played, whether it was offline or online, how many players took part, your role and result, how long the match lasted, how many rounds were played, and — if the match was not finished — the point at which it stopped.
• Gameplay events. Events relating to in-game coins and rewards, such as coins earned or spent, so the developer can keep the in-game economy balanced.

These records include your account identifier so that repeated problems affecting one player can be recognised. They do not contain the contents of your chat messages, your voice audio, the words or secret numbers used in your games, your name, or your email address.

This data is visible only to the developer. It is not shared with advertisers or any analytics company, and it is not used to build advertising profiles.

7. Data We Do Not Intentionally Collect

• We do not request camera, microphone, or contacts access for gameplay.
• We do not collect precise GPS location through gameplay features.
• We do not collect payment card or bank account data.

8. How Data Is Used

• Operate core gameplay (offline and online modes).
• Create/join rooms, synchronize real-time game state, and deliver chat in online rooms.
• Maintain session continuity (for example, online rejoin support).
• Review user feedback submitted through the suggestion form, and send replies back to you in the app.
• Diagnose crashes, fix bugs, and improve game balance and design, as described in section 6.

9. Sharing and Processors

• We do not sell personal information.
• Online gameplay, diagnostics, and analytics data is processed using Appwrite infrastructure.
• Suggestion form data is processed by Discord webhook infrastructure when a user submits feedback.
• Crash and analytics data is not shared with any third-party analytics or advertising provider.

10. Retention

• Local data remains on your device until cleared by you (for example, app data reset or uninstall).
• Online room/player/message/request data is retained according to operational backend behavior and cleanup routines, and may be removed when rooms are stale or no longer needed.
• Submitted suggestions may remain in developer records and third-party service history.
• Crash reports, match records, and gameplay events are retained while they remain useful for diagnosing problems and improving the games, and are deleted when you delete your account.

11. Your Choices

• You can use offline local mode without online multiplayer.
• You can avoid sending suggestion data by not using the feedback form.
• You can remove local data by clearing app storage or uninstalling the app.
• You can request deletion of your account and its associated data, including diagnostics and match records, using the in-app account deletion option or the account deletion page.

12. Security

Reasonable technical and organizational measures are used to protect data, but no method of storage or transmission can be guaranteed 100% secure. Crash reports, match records, and suggestions are readable only by the developer's administrator account; the app itself can write these records but cannot read anyone's.

13. Changes to This Policy

This policy may be updated over time. Changes are published with a revised "Last updated" date.

14. Contact

For privacy questions, use the in-app suggestion form to contact the developer.