Pişti Ligi

Privacy policy

Publisher: Can Avcılar

This page contains the same text as the policy the app opens at pisti.thecoveragehacker.com/privacy.html, plus sections specific to the iOS version (marked). Both addresses are valid. This English text is a translation of the Turkish original.

This policy applies to the Pişti Ligi: Yapay Zekaya Karşı app. The publisher and the person responsible for app data is Can Avcılar. Privacy requests: canavcilar77@gmail.com.

Contents
  1. Information collected and why
  2. Optional notifications and in-game announcements
  3. Ads and Google services
  4. Information specific to the iOS version
  5. Recipients and security
  6. Account deletion and retention
  7. Your requests
  8. Audience and changes

Information collected and why

  • Player and league information: player ID, nickname, avatar, league tier, points, number of matches, ranking and season history; kept to provide your game account, the leaderboard and past results. Nickname, avatar and league statistics are shown to other players on the leaderboard.
  • Match and verification records: match and request IDs, difficulty, multiplier, card deal, moves and results, status and timestamps; processed to run the game, verify results and prevent the same result from being rewarded more than once.
  • Google sign-in: for optional account linking and recovery, the account identifier verified by Google is associated with your player account. The email address Google passes as verified and the time of the last verification are stored for account management and support; they are visible only in the authorised admin panel, are not shown on the leaderboard or to other players and are not used for ad targeting. Accounts are matched by the Google account identifier, not by email. No access to Gmail messages or Drive files is requested. Your Google password is never sent to our server.
  • On-device records: the access key is kept in secure device storage; game preferences, pending match records and the ad counter are stored on the device. The server uses a hash of the access key.
  • Technical records: rate-limiting counters and diagnostic logs are used for service security and troubleshooting. The hosting provider may keep access logs.
  • Support: the contact option opens your email app. The email address, message and attachments you send are processed in the support mailbox to answer your request. Please do not send unnecessary personal information or passwords.

Optional notifications and in-game announcements

Android version

In versions that offer notifications, with your permission the phone periodically checks our own game server. Firebase Cloud Messaging is not used for this feature. Notification preferences, a random installation identifier, a server-side hash of a key that only grants notification access, and notification display acknowledgements are processed. The phone key is stored on the device in an encrypted area that is not backed up, and is separate from the game account access key.

Last app activity and last match time are used to run the service and to decide on come-back reminders. An approximate online status derived from last activity may be visible in the authorised admin panel. The background notification check does not count the player as online. Announcement IDs and display records are associated with your account so the same announcement is not repeated. You can turn notifications off in the app and in Android settings; declining does not block access to the game. Battery and network conditions may delay notifications.

Android version

On a new installation, league news and the reminder after a two-day break are selected and quiet hours are off. Selected categories do not mean you have granted Android notification permission; you confirm the permission request yourself. You can change your preferences in Settings. When quiet hours are on, no notifications are shown between 22:00 and 10:00 Türkiye time; when off, no time restriction applies. To receive notifications, the relevant category and the Android permission must both be on.

Ads and Google services

The app includes Google Mobile Ads and Google’s ad privacy choices framework. The current test distribution uses test ads. When it runs, the SDK may collect IP address (from which approximate location can be inferred), device or other identifiers, app interactions and diagnostic information for advertising, analytics and fraud prevention, and share them with Google. Using test ads does not mean that no data is processed.

Where applicable, you can manage your ad privacy choices in the app's Settings. If an ad fails to load, the game is not blocked. Advertising ID controls are in Android settings.

Google Privacy Policy · Google Mobile Ads data disclosure (Android)

Information specific to the iOS version

The following applies only to the iOS version of the app. Where the sections above describe behaviour as Android-specific, the iOS version works as described here.

Sign in with Apple

In the iOS version, Sign in with Apple can be used for optional account linking and recovery. The app-specific user identifier passed by Apple is associated with your player account; accounts are matched by this identifier, not by email. If Apple passes an email address, it may be your real address or a relay address created with Apple's “Hide My Email” option; it is stored for the same purpose as the Google email address (account management and support), is not shown on the leaderboard or to other players and is not used for ad targeting. Your Apple Account password is never sent to our server.

A verified account deletion also covers the Sign in with Apple link: when the account is deleted, the app's Sign in with Apple authorisation is revoked with Apple (token revocation). Your Apple Account is not deleted. You can also remove the app's connection under “Sign in with Apple” in your Apple Account settings.

Notifications (Apple Push Notification service)

In the iOS version, notifications are delivered through the Apple Push Notification service (APNs). When you allow notifications, the notification token Apple creates for your device is stored on our server and used only to send notifications; notifications reach your device through Apple's systems. You can turn notifications off in the app or in iOS Settings > Notifications; declining does not block access to the game. Device notification records are removed when the account is deleted.

Ad tracking permission (App Tracking Transparency)

In the iOS version, Apple's App Tracking Transparency (ATT) permission may be requested for access to the device's advertising identifier (IDFA). If you do not allow it, the advertising identifier is not given to the app or the ad SDK; ads may still be shown and the game works the same. You can change this in iOS Settings > Privacy & Security > Tracking.

Google Mobile Ads data disclosure (iOS) · Apple Privacy Policy

Recipients and security

Game data is processed through a server hosting provider; Google services are used for account verification and ad features. Support messages arrive in a Gmail mailbox. Processing by these services may involve systems outside Türkiye. Communication between the app and the server is encrypted over HTTPS. No storage or transmission method guarantees absolute security.

In the iOS version, Apple services are also used for Sign in with Apple and notification delivery.

Account deletion and retention

Request deletion of your account and related game data. You can also apply by email without installing the app. Requests are reviewed manually and completed after account ownership is verified. Uninstalling the app alone does not delete the account on the server.

Account data is kept to provide the game account and its history. A verified deletion request covers the active player record, matches, season history, points, the Google link, the stored email address, related recovery records, device notification records, and activity and announcement display records. Your Google account is not deleted. Notification job records, except records that prevent the come-back reminder from repeating, are removed by scheduled cleanup after 30 days; those repeat-prevention records are removed when the account is deleted. Admin action logs fall under a 90-day cleanup.

When the technical deletion confirmation is used, a retry record containing the access key hash and the request ID is valid for 24 hours and removed in the next hourly cleanup. This record is not anonymous.

Exact retention and cleanup periods for backups, hosting logs and support correspondence have not yet been set. Deleting the active account does not mean that all copies are deleted at the same time. No claim is made that these areas are complete or that a specific backup deletion period applies.

In the iOS version, a verified deletion also covers the Sign in with Apple link and APNs notification tokens; token revocation is sent to Apple. Your Apple Account is not deleted.

Your requests

You can write to the contact address above for information, correction or account deletion regarding your data. Ownership verification may be requested so that another player's data is not disclosed or deleted. Do not send your password, verification code or secret access key.

Audience and changes

The game is intended for users aged 18 and over; this does not mean that every user's age is verified. This page is updated when data practices change.

Last updated: 28 October 2026 (iOS sections added; base text 27 September 2026)