Click Here to Install Silverlight*
United StatesChange|All Microsoft Sites
Windows Media Player 9 Series
|Windows Media Worldwide

Windows Media 9 Series SDK Privacy Information

Privacy Information for Developers Using Windows Media
9 Series Software Development Kits


Summary: The following information is designed to assist developers in understanding what privacy information might be important to disclose to their end users when they build solutions on the following Microsoft® Windows Media® software development kits:

  • Microsoft® Windows Media® Player 9 Series Software Development Kit (Player SDK)
  • Microsoft® Windows Media® Encoder 9 Series Software Development Kit (Encoder SDK)
  • Microsoft® Windows Media® Format 9 Series Software Development Kit (Format SDK)

Communicating Privacy Information to End Users

Microsoft's goal is to help protect the privacy of end users. To help end users make informed choices regarding privacy, Microsoft publishes privacy statements that disclose what information Microsoft collects, how it is used, and what privacy options exist. Windows Media Player has such a statement. In addition, the first time an end user launches Windows Media Player, the user will be asked to set some important privacy options to enable them to make an informed choice right from the start.

When Microsoft technology is embedded in a 3rd Party application, it is not always possible for the Microsoft technology to present to the end user this type of privacy information For example, when the Windows Media Player ActiveX control is embedded in an application, privacy information such as what data is being collected or what privacy controls exist will not be communicated to the end user, unless the 3rd party application makes that information or control available through its own privacy disclosure or user interface.


Privacy and the Windows Media Player SDK

If you build your solution using the Player SDK, Microsoft recommends you inform your end users that your technology is built using Microsoft® Windows Media® Player technology and that they should review the Windows Media Player 9 Series privacy statement.

Ideally, you should focus the end user's attention on scenarios that they may encounter when using your solution. For example, if end users can use your application to play back protected content, you should direct them to the section on Microsoft Digital Rights Management. Other sections to reference might include:
  • Communication with Streaming Media Servers if your application plays back streamed content from a remote media server.

  • Media Library if your application manipulates the Player's Media Library.

  • Cookies if your application uses the Player SDK to access Web-based content or services.

  • Automatic CODEC Download if your play back of content could trigger a download of a CODEC from the Microsoft CODEC download service.

Privacy and the Windows Media Encoder SDK

Like the Player SDK above, if you build your solution using the Encoder SDK, you should inform your end users that your technology is built using Microsoft® Windows Media® Encoder technology and that they should review the Windows Media Encoder 9 Series privacy statement. A key section to reference is Digital Rights Management if your application can generate protected content.


Privacy and the Windows Media Format SDK

If you build your solution directly on the Format SDK and your solution is able to play back streamed content from a remote media server, Microsoft recommends you provide a disclosure similar to the one in the Windows Media Player 9 Series privacy statement that covers Communication with Streaming Media Servers.

If your solution is able to play back or manipulate content protected with Microsoft's digital rights management system for Windows Media (DRM), you have some special obligations relating to DRM Security Upgrades. It is through DRM Security Upgrades that the DRM security components on an end user's system can become "individualized", thus improving the overall security of DRM. According to the license agreement that covers DRM client use, your solution must initiate a DRM Security Upgrade (i) during setup, (ii) by end user invocation, or (iii) when DRM protected content that requires "individualization" is opened (i.e. when your application receives a WMT_NEEDS_INDIVIDUALIZATION status message).

From a privacy perspective, it is critical that you first receive an end user's explicit consent before performing a DRM Security Upgrade on their computer. When initiating a DRM Security Upgrade, Microsoft recommends you follow the user interface conventions listed below:
  1. Inform the end user (e.g. via a dialog box) that a DRM Security Upgrade is required to play the protected content the end user has selected (or may select). Your notice should inform the end user what information will be collected and what components will be downloaded onto the end user's computer.

  2. Provide the end user a choice of whether to perform the DRM Security Upgrade (e.g. include a button to accept the upgrade and a button to decline the upgrade).

  3. Include a "Learn More" button that will launch the following URL: http://go.microsoft.com/fwlink/?LinkId=12872. When launched, the URL will resolve to a Microsoft hosted web page containing DRM Security Upgrade privacy information.

  4. Only proceed with the DRM Security Upgrade if the end user provides their consent.
For additional information regarding possible DRM scenarios, see the Microsoft Digital Rights Management section in the Windows Media Player 9 Series privacy statement.


Additional links



Back to the top of this page Back to the top



© 2013 Microsoft Corporation. All rights reserved. Contact Us |Terms of Use |Trademarks |Privacy Statement
Microsoft