United States: Lessons From In Re HTC America Inc.: FTC's Broadening Approach To Consumer Data Security Leaves Unwary Manufacturer Or Developer With More Than It Bargained For

Last Updated: March 13 2013
Article by Mauricio F. Paez

The Federal Trade Commission's ("FTC") recent enforcement action In the Matter of HTC America Inc ("HTC"), FTC File No. 1223049, illustrates the FTC's broadening approach to regulating reasonable data security practices and consumer protection. The FTC's traditional enforcement action in the area of consumer privacy and data security protection has focused on companies with direct contact with consumers. The complaint and consent order in In the Matter of HTC America Inc. is significant because it involves component manufacturers and software developers who provide the solutions used to store, process, or otherwise interact with consumer personal data. As a result of this consent order, a much broader range of companies needs to consider the privacy and data security implications of developing custom applications and software interfaces for consumer products.

The Complaint

HTC is a mobile device manufacturer whose portfolio includes smart phones and tablets powered by the Android and Windows Phone mobile operating systems. The FTC charged HTC with failing to employ "reasonable security measures" in the customization of software used in certain mobile devices running these operating systems. Although these devices were sold to consumers by network operators, the FTC charged HTC with unfair and deceptive business practices related to security and privacy violations in connection with HTC's creation and modification of preinstalled applications, and HTC's representations made in the devices' user manuals and interfaces.

Allegations. In support of its position that HTC engaged in unfair and deceptive business practices in violation of consumer protections, the FTC complaint alleged that HTC: (i) failed to implement an adequate program to assess the appropriateness of the security features in its mobile devices; (ii) failed to implement adequate data privacy and security guidance or training for its engineering staff; (iii) failed to conduct ongoing assessments and reviews to identify potential security vulnerabilities in its mobile devices; (iv) failed to follow well-known and commonly accepted secure coding practices; and (v) failed to implement a process for receiving and addressing security vulnerability reports from researchers, academics, or the public.

Permissions and Re-Delegation. The primary focus of the FTC's complaint was HTC's various actions and inactions that allegedly undermined Android's permission-based security model. The Android operating system employs a permission-based approach to restrict access by third-party applications to certain information (e.g., location information or the contents of text messages) and device functionality (e.g., the ability to record audio through the device's microphone or take pictures with the device's camera). Third-party applications are required to declare, during the installation process, what information or functionality they access, and request a user's permission prior to such access.

The FTC contended that HTC undermined Android's permission-based security model by introducing "permission re-delegation" vulnerabilities through its own custom applications that it preinstalled on each device. This custom software allowed third-party applications to access sensitive information and functionalities without receiving permission from the user. For example, the FTC alleged that HTC preinstalled a custom voice recorder on its devices that, if exploited, enabled third-party applications to access the device's microphone, without requesting permission from the user.

Similarly, the FTC alleged that HTC preinstalled a download application that enabled third-party applications to install any additional applications from any server onto the device without the user's knowledge or consent by bypassing the Android permission-based security installation protocol. Because the preinstalled download application installs applications outside the normal Android application installation process, the FTC alleged the user would not be notified of what sensitive information or functionality the application would access. The FTC alleged that this vulnerability "undermine[d] all protections provided by Android's permission-based security model."

Despite these alleged security deficiencies, HTC's user manuals for its Android-based mobile devices discussed Android's permission-based security model and informed consumers that applications installed from the Android marketplace require permission to access personal information or sensitive device functions.

Insecure Communications Mechanisms. Another significant security threat alleged by the FTC was the insecure communications mechanisms HTC utilized in implementing the HTC Logger and Carrier IQ logging applications on its devices. These logging applications saved important information regarding a user and the device, including GPS and network locations, web-browsing and media-viewing history, the user's personal phone number, text message content, and any other usage and device information specified for collection by network operators. The FTC contended that the communications mechanisms used to process and analyze the logging data were unencrypted, and thus any third-party application with internet access could access the sensitive information contained on the loggers, rendering the device and such data insecure.

Debug Code. The FTC also alleged that HTC failed to deactivate the debug code it used to develop and test its implementation software for the Carrier IQ logging application. As a result, all information sent to Carrier IQ by such software was written to the Android system log. This information was then viewable by any third-party application with permission to read the log, and included GPS-based location, web-browsing and media-viewing history, and the content of incoming text messages. This information was also provided to HTC whenever a user chose to send error reports using the "Tell HTC" error reporting tool, even where the user to declined consent to the transmission of location information to HTC.

Claims. The FTC claimed HTC's practices constitute unfair business practices by causing, or being likely to cause, substantial injury to consumers, including potential financial harm (due to compromised bank information, personal history information, text message fraud) and physical harm (by possibly physically tracking or stalking individuals by manipulating sensitive device functionalities).

It also alleged that HTC engaged in deceptive business practices by making false or misleading representations concerning data and device security in its user manuals, while including custom applications that circumvented the operating system's permission-based security model.

Finally, the FTC charged HTC with using a deceptive user interface with regard to its "Tell HTC" reporting tool, which purported to require user consent to transmit location data to HTC, but which transmitted the data without such consent.

The Consent Order

Without admitting fault, HTC stipulated to a 20-year term consent order to settle the enforcement action. Like many FTC consent orders, this consent order requires HTC to establish a comprehensive security program designed to address security risks relating to devices and consumer data. The consent order and settlement require HTC to identify and implement a wide-ranging protocol throughout its mobile devices business, including:

  • Designating employees to coordinate and be accountable for the security program;
  • Identifying internal and external risks to the security of mobile devices that could result in unauthorized access to, or use of, device functionality (and continuously assessing the risks);
  • Identifying material internal and external risks to the security, confidentiality, and integrity of consumer information that could result in unauthorized disclosure, misuse, loss, alteration, destruction, or other compromise of such information (and continuously assessing the risks);
  • Designing and implementing reasonable safeguards to control the risks identified through the risk assessments, including through reasonable and appropriate software security testing techniques, and regular testing or monitoring of the security program; and
  • Developing and using reasonable steps to select and retain service providers capable of maintaining security practices consistent with the consent order.

The consent order also requires HTC to issue security patches to address the security vulnerabilities identified in the complaint. Additionally, HTC is required to develop record retention, notice, and reporting processes to ensure its compliance with the consent order and hire a qualified, objective, independent third-party professional to assess, evaluate, and issue reports regarding its security program every two years during the consent order's 20-year term. The consent order is currently open for public comment, with comments due by March 22, 2013.


Many original equipment manufacturers and device application providers collect device and certain user data to improve their products and, in some cases, establish a direct relationship with consumers through product registrations, warranty support, and device use analytics. As illustrated by the FTC's complaint, the entire chain of companies connected with consumer products, especially those that implicate the collection and storage of consumer data, are expected to employ reasonable device and information security practices. Manufacturers and developers are expected to implement a reasonable design and development process that adopts reasonable security practices to avoid introducing security risk into consumer products. This recent FTC enforcement action shows that even manufacturers and developers with limited contact with consumers face data privacy and security consumer protection enforcement risks.

Also, the FTC's policy of "security by design" now clearly applies to any number of "upstream" activities that can affect the consumer. Companies must therefore address privacy and data security issues when developing custom applications and software interfaces for consumer products. Such applications and interfaces should also include privacy policies where the associated device collects and stores data about the customer, because enforcement agencies often link together issues relating to privacy and security.

In the case of HTC, software development was alleged to have provided access to sensitive information both directly (microphones, etc.) and through logging applications and error reports. To the FTC, inadequate post-development controls (such as the failure to have a security checklist or other control mechanism to detect that the debugging code had not been deactivated), and the lack of appropriate monitoring and audit procedures, compounded the development problems and delayed detection and correction of the security flaws. Accordingly, in addition to considering security at the development stage, it is equally important for companies in the supply chain to establish security procedures connected to ongoing post-development product monitoring.

This consent order also has implications for any original manufacturers and developers and upstream companies that provide communications to consumers relating to data, device, and application security. All notices, user manuals, information sheets, and other information shared with consumers directly by such companies must accurately reflect the product's security to avoid potential false or misleading representation allegations. This will become increasingly important for companies that traditionally have not established a direct consumer relationship through data collection and installed applications, but that increasingly see significant value in such relationships.

In sum, original manufacturers and upstream developers must take stock of the data security issues implicated by their products and programs. Security should be considered at each stage of development, with attention to reasonable, industry-standard security principles and practices. These include utilizing appropriate notice and consent procedures, limiting collection and storage of information, protecting collected information through encryption or other reasonable procedures, and having reasonable procedures to identify and remedy security threats. The FTC business guide, Mobile App Developers: Start with Security, provides additional information software developers may find useful in implementing reasonable security measures.

The content of this article is intended to provide a general guide to the subject matter. Specialist advice should be sought about your specific circumstances.

To print this article, all you need is to be registered on Mondaq.com.

Click to Login as an existing user or Register so you can print this article.

Mauricio F. Paez
In association with
Related Video
Up-coming Events Search
Font Size:
Mondaq on Twitter
Register for Access and our Free Biweekly Alert for
This service is completely free. Access 250,000 archived articles from 100+ countries and get a personalised email twice a week covering developments (and yes, our lawyers like to think you’ve read our Disclaimer).
Email Address
Company Name
Confirm Password
Mondaq Topics -- Select your Interests
 Law Performance
 Law Practice
 Media & IT
 Real Estate
 Wealth Mgt
Asia Pacific
European Union
Latin America
Middle East
United States
Worldwide Updates
Check to state you have read and
agree to our Terms and Conditions

Terms & Conditions and Privacy Statement

Mondaq.com (the Website) is owned and managed by Mondaq Ltd and as a user you are granted a non-exclusive, revocable license to access the Website under its terms and conditions of use. Your use of the Website constitutes your agreement to the following terms and conditions of use. Mondaq Ltd may terminate your use of the Website if you are in breach of these terms and conditions or if Mondaq Ltd decides to terminate your license of use for whatever reason.

Use of www.mondaq.com

You may use the Website but are required to register as a user if you wish to read the full text of the content and articles available (the Content). You may not modify, publish, transmit, transfer or sell, reproduce, create derivative works from, distribute, perform, link, display, or in any way exploit any of the Content, in whole or in part, except as expressly permitted in these terms & conditions or with the prior written consent of Mondaq Ltd. You may not use electronic or other means to extract details or information about Mondaq.com’s content, users or contributors in order to offer them any services or products which compete directly or indirectly with Mondaq Ltd’s services and products.


Mondaq Ltd and/or its respective suppliers make no representations about the suitability of the information contained in the documents and related graphics published on this server for any purpose. All such documents and related graphics are provided "as is" without warranty of any kind. Mondaq Ltd and/or its respective suppliers hereby disclaim all warranties and conditions with regard to this information, including all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement. In no event shall Mondaq Ltd and/or its respective suppliers be liable for any special, indirect or consequential damages or any damages whatsoever resulting from loss of use, data or profits, whether in an action of contract, negligence or other tortious action, arising out of or in connection with the use or performance of information available from this server.

The documents and related graphics published on this server could include technical inaccuracies or typographical errors. Changes are periodically added to the information herein. Mondaq Ltd and/or its respective suppliers may make improvements and/or changes in the product(s) and/or the program(s) described herein at any time.


Mondaq Ltd requires you to register and provide information that personally identifies you, including what sort of information you are interested in, for three primary purposes:

  • To allow you to personalize the Mondaq websites you are visiting.
  • To enable features such as password reminder, newsletter alerts, email a colleague, and linking from Mondaq (and its affiliate sites) to your website.
  • To produce demographic feedback for our information providers who provide information free for your use.

Mondaq (and its affiliate sites) do not sell or provide your details to third parties other than information providers. The reason we provide our information providers with this information is so that they can measure the response their articles are receiving and provide you with information about their products and services.

If you do not want us to provide your name and email address you may opt out by clicking here .

If you do not wish to receive any future announcements of products and services offered by Mondaq by clicking here .

Information Collection and Use

We require site users to register with Mondaq (and its affiliate sites) to view the free information on the site. We also collect information from our users at several different points on the websites: this is so that we can customise the sites according to individual usage, provide 'session-aware' functionality, and ensure that content is acquired and developed appropriately. This gives us an overall picture of our user profiles, which in turn shows to our Editorial Contributors the type of person they are reaching by posting articles on Mondaq (and its affiliate sites) – meaning more free content for registered users.

We are only able to provide the material on the Mondaq (and its affiliate sites) site free to site visitors because we can pass on information about the pages that users are viewing and the personal information users provide to us (e.g. email addresses) to reputable contributing firms such as law firms who author those pages. We do not sell or rent information to anyone else other than the authors of those pages, who may change from time to time. Should you wish us not to disclose your details to any of these parties, please tick the box above or tick the box marked "Opt out of Registration Information Disclosure" on the Your Profile page. We and our author organisations may only contact you via email or other means if you allow us to do so. Users can opt out of contact when they register on the site, or send an email to unsubscribe@mondaq.com with “no disclosure” in the subject heading

Mondaq News Alerts

In order to receive Mondaq News Alerts, users have to complete a separate registration form. This is a personalised service where users choose regions and topics of interest and we send it only to those users who have requested it. Users can stop receiving these Alerts by going to the Mondaq News Alerts page and deselecting all interest areas. In the same way users can amend their personal preferences to add or remove subject areas.


A cookie is a small text file written to a user’s hard drive that contains an identifying user number. The cookies do not contain any personal information about users. We use the cookie so users do not have to log in every time they use the service and the cookie will automatically expire if you do not visit the Mondaq website (or its affiliate sites) for 12 months. We also use the cookie to personalise a user's experience of the site (for example to show information specific to a user's region). As the Mondaq sites are fully personalised and cookies are essential to its core technology the site will function unpredictably with browsers that do not support cookies - or where cookies are disabled (in these circumstances we advise you to attempt to locate the information you require elsewhere on the web). However if you are concerned about the presence of a Mondaq cookie on your machine you can also choose to expire the cookie immediately (remove it) by selecting the 'Log Off' menu option as the last thing you do when you use the site.

Some of our business partners may use cookies on our site (for example, advertisers). However, we have no access to or control over these cookies and we are not aware of any at present that do so.

Log Files

We use IP addresses to analyse trends, administer the site, track movement, and gather broad demographic information for aggregate use. IP addresses are not linked to personally identifiable information.


This web site contains links to other sites. Please be aware that Mondaq (or its affiliate sites) are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of these third party sites. This privacy statement applies solely to information collected by this Web site.

Surveys & Contests

From time-to-time our site requests information from users via surveys or contests. Participation in these surveys or contests is completely voluntary and the user therefore has a choice whether or not to disclose any information requested. Information requested may include contact information (such as name and delivery address), and demographic information (such as postcode, age level). Contact information will be used to notify the winners and award prizes. Survey information will be used for purposes of monitoring or improving the functionality of the site.


If a user elects to use our referral service for informing a friend about our site, we ask them for the friend’s name and email address. Mondaq stores this information and may contact the friend to invite them to register with Mondaq, but they will not be contacted more than once. The friend may contact Mondaq to request the removal of this information from our database.


From time to time Mondaq may send you emails promoting Mondaq services including new services. You may opt out of receiving such emails by clicking below.

*** If you do not wish to receive any future announcements of services offered by Mondaq you may opt out by clicking here .


This website takes every reasonable precaution to protect our users’ information. When users submit sensitive information via the website, your information is protected using firewalls and other security technology. If you have any questions about the security at our website, you can send an email to webmaster@mondaq.com.

Correcting/Updating Personal Information

If a user’s personally identifiable information changes (such as postcode), or if a user no longer desires our service, we will endeavour to provide a way to correct, update or remove that user’s personal data provided to us. This can usually be done at the “Your Profile” page or by sending an email to EditorialAdvisor@mondaq.com.

Notification of Changes

If we decide to change our Terms & Conditions or Privacy Policy, we will post those changes on our site so our users are always aware of what information we collect, how we use it, and under what circumstances, if any, we disclose it. If at any point we decide to use personally identifiable information in a manner different from that stated at the time it was collected, we will notify users by way of an email. Users will have a choice as to whether or not we use their information in this different manner. We will use information in accordance with the privacy policy under which the information was collected.

How to contact Mondaq

You can contact us with comments or queries at enquiries@mondaq.com.

If for some reason you believe Mondaq Ltd. has not adhered to these principles, please notify us by e-mail at problems@mondaq.com and we will use commercially reasonable efforts to determine and correct the problem promptly.