Privacy Policy
This Privacy Policy explains what information Nub Games collects when you use our website or our mobile applications, and how we use it. Using the service means you agree to this policy.
Scope
"Nub Games" refers to (a) the website at nub.games and its localized variants, and (b) the official Nub Games mobile applications distributed via Google Play, RuStore and Huawei AppGallery. The mobile data-handling sections below apply only to the apps; the cookie and analytics paragraphs further down apply to the website.
Information We Collect (Mobile App)
Our mobile applications may collect the following categories of data:
| Category | Type | Purpose |
|---|---|---|
| Anonymous user ID (UUID) | Hex string generated on the device | Recommendations, push notifications |
| Device ID / Android ID | System identifier | Advertising, anti-fraud |
| AppMetrica device ID | UUID generated by Yandex AppMetrica SDK | Mobile analytics, attribution, push targeting |
| IP address | Network metadata | Geo-detection, fraud prevention, analytics |
| Approximate location (city) | Derived from IP | Advertising targeting |
| App interactions | Events: game_play_start, search, tap | Analytics, feature improvement |
| Search history (in-app) | Search query strings | Search personalization |
| Crash logs | Stack traces, device model, OS version | Diagnostics |
| Push token (FCM / HMS / RuStore Push) | Platform-issued identifier | Sending notifications |
Information We Collect (Website)
The website does not require registration. It stores your recently-played games in your browser's localStorage so you can return to them quickly - that data never leaves your device. Our hosting and analytics providers may automatically record standard log data (IP, browser type, pages visited) to operate the site and detect abuse.
Mintegral Campaign Measurement
For eligible paid visits from Mintegral, the browser sends Nub Games a first-party session record only while website analytics is allowed. The record contains an anonymous browser session ID, campaign ID, source key, offer ID, creative ID, numeric VID, the server-resolved game, and server-recorded times for session start, confirmed game visibility, 60 seconds of visible play and 180 seconds of visible play. We use these fields to measure campaign quality. We do not store the landing URL, referrer, IP address, user-agent, Mintegral click ID or device identifier in this record. We intend to retain these records for no more than 90 days. Automated deletion is not implemented yet, so 90 days is the retention target and not a claim that records are already deleted automatically. In addition, after a paid visit the browser keeps the last set of campaign identifiers (campaign, source, offer, creative, VID) in localStorage for 7 days. If you come back within that period without an ad link and start a game, a separate record marked as a return visit links that start to the same campaign. This record contains no personal data, never leaves your device except as part of the record described above, stops being used after 7 days and is removed the next time you open the site.
Third-Party SDKs
Our mobile applications integrate the following third-party SDKs. Each is listed by name (Google requires explicit named disclosure rather than a generic "advertising partners" reference):
| SDK | Purpose | Data categories |
|---|---|---|
| Google AdMob | Advertising, analytics | User IDs, Device IDs, App activity, Approximate location |
| AppLovin MAX | Advertising: ad mediation in the Google Play app | Device IDs, App activity, Approximate location |
| Yandex Mobile Ads | Advertising | User IDs, Device IDs, Approximate location |
| Unity Ads | Advertising through AppLovin MAX mediation (Google Play app) | Device IDs, App activity, Approximate location |
| InMobi | Advertising through AppLovin MAX mediation (Google Play app) | Device IDs, App activity, Approximate location |
| Liftoff Monetize (Vungle) | Advertising through AppLovin MAX mediation (Google Play app) | Device IDs, App activity, Approximate location |
| Pangle | Advertising through AppLovin MAX mediation (Google Play app) | Device IDs, App activity, Approximate location |
| Meta Audience Network | Advertising through AppLovin MAX mediation (Google Play app) | Device IDs, App activity, Approximate location |
| Firebase Analytics (Google Play Android app) | App analytics and ad revenue measurement | App instance identifiers, app interaction events, ad impression data; advertising ID collection disabled |
| Tenjin (Google Play Android app) | App analytics and ad revenue measurement | App or installation identifiers, device and network information, app event names and ad impression data |
| Yandex AppMetrica | Mobile analytics, push delivery (gms build, AppMetrica Push) | AppMetrica device ID, App activity, App version, Locale, Approximate location |
| Firebase Cloud Messaging (FCM) | Push transport (used by AppMetrica Push on the gms build, and by direct backend pushes) | Push tokens |
| Huawei Push Kit (HMS) | Push notifications (huawei build) | Push tokens |
| RuStore Universal Push | Push notifications (rustore build) | Push tokens |
| Sentry | Crash reporting, diagnostics | Crash logs, device info |
On the website, games are embedded from Yandex Games / PlayHop. When you play an embedded game, the provider may collect data according to its own policy - we do not control that data.
Analytics and Notifications in the Google Play App
In the Google Play Android app, Firebase Analytics and Tenjin are used to understand app use and measure advertising revenue. The app is configured to send Firebase Analytics selected app interaction events and ad impression information, including the value of an impression. It is configured to send Tenjin selected event names and ad impression information, including the network, ad format, placement and revenue. These services may process app or installation identifiers, device information and network information such as IP address.
The app enables these analytics services after you accept its data-processing choice. Firebase Analytics advertising ID collection is disabled. Tenjin is configured to withhold the advertising ID unless you have accepted app analytics and the relevant advertising purposes are explicitly allowed. If analytics consent is withdrawn, the app disables Firebase Analytics, requests a reset of its analytics data and stops the Tenjin process. This does not guarantee cancellation of requests already in progress or deletion of data already received by a provider.
If you accept the app data-processing choice, choose to receive notifications and allow them in Android, Firebase Cloud Messaging can issue a push token. The app sends that token to our server with the app user and device identifiers, platform, store, app version, locale and country, to deliver notifications. Turning notifications off disables automatic FCM token initialization and requests token deletion from Firebase. It does not by itself remove the previously registered device record from our server.
Resetting analytics or deleting a push token does not necessarily delete a Firebase installation identifier. Google, Tenjin and other SDK providers may retain data they received under their own policies. Contact us about a request involving data held by these providers.
Advertising in the Google Play App
Starting with version 1.1.0, the Google Play version of our Android app shows ads selected through the AppLovin MAX mediation platform and the advertising partners listed below. This section applies only to that version of the app. Games in the app are embedded from Yandex Games / Playhop and may show their own ads under the provider's rules; the app's consent form below does not apply to them.
AppLovin and these partners may receive the device advertising identifier (Google Advertising ID), IP address, device information (such as model, operating system and language) and information about interactions with ads (such as impressions, clicks and video views). They may use this information to show and personalize ads, measure ad performance and prevent fraud, subject to your privacy choices and applicable law.
The Unity Ads SDK disclosure lists user identifiers as data the SDK collects and shares for app functionality, and purchase history as data it collects and shares for advertising and analytics. The game's analytics setting does not control all collection by advertising SDKs.
In the EEA, the UK and Switzerland the app asks for your advertising consent with the Google UMP (User Messaging Platform) form before it starts AppLovin MAX. You can review or change your choice at any time in the app settings under "Privacy settings". In US states whose privacy laws treat targeted advertising as a "sale" or "sharing" of personal information, you can opt out by deleting your advertising ID in your device settings (Settings > Privacy > Ads > Delete advertising ID; on older Android versions, Opt out of Ads Personalization).
We do not store the advertising ID on our servers. AppLovin and each partner keeps this data for the periods set out in its own policy and describes there how it processes data:
Account & Data Deletion
You can request deletion of all data tied to your installation in two ways - both are mandatory under Google Play's account-deletion policy:
- Inside the mobile app: Profile → "Delete account".
- Via the web form at https://nub.games/account/delete - usable without login, for users who have already uninstalled the app or lost access.
When we can match the identifiers and process a deletion request, our server clears registered push tokens and deletes matching mobile event records. We retain a record of the request containing the identifiers used to process it. This does not automatically delete data held by Firebase, Tenjin or other providers. Contact us about data held by those providers.
GDPR Rights (EEA / UK)
If you reside in the European Economic Area or the United Kingdom, the GDPR / UK GDPR grants you the following rights with respect to your personal data:
- Right of access - request a copy of the data we hold about you
- Right to rectification - correct inaccurate or incomplete data
- Right to erasure ("right to be forgotten") - request deletion
- Right to data portability - receive your data in a machine-readable format
- Right to object - object to processing for direct marketing or legitimate-interest grounds
- Right to restrict processing - limit how we use your data while a dispute is resolved
To exercise any of these rights, contact maxdev@appyapp.org. We will respond within one month. Operator details are listed on the Imprint page.
Cookies
We and our partners use cookies and similar browser storage on the website. Who sets them and why:
- Yandex Metrica (analytics). Counts visits, clicks and page speed so we can see what works on the site. Its cookies are set by Yandex. Where it waits for your consent, and where it does not load, is described in the next section.
- Google AdSense (advertising, shown to most visitors outside Russia). Third-party vendors, including Google, use cookies to serve ads based on your prior visits to this website or other websites, to measure ads and to limit how often you see the same ad. In the EEA, the UK and Switzerland Google shows personalized ads only with your consent, which Google asks for in its own message. There are no Google ads on kids pages.
- Yandex Advertising Network (advertising, shown to most visitors in Russia). Yandex uses cookies to show and measure ads.
- Meta Pixel (ad measurement). Loads only for people who came to the site from a Meta ad (Facebook, Instagram), for 7 days after that visit. It tells Meta about page views and game starts (start, game loaded, one minute of play) so we can see which ads bring players and pay less for them. Meta sets its own cookies (_fbp, _fbc). It does not load in the EEA, the UK and Switzerland, and it switches off if you decline in the site's cookie banner.
- Our own browser storage. localStorage keeps your recently played games, your cookie choice, a marker that you arrived from a Yandex ad (it decides which ad network the site uses for you) and the campaign markers described above. It does not leave your device except as described in this policy.
You can turn off personalized Google ads in Google Ads Settings and read how Google uses information from sites that use its services. Yandex Metrica can be blocked with the official Yandex opt-out browser add-on. If you chose "Opt out" in our cookie banner, Yandex ads are switched off at once, Yandex Metrica stops loading from the next page load, and Google ads, where shown, are requested as non-personalized. You can also delete or block cookies in your browser settings.
Cookies in embedded game iframes are governed by the game provider's own policy.
Ads, Analytics and Consent by Region
Which ads you see is decided in your browser, mainly from your device's time zone. We do not look up your IP address for this.
- Yandex ads. Visitors in Russia, and visitors who came to the site from a Yandex ad, see ads from the Yandex Advertising Network across the site, the kids section included. Yandex chooses and shows these ads under its own rules. For these visitors Yandex Metrica works on every page until they choose "Opt out" in our cookie banner.
- Google ads. Most other visitors see Google AdSense ads. For them, kids pages have no Google ads, and Yandex Metrica does not load there.
- Consent in Europe. In the European Economic Area, the United Kingdom and Switzerland, Google shows its own consent message on pages with Google ads. Google shows personalized ads only with your consent and uses cookies for ads as you choose there. You can change your choice at any time with the privacy and cookie settings link that Google shows at the bottom of the page.
- Analytics in Europe. If you see Google ads and your device's time zone is in these countries, or names no country, our analytics, Yandex Metrica, waits for your answer in Google's message, unless Google reports that these rules do not apply to your visit. In that message nub.games asks for your consent to four purposes of its own: store and/or access information on a device, measure content performance, understand audiences through statistics, and develop and improve services. Metrica loads only once you have consented to the first of them and to measuring content performance or understanding audiences. Until you answer, or if you refuse, it does not load. After you withdraw consent, it stops loading from the next page load.
- US states. In some US states with their own privacy laws, Google adds a "Do Not Sell or Share My Personal Information" link to pages with its ads. Use it to opt out of the sale or sharing of your personal information; Google then turns off ad personalization for you.
- Ad blockers. On pages with Google ads, a Google Funding Choices script may also run to measure how many visitors use an ad blocker. It shows no messages.
Children's Privacy
nub.games is a site for a general audience with a section of games for children: the Kids Games hub, the Kids category, collections for kids and the pages of games made for children.
- Most visitors outside Russia see Google ads on the rest of the site. On kids pages they see no Google ads, and Yandex Metrica does not load there.
- Visitors in Russia, and visitors who came from a Yandex ad, see ads from the Yandex Advertising Network on kids pages too. Yandex shows them under its own rules, and Yandex Metrica works there as on other pages.
- Games on all pages, kids pages included, are embedded from Yandex Games. Inside a game Yandex may show its own ads and collect data under its own policy; we do not control this.
If you believe a child has given us personal information, write to maxdev@appyapp.org and we will delete the information we hold.
Contact
Questions about this policy, or DSAR / 152-ФЗ data-subject requests, should go to maxdev@appyapp.org. The operator's postal address and registration details are listed on the Imprint page.