App policies for Windows Phone
November 04, 2013
To protect the Windows Phone Store service and users of the service, and to address mobile operator requirements, Microsoft has established the following policies for apps (including publisher name, app name, app icon, app description, and app screenshots) offered for distribution in the Windows Phone Store. Microsoft reserves the right to update these policies as needed.
If your app includes in-app purchase, billing functionality or captures financial information, the following requirements apply:
If your app uses the Microsoft in-app purchase API provided by Windows Phone, the following requirements apply:
You cannot use in-app purchase to sell VoIP minutes in Australia, Brazil, Turkey or United States.
If your app includes in-app billing functionality or captures financial account information but does not use the Microsoft in-app purchase API provided by Windows Phone, the following requirements apply for the listed account types:
If your app is used to facilitate or collect charitable contributions or to conduct a promotional sweepstakes or contest, you must do so in compliance with applicable law. It must be clear that Microsoft is not the fundraiser or sponsor of the promotion.
Your app may not sell, link to, or otherwise promote mobile voice plans.
Your app must not jeopardize the security or functionality of (a) Windows Phone devices or (b) the Windows Phone Store and must not have the potential to cause harm to Windows Phone Users.
If your app includes or displays advertising, the advertising must comply with the Microsoft Advertising Creative Acceptance Policy Guide and the app must have distinct, substantial and legitimate content and purpose other than the display of advertising.
If your app requires the download of a large additional data package (e.g. greater than 50 MB) to enable the app to run as described, the app description must disclose the approximate size of the data package and that additional charges may apply depending on connectivity used to acquire data.
If your app 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 app must include a mechanism to verify that the user creating the account or ID is at least 13 years old.
The following requirements apply to apps that receive the location of a user's mobile device:
Your app must determine location using the Microsoft Location Service API.
Your app must provide in-app settings that allow the user to enable and disable your app's access to and use of location from the Location Service API.
If your app publishes or makes available location data obtained from the Location Service API to any other service or other person (including advertising networks), your app must implement a method to obtain opt-in consent. To "implement a method to obtain 'opt-in' consent," the app must:
Your app must not override, circumvent, or suppress any Microsoft toast notification or prompts related to the Location Service API.
Your app must not override or circumvent a user's choice to disable location services on the mobile device.
Your app must request location and retain and use location data from the Location Service API only as necessary to deliver the location-aware features your app provides to users.
You and your app must adopt measures to protect against unauthorized access to, use or disclosure of location data received from the Location Service API.
If your app (a) accesses or uploads a user's Contacts, Photos, Phone number, SMS history, Browsing history or any other data reasonably considered personal in nature, or if your app shares any of the foregoing information with third-party services or individuals, or (b) shares any unique device or user IDs, combined with user information, with third-party services or individuals, the app must implement a method to obtain the user’s "opt-in" consent.
To "implement a method to obtain 'opt-in' consent," the app must:
If your app uses the Microsoft Push Notification Service, the app and the use of the Microsoft Push Notification Service must comply with the following requirements:
The app 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 App policies for Windows Phone, Content policies for Windows Phone and Additional requirements for specific app types for Windows Phone.
The app 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.
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.
Your app and metadata must have distinct, substantial and legitimate content and purpose.
Your app must be fully functional when acquired from the Windows Phone Store and it must provide functionality other than launching a webpage.
Your app must not be unreasonably priced in relation to the functionality of the app.
Your app and its associated metadata must accurately represent its functionality, capabilities and features.
If your app has a Voice Command Definition (VCD) file, the CommandPrefix element in the VCD file and the app name must not be a homophone or an exact match to a speech system command. For a list of speech system commands, see System voice commands for Windows Phone 8. For more information about voice commands, see Voice commands for Windows Phone 8.