Last updated and effective: 22 July 2026
Data controller: Cengizhan Recep ÇEKMEZ (Ceng Games)
Contact: playcenggames@gmail.com
Address: Cevizli Neighborhood, Zühal Avenue, A Commercial Block Building, No. 46/50, Maltepe, Istanbul, Türkiye
Web: https://www.cenggames.com
This policy explains how personal data is processed in the BilHece mobile application and the BilHece-specific privacy and account-deletion pages. It is a privacy notice, not blanket consent. Optional analytics, advertising/tracking, and notification choices are presented separately before the relevant processing. Refusing an optional choice does not block access to the core game.
1. How BilHece works
BilHece combines on-device word and knowledge content with online accounts, progress synchronization, ranking, friends, Duels, notifications, advertising, and in-app purchases.
On first launch, an anonymous account with a random Firebase user ID (UID) may be created to separate the core game and progress between users. The user can later link the account to Google or Apple. Email, display name, and provider ID may be received if supplied by the provider.
2. Data we may process
The data depends on the feature used, whether the account is linked, the device, region, and user choices:
- Account: Firebase UID, including for an anonymous account; email, display name, and Google/Apple provider ID when provided for a linked account.
- Profile and social: Unique public player name and player-name search query; avatar, frame, level, rating, rank, and Plus indicator; friends, requests, blocks, invitations, preset Duel messages, online visibility, connection state, and last-online time. Player reports may include reporter/target IDs, a fixed reason, relevant public-profile snapshot, review status, and timestamps.
- Gameplay and progress: Correct/incorrect summary, score, category or mode, duration, hints and skips, completed content, XP, level, streak, active days, quests, Coin movements, inventory, achievements, and advanced statistics. Question/answer inputs are processed for scoring; persistent records generally contain results, scores, and time summaries.
- Duels and ranking: Matches, participants, run summaries, results, rating changes, leaderboard, and anti-abuse records.
- Purchases and subscriptions: RevenueCat app-user ID based on Firebase UID; a random RevenueCat identity that may exist during session transitions; product/package, store transaction and receipt information, purchase, subscription, restoration, cancellation/refund, verification, and BilHece Plus or Ad-Free entitlement state. Ceng Games and RevenueCat do not receive the full card number or store password.
- Advertising: Placement, impression, interaction, and reward; rewarded-ad session/transaction ID and fraud signals; depending on region and permission, IP address, approximate location, device/app information, advertising/device identifier, and advertising privacy choice.
- Analytics: Only while Usage Analytics is separately enabled: screens and feature interactions, app-instance/session ID, approximate device/app information, and campaign attribution. BilHece does not send the Firebase Auth UID or email as a Firebase Analytics user ID.
- Notifications: Random installation ID, FCM/APNs token, platform, UID association, notification-category choices, relevant player’s public name, content such as an invitation or preset message, update time, and delivery/interaction signal.
- Technical and security: App version, operating system, language/time zone, approximate region inferred from IP, request/server logs, Firebase App Check token, Google Play Integrity, and Apple App Attest/DeviceCheck signals.
- On-device: Theme, sound, haptics, and privacy settings; Analytics-choice text version and change time; seen questions, offline progress, tutorial state, and content cache.
- Support and rights requests: Email, message, optional attachment, request type, and limited verification information needed to protect the account.
- Web page: When cenggames.com is visited, Google Firebase Hosting may process the IP address, requested URL, request time, browser/device information, and technical request/log data to serve static pages through HTTPS/CDN and support availability, security, and abuse prevention. The first website version has no analytics or marketing tag, form, chat, or newsletter.
BilHece does not request camera, microphone, contacts, photo-library, sensitive-health, or precise-GPS permission.
3. Purposes and legal bases
As applicable, processing relies on Article 5 of Türkiye’s KVKK, Article 6 of the GDPR in the EEA and UK GDPR in the United Kingdom, and appropriate bases under other mandatory local laws:
- Operating the account, progress, synchronization, social features, rankings, and game: entering into/performance of a contract, the user request, and legitimate interests in secure operation.
- Authentication, App Check, cheating, fraud, abuse, and security controls: legal duty, establishment/exercise/protection of a right, and legitimate interests.
- Player reports and moderation: safe community operation, the user request, protection of a right, and legitimate interests.
- Purchases, subscriptions, refunds, and mandatory records: performance of a contract, legal duty, and establishment/exercise/protection of a right.
- Notifications: the user request and separate consent where required.
- Firebase Analytics: only a separate, freely given Usage Analytics choice/consent.
- Advertising personalization and tracking: separate valid consent and iOS ATT permission where required. Another applicable legal basis may apply to eligible non-personalized/limited ads and reward/fraud controls.
When legitimate interests are used, necessity, proportionality, and the possible impact on user rights are assessed.
4. Profile, social features, and automated rules
Player name, avatar/frame, level, rating, rank, and some Plus indicators may be visible to other players. Email is not shown to them. BilHece has no free-text chat; do not place a phone number, email, address, or sensitive information in a player name.
Scoring, matchmaking, reward limits, and anti-cheat controls may use automated rules. They are not designed to produce legal or similarly significant decisions.
5. Analytics choices
Firebase Analytics is off by default and operates only while the separately presented Usage Analytics choice is enabled. This choice is independent of UMP advertising choices and iOS ATT permission.
Personal gameplay and advanced performance statistics shown in the profile are not Firebase Analytics and are separate from the Usage Analytics choice in Settings. They accumulate for the anonymous or linked account to provide game progress and related account features, both while BilHece Plus is active and while it is inactive. Plus unlocks the detailed view; if you subscribe later, eligible gameplay summaries accumulated before membership may also appear. The detailed view may close when membership ends, but gameplay statistics continue to accumulate while the account remains active.
Disabling Usage Analytics in Settings stops future collection and resets the on-device Analytics app-instance identity. Historical Analytics events may not be individually retrievable through an account identity because they are not associated with Firebase Auth UID. A deletion request is assessed where an applicable identifier and legal right exist; BilHece does not create a new UID-to-Analytics-identity map solely for that purpose.
6. Advertising, UMP, and iOS ATT
BilHece may show native and optional rewarded ads through Google Mobile Ads/AdMob. An ad request is made only when Google User Messaging Platform (UMP) canRequestAds() permits it. In applicable regions, UMP presents advertising and data-use choices. Where required, these choices can be changed prospectively through Settings > Advertising Privacy Options.
A UMP choice is not Apple App Tracking Transparency (ATT) permission. On iOS, if ad targeting or measurement links data with other companies’ apps or websites, Apple’s system permission is shown before tracking or access to the advertising identifier. Personalized advertising is used only when the applicable UMP choice, local legal requirements, and ATT status all permit it.
If ATT is denied, restricted, not determined/unavailable, or the UMP choice does not allow personalization, BilHece does not access the advertising identifier or perform ATT-covered tracking. If UMP permits an ad request, an eligible non-personalized or limited ad may be requested instead; otherwise no ad is requested. These choices do not block the core game. ATT can be changed prospectively in iOS Settings.
Non-personalized ads do not target based on past behavior, but IP, device/app information, and other permitted signals may still be processed for contextual advertising, frequency capping, aggregate measurement, delivery, and fraud prevention. Limited ads disable personalization and features requiring a local identifier. Ad availability is not guaranteed.
We do not sell personal data for money. Certain advertising transfers may be defined under applicable local law as a “sale,” “sharing,” or “targeted advertising”; an applicable opt-out control is provided where required.
The mobile app does not directly read browser-specific DNT or GPC signals. The first version of cenggames.com has no analytics or marketing tag, form, chat, or newsletter and is served as a static site through Google Firebase Hosting. The technical hosting layer’s handling of browser-specific signals depends on Google/Firebase configuration. If a new site tool is added later, this policy and any choices required by applicable law will be updated.
7. Notifications
Notification registration occurs only when the BilHece explanation and master notification choice, operating-system permission, and session state all permit it. Daily, friends/Duel, and new-content notifications can be managed separately in the app.
Notifications can be disabled in BilHece Settings or operating-system settings. Turning off the master choice detaches the installation record and attempts to invalidate the token. Delivery previously accepted but delayed by the operating system cannot be fully recalled.
8. In-app purchases
Apple App Store or Google Play processes payments. UID, product/transaction, and entitlement state are shared with RevenueCat for verification, restoration, refunds, and cross-device synchronization.
Deleting a BilHece account does not automatically cancel an active store subscription. To stop renewal, separately cancel it in App Store or Google Play subscription management. Cancellation is not a precondition to submitting an account-deletion request.
9. Recipients and providers
Data may be shared only as needed for the relevant purpose with:
- Google Firebase: Core, Authentication, Firestore, Realtime Database, Functions, Analytics (only with the user’s choice), Messaging, Installations, and App Check.
- Google Mobile Ads/AdMob and UMP: Ad delivery, privacy choices, measurement, and fraud prevention.
- RevenueCat: Products, receipt/subscription validation, entitlements, refunds, restoration, and provider-side completion of customer-record deletion.
- Apple and Google Play: Distribution, platform sign-in, payments/subscriptions, APNs delivery, Apple App Attest/DeviceCheck, Google Play Integrity, and store security.
- Google Firebase Hosting: Serving static pages on cenggames.com through HTTPS/CDN and supporting availability, security, and abuse prevention.
- Competent authorities and advisers: Where legally required or needed to establish, exercise, or protect rights.
Providers’ own terms and privacy notices may also apply to their independent processing.
10. International transfers
Google/Firebase, AdMob, RevenueCat, and Apple infrastructure may process data outside Türkiye, including in the EEA, United States, or another provider country.
Applicable KVKK international-transfer requirements and, where relevant, GDPR/UK GDPR transfer requirements are assessed separately for each data flow. A transfer is not made unless the required adequacy decision, standard clauses, binding corporate rules, or another valid safeguard is in place; otherwise the relevant processing or market is not offered. Using the app is not, by itself, explicit consent to international transfers. Contact us for information about the applicable mechanism.
11. Retention
Data is retained for the shortest time needed for the purpose and applicable legal duties. Current principal periods and criteria are:
- Linked-account, profile, progress, economy, and social data are retained while the account is active and are deleted or anonymized upon deletion, subject to the limited exceptions below. An anonymous/guest account that has not been linked to Google/Apple is automatically deleted with its progress after 180 days without verifiable server or Firebase Authentication activity. This is permanent; keeping the app offline may not create server activity. Users who need long-term progress retention can link the account.
- Only the latest 62 calendar days of daily aggregate gameplay summaries are used for period performance comparisons. Older daily summaries are deleted on the account’s next relevant gameplay/data update; all-time performance totals remain part of account progress while the account is active.
- Weekly leaderboard rows are retained for up to 60 days and monthly rows for up to 180 days. An all-time ranked row remains while the account is active and is removed on account deletion. A former player-name reservation remains for about 30 days after a change and is then deleted.
- Terminated Duel records are retained for up to 60 days. On account deletion, public player information is replaced with a random “Deleted Player” identity; a restricted internal participant record may remain only for the remaining period to preserve result integrity.
- Stale notification tokens are retained for about 60 days; notification tombstones that prevent a delayed request from restoring an old choice are retained for about 30 days.
- Rewarded-ad session/reward records are retained for about 30 days; top-level AdMob SSV transaction records for up to 90 days for verification and fraud review.
- Player reports are retained for up to 180 days from acceptance; report-rate-limit records for about 48 hours.
- Certain game-security audit records may be retained for up to 60 days; deduplication and client-operation records for up to 180 days.
- Purchase and receipt records may be retained for verification, preventing duplicate entitlement/Coin grants, refund/dispute handling, and mandatory financial or legal periods. On deletion, owner UID is removed from the purchase anti-replay claim; a one-way transaction key and minimal fraud state may remain as long as needed to prevent reuse of the same transaction.
- A RevenueCat customer-deletion job remains for safe retry until provider deletion succeeds and is then removed.
- Analytics is not linked to Firebase UID and is retained only while separately enabled for the verified retention setting in the Firebase/Google Analytics property. Aggregate reports or events that cannot be linked to a particular account may remain after account deletion.
- Local app data may remain until clearing, uninstalling, or relevant account deletion.
- Limited residual copies in technical logs or backups may remain with restricted access until the provider’s configured ordinary overwrite/backup lifecycle or a mandatory legal period ends and are not used for another purpose.
12. Account and data deletion
In the app, use Profile > My Account (or Save Progress for an anonymous account) > Delete Account. A Google- or Apple-linked account requires reauthentication. For an Apple-linked account, revoking the Apple authorization is also part of the deletion flow.
If the app is unavailable, use the BilHece Account Deletion page or email playcenggames@gmail.com with the subject “BilHece Account Deletion Request.” Never send a password, one-time code, access token, full identity-document copy, full card data, or full receipt. Proportionate verification may be requested to protect the account.
Deletion covers the Firebase account, profile, progress, social links, Coins, inventory, notification registration, and linkable game data other than the mandatory/limited records described above. RevenueCat customer-record deletion is started through a durable server job and retried after temporary provider failures. An active store subscription must be separately cancelled in the store.
Requests are answered within applicable legal periods. KVKK requests are generally resolved within 30 days; where GDPR/UK GDPR applies, generally within one month. If complexity, verification, or a lawful extension applies, the user is informed under the applicable rule.
13. Your rights
Article 11 of the KVKK provides rights to learn whether personal data is processed and obtain information; learn purposes and recipients; request correction and, where conditions apply, erasure/destruction and recipient notification; object to an adverse result based exclusively on automated analysis; and seek compensation for unlawful processing.
Where the GDPR, UK GDPR, LGPD, or applicable U.S. state law applies, additional rights may include access, correction, erasure, restriction, portability, objection, consent withdrawal, opting out of sale/sharing/targeted advertising, appeal, and complaint to a competent supervisory authority.
Send requests to playcenggames@gmail.com. Proportionate verification may be requested to protect the account and other users’ data. Users are not discriminated against for exercising privacy rights.
14. Children’s privacy
BilHece is a word and knowledge game designed for a general audience. Although its content is intended to be suitable for a broad range of ages, it is not designed, marketed, or advertised specifically for children. A child being able to find or use the app does not make children the target audience. Store listings and advertising campaigns are not directed specifically to children, primary-school students, or a particular child age group; child age groups are not selected as the Google Play target audience, and Apple Kids Category is not used.
The current release does not request date of birth, independently verify age, or use child/teen/adult modes. UMP is not an age-verification or parental-consent mechanism. The store content rating is determined separately from the marketing audience through truthful answers about actual content and features.
A parent or legal guardian who believes data relating to a child has been processed contrary to applicable law may contact us. Where review determines that action is legally required, reasonable steps are taken to erase the data or restrict processing. If BilHece later changes to target children, the policy, technical controls, advertising behavior, and store disclosures will be updated before release of that change.
15. Security
Measures include encryption in transit, access controls, server-side authorization, Firebase App Check, rate limits, and transaction deduplication. No electronic method is completely secure, so absolute security cannot be guaranteed.
16. Changes and contact
This policy and its effective date are updated when features, providers, or law change. A material change may be accompanied by an in-app notice or renewed separate choice where required.
For a privacy question, rights request, or complaint:
Cengizhan Recep ÇEKMEZ (Ceng Games)
Email: playcenggames@gmail.com
Address: Cevizli Neighborhood, Zühal Avenue, A Commercial Block Building, No. 46/50, Maltepe, Istanbul, Türkiye
Web: https://www.cenggames.com