mardi 22 août 2017

Privacy policy

Protecting your privacy is important to us. We hope the following statement will help you understand how Ziani anas deals with the android permission READ-PHONE-STATE and android permission GET-ACCOUNT you may occasionally provide to us via Internet Ziani anas uses Admob as ads provider. Admob wants to show ads that are relevant to you. · Device and app history – An app may be able to do read sensitive log data, read web bookmarks and history, retrieve apps and retrieve system internal state. The last one is caused by the android.permission.DUMP which allows the app to retrieve state dump information from system services. This can reveal very sensitive information about the device using the app. All of these permissions deal with device and app history. · In-app Purchases – The application offers ways to purchase content inside the app itself. For example, an in-game currency. This will needed to be added to the Androidmanifest to use this permission. · Contacts – This permission is similar to last one, however, this one can only access contacts on the device, however, it still has the ability to read and modify them. Googel has put all the permissions neatly into this permissions group. · Location – An app can use the device’s location. This includes two different location settings, approximate and precise. Using the approximate location option, the app gets the device’s location from the network, and the precise option uses the device’s GPS and network to determine the location. To do this, the permission allows the app to access extra location provider commands and GPS. · SMS – The app can use the device’s SMS and MMS services. This includes the ability to receive text messages (SMS, WAP), read SMS and MMS, edit SMS and MMS, and send SMS and MMS. This can cost money. · Phone – The app can directly call phone numbers. Read and write the call log, reroute outgoing calls, modify phone state and make calls without the user knowing. Like the SMS permission, this can cost money. This permission group handles everything that has to do with telephony features. · Photos/Media/Files – The application has the ability to use the file on the device with the application installed. This includes reading and writing to the SD card and USB storage. The app can also mount and un mount external storage as well as format external storage. This permission deals with reading external storage on newer devices. · Microphone – The app can use the device’s microphone, this may include recording audio. This may happen with or without the user’s permission. · Identity – With this permission the app can find accounts on the device, see and modify the owner’s contact card and add or remove contacts from the device. The permission group CONTACTS deals with the user’s contacts while ACCOUNT_MANAGER deals with the user’s accounts. · Cellular data settings – The app can control the device’s mobile network settings and possibly intercept the data received. Here are some examples of the permissions needed. · Wi-Fi connection information – The app can access the device’s Wi-Fi connection information including whether or not Wi-Fi is turned off as well as connected devices. · Bluetooth connection information – The application can control Bluetooth which includes sending and receiving data from nearby devices. · Wearable sensors/activity data – The device is able to access information from a wearable device. For example, getting heart rate information from an Android Wear device. · Device ID & call information – An app can access the device ID, phone number, whether the device is making a call, and the number connected on the other end of the call. · Other – If a function of an app does not fit inside one of the other permissions, there is the ability to add an “other” permission. This may include using social media streams and the like. If this is included as a permission, users will have to approve every update of the application. These permissions are used to get the weather from the device and relay the information to an Android Wear device. Google offers documentations for developers to use to determine what permissions should be used. Declaring permissions should happen in the Android manifest in the format provided in the image. In the sample code posted, it is not necessary to include watch permissions, they are only required if the app works with Android Wear. It should be noted that whether or not to send us your feedback or bug report is a completely voluntary initiative upon your own decision. If you want further information about our privacy policy and what it means, please feel free to email us at anas-peace@hotmail.com, we will endeavor to provide clear answers to your questions in a timely manner.