Privacy Policy of “Numbrle” Android App:

"Numbrle" Android App uses Google Play Games Services, Google AdMob and Google Mobile Ads SDK. 

Part 1: Leaderboards:

The purpose for using the data and how the app accesses Google user data:

Which user data does it need?
It uses Google Play Games Services player name and score.

-Google Play Games Services player name is the name you entered when you log in to Google Play Games in your device.

-Score is how many times you guessed the number correctly. When you win a round, it means 1.

Purpose of this data
These info (player name and score) are used for showing the Leaderboard. Leaderboard is the High Score list where you can see your ranking among other players in the world.

When you start the app, it automatically prompts you to log in to Google Play Services. If you log in, whenever you win a round, it adds up 1 to your score.

If you don't log in when the app starts, you cannot publish your score and see your ranking among other players. 

How it's accessed:
It will get your player name data through Google's OAuth login info. It will calculate the score by how many times you win the game to use in Google Play Leaderboards. 
When you guess the number right, it adds one to your score. Your score is determined locally and then uploaded to Leaderboards, online. When you tap High Scores, the Leaderboards is retrieved from Google Cloud Services and shown on screen.

We use Google's APIs and SDKs and Google Cloud Services while doing that. 

How it's stored:
We don't store highscores or player names locally. They are stored on Google Cloud Services Leaderboards, online. 

How it's used:
It's only used for determining the High Scores and showing to players purposes. When you tap High Scores, the Leaderboard will be shown on screen.


Part 2: Ads:

Numbrle Android App may use personalized or non-personalized ads.

Personalized ads:

Personalized advertising (formerly known as interest-based advertising) is a powerful tool that improves advertising relevance for users and increases ROI for advertisers. In all our publisher products, we make inferences about a user’s interests based on the sites they visit or the apps they use. This allows advertisers to target their campaigns according to these interests, providing an improved experience for users and advertisers alike. 

Google considers ads to be personalized when they are based on previously collected or historical data to determine or influence ad selection, including a user's previous search queries, activity, visits to sites or apps, demographic information, or location. Specifically, this would include, for example: demographic targeting, interest category targeting, remarketing, targeting Customer Match lists, and targeting audience lists uploaded in DoubleClick Bid Manager or Campaign Manager 360.

Non-personalized ads (NPA):

Non-personalized ads are ads that are not based on a user’s past behavior. They are targeted using contextual information, including coarse (such as city-level) geo-targeting based on current location, and content on the current site or app or current query terms. Google disallows all personalized targeting, including demographic targeting and user list targeting. 

Although non-personalized ads don’t use cookies or mobile ad identifiers for ad targeting, they do still use cookies or mobile ad identifiers for frequency capping, aggregated ad reporting, and to combat fraud and abuse. 

Check out https://policies.google.com/technologies/partner-sites and http://www.google.com/policies/privacy/ for more.