hunkargames · Ninja King Adventures
Privacy Policy
Here we explain what information the game and this website use, why they use it and how you can request deletion.
A quick note for families
Ninja King Adventures is a game children and families play by showing hand gestures to the camera. Camera footage and detected hand landmarks are processed on the device; they are not recorded or sent over the internet. The microphone is not used.
There are no game accounts or chat. Scores, diamonds and game progress are stored on the device. In-game advertising, online settings and Firebase notifications you choose to enable may process some technical data. Our website's support form uses an adult's email address and the message they send us. The website does not ask for age or date of birth. The home and privacy pages use limited Google Analytics measurement with analytics cookies disabled; technical requests are sent to Google. We explain these data flows separately below.
1. Camera and permissions
The camera detects hand and finger movements so you can control the game. A camera explanation is shown on first use. Android camera permission is requested after you choose to play with the camera; closing the explanation or going back does not grant permission. If permission is denied, the camera is not used and you can return to the main menu.
Camera frames and hand landmarks are processed only in device memory. No photo, video or biometric identity record is created; images and hand landmarks are not sent to hunkargames, Google AdMob or Firebase servers. The camera stops when you return to the main menu or put the app in the background.
The app does not request microphone, location, contacts, photo/storage or Bluetooth permissions. Internet access is used for ads, online settings and game notifications you choose to enable. Vibration provides gameplay feedback and can be turned off in game settings. You can change camera permission under Android Settings → Apps → Ninja King Adventures → Permissions. This website does not request camera or microphone access.
Optional game reminders
Notifications are off by default. In an Android version configured with Firebase Cloud Messaging, choosing to enable them in game settings requests your phone's notification permission and registers this installation for general game announcements. The publisher sets notification text and delivery time through Firebase; no fixed weekly alarm is scheduled on the device. Notifications are not personalized based on your camera footage, age, score or collection. Your collection is not deleted when time expires.
When you turn notifications off in game settings, the app blocks them and attempts to remove the Firebase notification registration; if offline, server-side removal may complete when the connection returns. You can also disable them in your phone's notification settings. Your notification preference is stored on the device. A local reminder preference from an earlier version does not count as permission for Firebase notifications; a new choice is required. Exact alarm permission is not requested. Service information Firebase needs to process is explained below.
2. Game information stored on your device
Scores, local best scores, diamond balance, unlocked worlds and powers, daily tasks, stickers, object counts by world, best combos and mastery stars, selected appearance, tutorial status, sound/vibration preferences and any local player nickname are stored on the device. The records screen is not a public online leaderboard.
This game information is not sent to a game server or analytics service. Clearing app data or uninstalling the app may cause local progress to be lost. Android cloud backup is disabled for the app.
3. Children's privacy and age selection
Children are included in the game's target audience. If no answer is saved, the first time you press “Play” you see two options with the same appearance: “I'm under 18” and “I'm 18 or older.” Neither option is preselected. An exact date of birth is not requested.
Your selected age range is stored only on the device, is not sent to a server and is not requested again in later games. “Not now” returns to the main menu without saving an age answer; the game does not start and the selection is requested again next time you try to play. Answers saved in an earlier version are retained; “12 or under” and “13–17” are treated as under 18.
Both age choices use the same game and child-directed, non-personalized advertising settings. Choosing the adult option does not unlock extra gameplay benefits, personalized ads or Analytics. Child-appropriate protections also apply when the player's age is unknown. Interest-based advertising and remarketing are disabled. Access to the Android advertising ID (AAID) has been removed.
The game has no account creation, direct messages, chat, social sharing profiles or exchange of personal information between players. We recommend asking an adult for help with purchases, support and privacy matters. We do not ask children to send personal information, photos or camera footage through the support form.
4. Google AdMob advertising
When ads are enabled in the game, they are served through the Google Mobile Ads SDK (AdMob). Full-screen ads are not shown during active gameplay or immediately on opening the app; they may appear between eligible game results. Rewarded ads are optional: completing one lets you continue the game with two lives. Choosing not to watch does not remove normal play or restart options. Our website does not display AdMob ads.
AdMob may process or share IP addresses and the approximate region derived from them, ad interactions, technical error and performance information, and service identifiers such as app set IDs for ad delivery, measurement and fraud prevention. Disabling the Android advertising ID does not disable all SDK data. The app does not request precise GPS location and does not share camera footage with the advertising service.
Before live ad requests, advertising privacy status is checked through Google's User Messaging Platform using child-appropriate settings. If a suitable result is not obtained, no live ads are requested. For the service's data processing and retention terms, see Google Privacy Policy and AdMob data disclosure for details.
5. Firebase settings, notifications and analytics
When Firebase is configured, Remote Config tells the app whether ads are enabled and how long to wait between them. This service uses a Firebase installation ID and technical connection data. Live ads remain disabled if there is no valid ad policy verified within the last 15 minutes; during brief connection interruptions, the last verified setting within that period may be used.
Optional Android notifications are delivered through Firebase Cloud Messaging (FCM). If you allow notifications, Google processes the Firebase installation ID, notification registration token, general notification topic subscription, app version and service/connection information to deliver notifications to the correct app installation. The notification registration token is not a game account, phone number or advertising ID. hunkargames does not store these identifiers in a separate player database. Service data may be processed on Google servers outside Türkiye.
In this version of the Android game app, Firebase Analytics, Crashlytics, cloud game-event reporting and Remote Config personalization are disabled. Limited Google Analytics measurement on the website does not change this app setting. Camera footage, hand landmarks, game scores, local nicknames and age ranges are not sent to Firebase. Processing of necessary service data cannot be fully disabled while using Remote Config.
Firebase may retain the installation ID until an explicit deletion request is made. Turning notifications off starts removal of the notification registration token; it does not automatically delete the installation ID used by Remote Config or all Google service records. After the installation ID deletion API is used, removal of associated data from live and backup systems may take up to 180 days. Details are on the Firebase Privacy and Security page.
6. Purchases
Real-money purchases are handled through Google Play Billing. The app does not ask for credit card numbers, bank details or Google account passwords. Google Play may provide the app with product IDs, transaction/payment status and purchase ownership information to verify purchases and unlock content.
In this version, no payments are taken for diamond packs while they are being prepared. Diamonds can be earned by playing. The ad-free product can be purchased when available on Google Play and restored using the same Google Play account. Payment records are subject to Google Play's retention and refund terms; clearing app data does not delete these records.
The website does not collect payment or card details. Ask an adult for help with purchases. For refunds, contact Google Play refund support for assistance.
7. Website and contact form
The contact form is for adults' support, partnership or privacy requests. It collects your email address and message so we can reply. Choosing a subject is optional. There are no fields for a name, phone number, date of birth, file attachment or photo. When describing a game issue, you may include technical details such as device model, Android version and app version in your message; we do not collect these automatically from your device.
Please do not include children's names, schools, contact details, photos or camera footage, passwords or payment information in your message. For child players, we ask a parent or another adult to write using their own email address.
Your message and email address are sent through the configured SMTP/email provider to our [email protected] support inbox so we can reply and resolve your request. Message content, email address and any technical details you provide are processed by hunkargames and the email service used for delivery/storage. The form application does not additionally store them in a database, server file, session or application log.
We use this data to handle the contact request you initiated. Limited technical processing for site security aims to prevent abuse and operate the service securely; relevant records may also be used when necessary to fulfill legal obligations or protect rights. Submitting the form does not grant marketing permission. Support emails are not used to build advertising profiles or send newsletters.
8. Visit measurement, cookies and security logs
Google Analytics for the website
Google Analytics 4 (measurement ID: G-B1C45M6J65) loads automatically on the home and privacy pages to understand website use and improve the site. Analytics cookie storage, advertising storage, advertising user data and ad personalization remain disabled: analytics_storage, ad_storage, ad_user_data and ad_personalization are set to “denied.” In this configuration, limited measurement requests are sent to Google without analytics cookies. The website does not display a new age question or measurement permission screen and does not create a new preference record.
Limited technical information such as page views, time and browser/device characteristics may be sent to Google. Google may also process the IP address when connecting. Page URL query parameters and the part after the fragment marker are excluded from measurement; the referrer is limited to the site origin. The absence of cookies does not mean no data is sent to Google or that data is fully anonymous. Google may process service data on servers outside Türkiye.
Google Analytics code does not load on the contact page. Form interactions, email addresses, support messages, children's personal information and in-game data are not sent to Google Analytics. Google Signals and ad personalization are disabled; web measurement is not used for remarketing. User and session reports may be limited with cookieless measurement; we do not promise full reporting or modeling results.
If you declined measurement in an earlier version of the site, the refusal saved in your browser is respected: while it remains, Google's measurement code is not loaded and no measurement requests are sent. No new expiry is applied to this old record; clearing the site's browser data removes it. A previous permission record does not enable analytics cookies. Old Google Analytics cookies accessible to the site are cleared. The website does not collect age answers or dates of birth or send them to Google.
Retention and deletion on Google servers depend on the service terms and Analytics account settings. Clearing browser data does not automatically delete data previously sent to Google. For privacy requests, use the contact section below. How Google handles data: How Google uses information from sites or apps that use its services and Google Privacy Policy.
Contact form and website security
Opening the contact page may use a session cookie needed for form security. It supports the CSRF check that prevents other sites submitting the form on your behalf and displays submission results; it is not used for advertising. Email addresses and messages are not written to the session. The cookie uses HttpOnly and SameSite protections, the Secure setting over HTTPS, and lasts for the browser session.
To limit form abuse, the application retains limited security information such as an HMAC identifier generated from the IP address with a secret key, time and a request counter. The raw IP address is not written to these protection files. Records are evaluated over a 24-hour period; expired records are cleared automatically during the next form operation. If there is no further form operation, expired files may remain until cleanup occurs. Using HMAC does not make this data fully anonymous.
Separately, the hosting service's standard access and error logs may include connection data such as IP address, requested page, time and browser details. The hosting service may process these to deliver the site, fix errors and maintain security. Retention of the provider's operational logs depends on its service terms and server settings; these differ from the form's 24-hour security records.
9. Retention, security and deletion
Local game data stays on your device until deleted. You can delete it by clearing data in Android app settings. This does not delete Google Play purchase records or immediately remove service providers' records. Because camera frames and hand landmarks are not stored permanently, there is no image archive to delete.
We delete support correspondence from our support inbox no later than 90 days after your request is closed. If retention is needed for a legal obligation, ongoing dispute or protection of rights, only the relevant records are kept for the necessary period. The email provider's delivery logs and backups are separately subject to its retention and deletion terms.
Form security records are evaluated over a 24-hour period, and expired records are cleared during the next form operation. Retention and deletion of hosting, Google AdMob, Firebase and Google Play records depend on the respective services' terms. Uninstalling the app or clearing browser data does not automatically delete these service records immediately.
The website does not create new analytics cookies or measurement preference records. A refusal record left from an earlier version keeps measurement fully disabled until this site's data is cleared in the browser. Data retention on Google Analytics servers is determined by the Analytics property's account settings and Google's service terms; not using cookies does not mean the service's server records have been deleted.
Online communications use encrypted connections such as HTTPS/TLS. Access to the support inbox and website administration is limited to people needed to address your request and operate the service. Camera footage and local game progress are not sold; your support information is not used for advertising.
10. Privacy requests and contact
Publisher and privacy contact: hunkargames. For information about your data or to request correction, access or deletion, write to [email protected]. If possible, send your support request from the email address you originally used. We may ask only for additional information necessary to handle your request securely; we do not ask for camera footage or children's personal information.
Because the game has no account creation, there is no separate game account to delete. We cannot remotely access your device's scores or diamonds. To delete local progress, use your device's app settings. Parents can submit requests relating to their children using their own contact details.
Other services' data terms: Google Privacy Policy, Firebase Privacy and Security and AdMob data disclosure.
11. Policy changes
This policy and related explanations are updated when the game's or website's data practices change. Significant changes are announced within the app where necessary, and required choices are requested again. The date at the top of the page shows the latest update.
English privacy summary
Ninja King Adventures and hunkargames
Publisher: hunkargames. Contact: [email protected]. Updated October 4, 2026. Android package: com.hunkargames.ninjaking.fruitslice.
Optional notifications are off by default. In a configured Android release, enabling them in game settings requests notification permission and registers this installation with Firebase Cloud Messaging (FCM) for general game announcements. The publisher sets messages and timing through Firebase; no fixed weekly alarm is scheduled on your device. Notifications are not personalized using camera images, age, score or collection progress. Collections do not expire.
Turning notifications off blocks their display and attempts to unsubscribe and delete the messaging registration; offline cleanup is retried when a connection is available. You can also disable notifications in your phone's settings. Your preference stays on the device. A previous local-reminder preference does not count as consent to remote notifications. No exact-alarm permission is requested.
The game's camera processes hand movements on your device. Camera frames and hand landmarks are not recorded, uploaded or shared with advertising or Firebase. The microphone is not used. A camera explanation precedes permission; closing it is not consent. The camera stops on the home menu or when the app goes into the background. This website does not request camera or microphone access.
Scores, diamonds, unlocked items, settings and your age answer stay on the device. If no answer is saved, the first tap on Play asks you to choose under 18 or 18 or older, with neither choice preselected. Not now returns to the menu without saving an age answer or starting the game. Saved answers are remembered; earlier child and teen answers are treated as under 18. No date of birth is requested. Both choices and users of unknown age receive child-directed, non-personalized ad settings. Choosing an adult age gives no gameplay benefit and does not enable personalized ads or Analytics. Android advertising ID access is removed. There are no game accounts, chat or public profiles.
When enabled in the game, Google AdMob may process IP address and approximate region, ad interactions, diagnostics and service identifiers for advertising, measurement and fraud prevention. Removing advertising ID access does not remove all SDK data processing. Optional rewarded ads grant two lives after completion. Website visitors do not see AdMob ads.
When configured, Firebase Remote Config uses a Firebase installation ID and connection data for ad settings. Opt-in FCM notifications use installation and messaging registration identifiers, the general topic subscription, app version and service/connection information processed by Google to deliver messages. A messaging identifier is not an account, phone number or advertising ID. hunkargames does not store these identifiers in a separate player database. Service data may be processed outside Türkiye.
Firebase Analytics, Crashlytics, cloud game-event reporting and Remote Config personalization are disabled in this release. Turning notifications off starts deleting the messaging registration, without automatically erasing the installation ID used by Remote Config or all Google service records. Firebase may retain installation IDs until explicitly deleted; deletion from live and backup systems can take up to 180 days after its deletion API is used.
Payments use Google Play Billing; the game and website do not request card details or passwords. Diamond pack payments are disabled while their delivery flow is being prepared. Diamonds can still be earned through play. Available ad-free purchases can be restored with the same Google Play account.
The adult contact form sends your email, message and optional topic through the configured SMTP/email provider to our support mailbox. You may voluntarily include device, Android or app version information in your message. Do not include children's personal details, photos, camera recordings, passwords or payment information. The form does not store email or message content in a database, server file, session or application log. We use correspondence to respond to your request, not for marketing.
Website Google Analytics 4 (measurement ID G-B1C45M6J65) loads automatically on the home and privacy pages, separately from the game's disabled Analytics. The analytics_storage, ad_storage, ad_user_data and ad_personalization states remain “denied”. Limited cookieless measurement requests are sent to Google. The website does not ask your age or date of birth, display a new measurement permission prompt or store a new preference. Google Signals and ad personalization remain disabled.
Limited page-view and technical information, such as timestamps and browser/device details, may be sent to Google. Google may process the connection IP address, including on servers outside Türkiye. Cookieless does not mean no data transfer or complete anonymity. Page URLs exclude query parameters and fragments; referrers are limited to their origin. The contact page never loads Analytics. Contact form interactions, email addresses, messages, children's personal details and game data are not sent to website Analytics. User/session reports may be limited; complete reporting or modeling is not guaranteed.
A refusal saved by the previous site version remains a complete opt-out while its local record exists: no Google measurement library or request is loaded. It no longer has a time limit; clearing this site's browser data removes it. A previous permission record does not enable Analytics cookies. Old Analytics cookies accessible to this site are cleared. Google's server-side retention depends on the Analytics property's settings and Google's terms. Clearing browser data does not automatically delete previously transmitted data. Contact us for privacy requests. See How Google uses information from sites or apps that use its services and Google's Privacy Policy.
The contact page uses an essential session cookie for CSRF protection and submission results. Form abuse protection uses a keyed HMAC of the IP address and limited time/counter metadata within a 24-hour validity period. Expired records are cleaned up during the next form operation; if there is no new operation, expired files may remain until cleanup. Hosting access/error logs may separately contain IP addresses and connection data; their retention depends on the hosting service and server settings.
We delete support correspondence from our mailbox within 90 days after closing the request, unless legal obligations or an ongoing dispute require relevant records to be kept longer. Provider delivery logs and backups follow the provider's rules. Clear the Android app's data to delete local progress; doing so does not erase Google Play purchases or immediately erase provider records. There is no separate game account to delete. Contact us for privacy, access, correction or deletion requests.