Application Policies

2.1

Your application must be fully functional when acquired from Windows Phone Marketplace (except for additional data as permitted below). Unless you have a pre-existing billing relationship with the user, your application may not require the user to provide payment information, within the application experience, to activate, unlock, or extend usage of the application.

2.2

Your application may not sell, link to, or otherwise promote mobile voice plans.

2.3

Your application must not jeopardize the security or functionality of (a) Windows Phone devices or (b) Windows Phone Marketplace.

2.4

If your application includes or displays advertising, the advertising must comply with the Microsoft Advertising Creative Acceptance Policy Guide and the application must have distinct, substantial and legitimate content and purpose other than the display of advertising.

2.5

If your application requires the download of a large additional data package (e.g. greater than 50 MB) to enable the application to run as described, the application description must disclose the approximate size of the data package and that additional charges may apply depending on connectivity used to acquire data.

2.6

If your application enables chat, instant messaging, or other person-to-person communication and allows the user to setup or create his or her account or ID from the mobile device, the application must include a mechanism to verify that the user creating the account or ID is at least 13 years old.

2.7

The following requirements apply to applications that receive the location of a user's mobile device:

2.7.1

Your application must determine location using the Microsoft Location Service API.

2.7.2

The privacy policy of your application must inform users about how location data from the Location Service API is used and disclosed and the controls that users have over the use and sharing of location data. This can be hosted within or directly linked from the application.

2.7.3

Your application must provide in-application settings that allow the user to enable and disable your application's access to and use of location from the Location Service API.

2.7.4

If your application publishes or makes available location data obtained from the Location Service API to any other service or other person (including advertising networks), your application must implement a method to obtain opt-in consent. To "implement a method to obtain 'opt-in' consent," the application must:

• (a) first describe how the location information will be used or shared;

• (b) obtain the user's express permission before publishing the location information as described; and

• (c) provide a mechanism through which the user can later opt out of having the location information published. Your application must periodically remind users or provide a visual indicator that location data is being sent to any other service or person.

2.7.5

Your application must not override, circumvent, or suppress any Microsoft toast notification or prompts related to the Location Service API.

2.7.6

Your application must not override or circumvent a user's choice to disable location services on the mobile device.

2.7.7

Your application must request location and retain and use location data from the Location Service API only as necessary to deliver the location-aware features your application provides to users.

2.7.8

You and your application must adopt measures to protect against unauthorized access to, use or disclosure of location data received from the Location Service API.

2.8

If your application shares a user's personal information (including, but not limited to Contacts, Photos, Phone number, SMS, Browsing history or unique device or user IDs combined with user information) with third parties such as other services or individuals, the application must implement a method to obtain "opt-in" consent.

To "implement a method to obtain 'opt-in' consent," the application must:

• provide your privacy policy, which at a minimum must describe how the personal information will be used or shared;

• obtain the user's express permission before sharing the information as described; and

• provide a mechanism through which the user can later opt out of having the information shared.

2.9

If your application uses the Microsoft Push Notification Service, the application and the use of the Microsoft Push Notification Service must comply with the following requirements:

2.9.1

The application must first describe the notifications to be provided and obtain the user’s express permission (opt-in), and must provide a mechanism through which the user can opt out of receiving push notifications. All notifications provided using the Microsoft Push Notification Service must be consistent with the description provided to the user and must comply with all applicable Application Policies Content Policies and Additional Requirements for Specific Application Types.

2.9.2

The application and its use of the Microsoft Push Notification Service must not excessively use network capacity or bandwidth of the Microsoft Push Notification Service, or otherwise unduly burden a Windows Phone or other Microsoft device or service with excessive push notifications, as determined by Microsoft in its reasonable discretion, and must not harm or interfere with any Microsoft networks or servers or any third party servers or networks connected to the Microsoft Push Notification Service.

2.9.3

The Microsoft Push Notification Service may not be used to send notifications that are mission critical or otherwise could affect matters of life or death, including without limitation critical notifications related to a medical device or condition. MICROSOFT EXPRESSLY DISCLAIMS ANY WARRANTIES THAT THE USE OF THE MICROSOFT PUSH NOTIFICATION SERVICE OR DELIVERY OF MICROSOFT PUSH NOTIFICATION SERVICE NOTIFICATIONS WILL BE UNINTERRUPTED, ERROR FREE, OR OTHERWISE GUARANTEED TO OCCUR ON A REAL-TIME BASIS.

2.10

Your application must have distinct, substantial and legitimate content and purpose. Your application must provide functionality other than launching a webpage. 

2.11

Your application and its associated metadata must accurately represent its functionality, capabilities and features.