Follow

Some Notes on Triple Town Android Permissions (Google Play version only)

Some people have been asking about the various permissions that Triple Town requests. On this page we discuss some of the permissions most commonly asked about and why the app requests them.

Note that it is not practical for us to make separate versions of the game for folks who don't like a particular permission and would be willing to give up the feature associated with that permission. We thus build the game with all features included, and permissions are asked accordingly.

(Permission names and descriptions are copied from what Google Play Store displayed to an Android 4.3 tablet in an attempted installation on 2014-01-29. The names and descriptions you see may differ slightly depending on how and when you look them up.)

Permission: Approximate location (network-based)

Description

Allows the app to get your approximate location. This location is derived by location services using network location sources such as cell towers and Wi-Fi. These location services must be turned on and available to your device for the app to use them. Apps may use this to determine approximately where you are.

Why Triple Town Requests It

The main game doesn't need it, but Tapjoy, the advertising service that provides the "Free Coins" option in some versions of the game, is requesting it. We assume this is so they can provide ads relevant to your geographic location. If you don't use the Free Coins service, your location data isn't used.

Permission: Find accounts on the device

Description

Allows the app to get the list of accounts known by the tablet. This may include any accounts created by applications you have installed.

Why Triple Town Requests It

The main game doesn't need it, but Fuel, the provider of the Boom Town Multiplayer feature, is requesting it. According to Fuel: "It's a convenience for sign on, allowing us to send a prize winning email, informing players how to claim and distribute their charitable tournament winnings."

Permission: Precise location (GPS and network-based)

Description

Allows the app to get your precise location using the Global Positioning System (GPS) or network location sources such as cell towers and Wi-Fi. These location services must be turned on and available to your device for the app to use them. Apps may use this to determine where you are, and may consume additional battery power.

Why Triple Town Requests It

The main game doesn't need it, but Tapjoy, the advertising service that provides the "Free Coins" option in some versions of the game, is requesting it. We assume this is so they can provide ads relevant to your geographic location. If you don't use the Free Coins service, your location data isn't used.

Per Tapjoy: "The GPS data is only leveraged at the point when the user engages with a GPS enabled ad, like locating your nearest McDonalds after a video. All of the geo data used at the point they engage with a geo-enabled ad is anonymized and never sold to 3rd parties for any reason."

Permission: Read phone status and identity

Description

Allows the app to access the phone features of the device. This permission allows the app to determine the phone number and device IDs, whether a call is active, and the remote number connected by a call.

Why Triple Town Requests It

The phone state is used to identify the device when a player makes an in-app purchase. We don't (nor could we) snoop on what you're saying in your phone conversations.

Permission: Retrieve running apps

Description

Allows the app to retrieve information about currently and recently running tasks. this may allow the app to discover information about which applications are used on the device.

Why Triple Town Requests It

The main game doesn't need it, but Fuel, the provider of the Boom Town Multiplayer feature, is requesting it. According to Fuel, this is needed for "Support so we can properly launch the game from push notifications."

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

0 Comments

Article is closed for comments.
Powered by Zendesk