Last updated: 15 December 2014

 

Reader® Mobile SDK is a software development kit that allows developers to create applications under their own name (these are referred to as Developer Applications) that download and view digital content, primarily eBooks, which may or may not contain digital rights management (DRM). DRM is a technology used by eBook providers to manage the copying, printing and sharing of eBooks.

The Adobe Privacy Policy describes the general privacy practices of most of Adobe’s websites and applications including Reader Mobile SDK. More privacy-related information for Reader Mobile SDK is provided below.

 

What information does Adobe collect on behalf of the developer when an end-user uses the Developer Application and how is that information used?

The following information may be collected by Adobe when an eBook with DRM is opened by a Developer Application. If an eBook does not have any DRM associated with it, then no information is collected.

  • User GUID: The User GUID is a unique value assigned in place of a User ID and is used to authenticate the end-user.
  • Device GUID: The Device GUID is a unique value generated to identify the end-user’s device. It is used to ensure that the eBook may be viewed on the end-user device and that the number of devices permitted by the licence is not exceeded.
  • Certified App ID: This ID represents the application that is being used to view the eBook, in this case the Developer Application. It is necessary to ensure that only a certified application may display an eBook. This helps to minimise piracy and theft of eBooks.
  • Device IP (Internet Protocol): This identifies the country the end-user is located in when they purchase an eBook. It is used by eBook providers for the enablement of localised pricing models. Only the country identifier of the Device IP is stored.
  • Duration for Which the Book was Read: This information may be collected to facilitate limited or metered pricing models entered into between eBook providers, such as publishers and distributors. These models are based on how long a reader has read an eBook. For example, an end-user may borrow an eBook for a period of 30 days. While some publishers and distributors may charge libraries and resellers for 30-days from the date of the download, others may follow a metered pricing model and charge them for the actual time the end-user reads the eBook.
  • Percentage of the eBook Read: The percentage of the eBook read may be collected to allow eBook providers, like publishers, to implement subscription pricing models where they charge based on the percentage of the eBook read.
  • Information provided by eBook providers relating to the eBook an end-user has  purchased: The following information is provided by the eBook provider to enable the delivery of the eBook to the end user’s device:
    • Date of eBook purchase/download
    • Distributor ID and Adobe Content Server Operator URL
    • Metadata of the eBook such as title, author, language, publisher list price, ISBN number
       

How is the information transmitted?

The data is sent periodically to Adobe via a secure transmission using HTTPS.

 

How is the information used?

Adobe uses the information collected about the eBook an end-user has opened in the Developer Application to ensure that it is being viewed in accordance with the type of DRM licence that accompanies that eBook. The type of licence is determined by the eBook provider. For more information on how each piece of data is used, please see above.

 

What information does Adobe share?

Adobe does not share any personally identifiable information. Adobe may share anonymous aggregated information with eBook providers to enable billing under the applicable pricing model.

 

Is there more information available about Adobe’s eBook solutions?

More information is available in Adobe’s white paper.