Tag: fcc

Save the Internet Act of 2019 Introduced

On 6 March 2019, Democrats in the House and Senate introduced the “Save the Internet Act of 2019.” The three-page bill (1) repeals the FCC’s Restoring Internet Freedom Order released in early 2018, as adopted by the Republican-led FCC under Chairman Ajit Pai; (2) prohibits the FCC from reissuing the RIF Order or adopting rules substantively similar to those adopted in the RIF Order; and (3) restores the Open Internet Order released in 2015, as adopted by the Democratic-led FCC under Chairman Tom Wheeler.

Major Impacts:

  • Broadband Internet Access Service (BIAS) is reclassified as a “telecommunications service,” potentially subject to all provisions in Title II of the Communications Act.

  • The three bright line rules of the Open Internet Order are restored: (1) no blocking of access to lawful content, (2) no throttling of Internet speeds, exclusive of reasonable network management practices, and (3) no paid prioritization.

  • Reinstates FCC oversight of Internet exchange traffic (transit and peering), the General Conduct Rule that authorizes the FCC to address anti-competitive practices of broadband providers, and the FCC’s primary enforcement authority over the Open Internet Order’s rules and policies.

  • Per the Open Internet Order, BIAS and all highspeed Internet access services remain subject to the FCC’s exclusive jurisdiction and the revenues derived from these services remain exempt from USF contribution obligations.

  • The prescriptive service disclosure and marketing rules of the Open Internet Order, subject to the small service provider exemption, would apply in lieu of the Transparency Rule adopted in the RIF Order.

FCC Chairman Pai promptly issued a statement strongly defending the merits and benefits of the RIF Order.

KH Assessment

  • From a political perspective, Save the Internet Act of 2019 garners support from many individuals and major edge providers committed to net neutrality principles but faces challenges in the Republican-controlled Senate.

  • In comments filed in the proceeding culminating in the RIF Order, the major wireline and wireless broadband providers supported a legislative solution that codified the no blocking and no throttling principles but not the no-paid prioritization prohibition or classifying BIAS as a telecommunications service.

It is highly unlikely that the legislation will be enacted as introduced. Though still unlikely, there is a better chance that a legislative compromise may be reached.

 

© 2019 Keller and Heckman LLP.

Now I Get It!: Using the FCC’s Order Keeping Text Messages as “Information Services” to Better Understand the Communications Act

Little known fact: the TCPA is just a tiny little part of something much bigger and more complex called the Communications Act of 1934, as amended by Telecom Act of 1996 (which the FCC loves to just call the “Communications Act.”) And yes, I know the TCPA was enacted in 1991 but trust me it is still part of the Communications Act of 1934.

The Communications Act divides communications services into two mutually exclusive types: highly regulated “telecommunications services” and lightly regulated “information services.”

So let’s look at some definitions:

A “telecommunications service” is a common carrier service that requires “the offering of telecommunications for a fee directly to the public, or to such classes of users as to be effectively available to the public, regardless of the facilities used.”

“Telecommunications” is “the transmission, between or among points specified by the end user, of information of the user’s choosing without change in the form or content of the information as sent and received.”

By contrast, an “information service” is “the offering of a capability for generating, acquiring, storing, transforming, processing, retrieving, utilizing, or making available information via telecommunications, and includes electronic publishing, but does not include any use of any such capability for the management, control, or operation of a telecommunications system or the management of a telecommunications service.”

Make sense so far? Basically a telecommunications service is something that telecommunications companies–who are common carriers– can’t tinker with and have to automatically connect without modifying. For instance, if I want to call my friends from law school and wish them well Verizon can’t say–wait a minute, Eric doesn’t have any friends from law school and refuse to connect the call. Verizon must just connect the call. It doesn’t matter who I am calling, how long the call will be, or why I’m making the call, the call must connect. The end.

Information services are totally different animals. Carriers can offer or not offer and tinker and manipulate such messages all they want–see also net neutrality.

So if text messages are a telecommunication then they must be connected without question. But if text messages are an information service then carriers can decide which messages get through and which don’t.

It might seem like you’d want text messages to be information services–after all why would we want the carriers determining how and when we can text each other? Well the FCC has an answer– automatic spam texts.

If text messages are subject to common carrier rules then people can blast your phone with spam text messages and the carriers can’t stop them. True the TCPA exists so you can sue the texter but–as we know–the vast majority of spammers are shady fly-by-nights or off-shore knuckleheads that you can’t find. So the FCC believes that keeping text messages categorized as “information services”–as they are currently defined–will keep spammers away from your SMS inbox. It issued a big order today accomplishing just that. 

And to be sure, the carriers are monitoring and block spam texts as we speak. As the FCC finds: “wireless messaging providers apply filtering to prevent large volumes of unwanted messaging traffic or to identify potentially harmful texts.”  The FCC credits these carrier efforts with keeping text messages relatively spam free:

For example, the spam rate for SMS is estimated at 2.8% whereas the spam rate for email is estimated at over 50%.  Wireless messaging is therefore a trusted and reliable form of communication for many Americans. Indeed, consumers open a far larger percentage of wireless messages than email and open such messages much more quickly.

So from a policy perspective keeping text messages as information services probably makes sense, but let’s review those definitions again.

A telecommunication service is essentially the transmission of information of the user’s choosing.

An information service is “the offering of a capability for generating, acquiring, storing, transforming, processing, retrieving, utilizing, or making available information via telecommunications.”

So is a text message the transmission of information of my choosing or is it the use of Verizon’s ability to store and retrieve information I am sending? (And is there really even a difference?)

Well the FCC says texts are absolutely information services and here’s why:

  • SMS and MMS wireless messaging services provide the capability for “storing”
    and “retrieving” information. When a user sends a message, the message is routed through servers on mobile networks. When a recipient device is unavailable to receive the message because it is turned off, the message will be stored at a messaging center in the provider’s network until the recipient device is able to receive it.

  • SMS and MMS wireless messaging services also involve the capability for “acquiring” and “utilizing” information. As CTIA explains, a wireless subscriber can “ask for and receive content, such as weather, sports, or stock information, from a third party that has stored that information on its servers. SMS subscribers can ‘pull’ this information from the servers by making specific requests, or they can signal their intent to have such information regularly ‘pushed’ to their mobile phone.

  • SMS and MMS wireless messaging services involve “transforming” and
    “processing” capabilities. Messaging providers, for example, may change the form of transmitted information by breaking it into smaller segments before delivery to the recipient in order to conform to the character limits of SMS.

Yeah…I guess. But realistically when I send a text I just want it to get there there the way I sent it. Maybe there’s some storing and utilizing and processing or whatever but not very much.

And that was Twilio’s point. It asserted:  “the only offering that wireless carriers make to the public, with respect to messaging, is the ability of consumers to send and receive messages of the consumers’ design and choosing.” That sounds right.

Well the FCC disagrees: “These arguments are unpersuasive.”

The FCC’s point is that “what matters are the capabilities offered by the service, and as we explain above, wireless messaging services feature storage, retrieval, and other information-processing capabilities.”

Hmmm. ok. I guess I’m ok with that if you are.

But let’s get to the good stuff from a TCPA perspective. Recall that a text message is a “call” for purposes of the TCPA. Well if a text isn’t even a telecommunication how can it be a call? Asks Twilio.

Yeah, FCC, how can it be a call? Asks the Czar.

The Commission answers:

the Commission’s decision merely clarified the meaning of the undefined term “call” in order to address the obligations that apply to telemarketers and other callers under the TCPA. That decision neither prohibits us from finding that wireless messaging service is an information service, nor compels us to conclude that messaging is a telecommunications service.

Ok. Well. Why not?

The Commission answers further:

The TCPA provision itself generally prohibits the use of a facsimile machine to send
unsolicited advertisements, but that does not constitute a determination that an individual’s sending of a fax is a telecommunications service, just as the application to an individual’s making “text calls” does not reflect a determination that wireless messaging is a telecommunications service. In any event, for purposes of regulatory treatment, there is a significant difference between being subject to Commission regulation and being subject to per se common carrier regulation. Only the latter requires classification as a telecommunications service. We clarify herein that SMS and MMS wireless messaging are Title I services, and thus, will not be subject to per se common carrier regulation.

Umm FCC, no disrespect intended, but I kind of feel like that doesn’t really answer the question.

But in any event, the FCC plainly believes that text messages are a “call” for purposes of the TCPA but are not a “telecommunication” for purposes of common carrier regulation.

From a policy perspective I’m fine with the conclusion the Commission reached–it makes sense to keep text messages free from spam. But we have to be honest with ourselves here, the Commission just did legal somersaults to get there. Maybe its time for Congress to take another look at the Communications Act hmmm?

In any event, now you get it!

 

Copyright © 2018 Womble Bond Dickinson (US) LLP All Rights Reserved.
This post was written by Eric Troutman of Womble Bond Dickinson (US) LLP.
Read more news about the TCPA at the National Law Review.

Federal Communications Commission Tackles the “Reassigned Number Problem”

Reassigned numbers have been at the center of the surge in litigation under the Telephone Consumer Protection Act (“TCPA”) during the last few years.  By now the story is well known to businesses that actively communicate with their customers: the customer consents to receive telemarketing and/or informational robocalls[1] at a wireless telephone number, but months or years later the customer changes his or her wireless telephone number and—unbeknownst to the business—the telephone number is reassigned to a different person.  When the recipient of the reassigned number starts receiving calls or messages from the business, a lawsuit often ensues under the TCPA because that party has not consented to receive such calls.  The FCC adopted on July 13 a Second Notice of Inquiry (“Second NOI”) that promises to address this problem in a meaningful way.  Specifically, the Second NOI focuses on the feasibility of “using numbering information to create a comprehensive resource that businesses can use to identify telephone numbers that have been reassigned from a consumer who has consented to receiving calls to a consumer who has not.”

Background on the Reassigned Number Problem

Under the current regime, the North American Numbering Plan (NANP) Administrator generally provides telephone numbers to voice service providers—including those who supply interconnected voice—in blocks of 1000.  The voice service providers recycle those numbers in and out of service, such that, after a number has been dropped, the number goes into a pool for a short period and then is brought out of the pool and reassigned to a different consumer.

The “reassigned number problem” occurs when a consumer consents to receive robocalls (telemarketing and/or informational), but then terminates service to the relevant wireless number without informing the businesses the consumer previously gave consent to make the robocalls.  Businesses that find themselves making robocalls to numbers that (unbeknownst to them) had been reassigned to a different consumer increasingly find themselves subject to lawsuits under the TCPA—this even though it has been widely acknowledged that (1) customers often switch telephone numbers without providing notice to businesses and (2) there is no public directory of reassigned wireless numbers that businesses can rely on to identify and scrub reassigned numbers.  When various industry groups and business entities asked the FCC to intervene, the FCC clarified that businesses making robocalls needed the consent of “the actual party who receives a call,” not of the intended recipient of the robocall.  FCC created a so-called “safe harbor” that afforded little protection in practice: a business could make a single call to a reassigned number without triggering liability under the TCPA, but the business would then be imputed with “constructive” knowledge that the number had been reassigned even if the single call did not yield actual confirmation that the number had been reassigned. The FCC did so even as it admitted that the tools available to identify reassigned numbers “will not in every case identify numbers that have been reassigned” and that the steps it was taking “may not solve the problem in its entirety” even “where the caller is taking ongoing steps reasonably designed to discover reassignments and to cease calls.”

The Second NOI

The Second NOI promises to more meaningfully address the reassigned number problem by suggesting the creation of a reliable, complete list of reassigned numbers that service providers would be required to update.  In pertinent part, the Second NOI addresses a number of other topics, including, but not limited to, possible reporting alternatives, compensation schemes, frequency of updates, and fees and eligibility requirements for accessing reassigned number data.  It also asks a number of logistical questions, including, but not limited to:

(1) What are the ways in which voice service providers could report the information in an accurate and timely way?

(2) Would the reporting—into a database or other platform—“substantially improve robocallers’ ability to identify reassigned numbers?”

(3) What information should voice service providers report?

(4) In what ways might the information reported raise concerns regarding the disclosure of private, proprietary, or commercially sensitive information?

(5) Should reassignment of toll-free numbers also be reported?

(6) What is the quantity of numbers reassigned and the benefits of reducing unwanted calls to these numbers?

(7) Should there be a safe harbor from TCPA violations for robocallers who use the new reassigned number resource?  What would be the advantages and disadvantages?

(8) How can the FCC incentivize robocallers to use the reassigned number resource?

In addition, the Second NOI seeks comment on whether the notification requirement should apply to all voice service providers or just providers of wireless services, and how to “balance the reporting burden placed on voice service providers against consumers’ privacy interests and robocallers’ interest in learning of reassignments.”   The item also seeks comment on which entity should be responsible for notification in circumstances when a voice service provider does not receive numbers directly from NANP, but instead obtains numbers “indirectly” from carrier partners.

The Commission claims it has the authority under Sections 227(b) and 251(e) of the Communications Act of 1934, as amended—which give the FCC control over the US portion of NANP and incorporate the TCPA—to require entities that obtain numbers from NANP to also report reassignments.  In fact, the Commission claims that doing so may further the statutory goals underlying the TCPA, which generally prohibits unwanted robocalls.

Although many details remain to be discussed and addressed by the FCC, the creation of the list that the FCC is proposing would address one of the main challenges faced by businesses that want to comply with the TCPA: how to gather reliable and complete information regarding which wireless telephone numbers have been reassigned.  The possibility of such a list working similar to that available to identify telephone numbers in the Do Not Call List is particularly promising, especially if it comes accompanied by safe harbor provisions similar to those attached to the Do Not Call List obligations in the FCC’s rules.

Comments are due August 28, 2017 and Reply Comments September 26, 2017.

[1] For purposes of this post “robocalls” refers to both calls made using an automatic telephone dialing system or using an artificial voice or pre-recorded message.

This post was contributed by Eduardo R. Guzmán  Paul C. Besozzi  and Koyulyn K. Miller of   Squire Patton Boggs (US) LLP
For more legal analysis check out the National Law Review.

FCC Slams Serial Robocaller With $120 Million Proposed Fine for “Spoofing” Numbers

We all get them.  Repeated marketing calls to our mobile and home phones with the incoming phone number altered to make it appear that it’s a local call, when in fact, the call is from a robo-scammer using IP technology to “spoof” the phone number.  As it turns out, there’s a federal law that makes such spoofing illegal, the Truth in Caller ID Act of 2009 (“TICIDA”), and in its first enforcement action under TICIDA, the FCC hit an alleged serial robocaller, Adrian Abramovich and his companies (together, Abramovich) with a whopping $120 million Notice of Apparent Liability for allegedly originating nearly 100 million such calls.

The Commission also issued a Citation and Order to Abramovich for alleged violations of the Telephone Consumer Protection Act (“TCPA”) for making unauthorized prerecorded telemarketing calls to emergency phone lines, wireless phones and residential phones without obtaining the required prior express written consent from the called party.  While TICIDA allows the Commission to directly fine first-time violators through its NAL authority, which it did here, in TCPA FCC enforcement actions involving entities and individuals that do not hold Commission authorizations, the Commission must first issue a citation, and then can only proceed with a fine if the recipient repeats the violation.  That still leaves Abramovich open to potentially monumental TCPA class action exposure.   The Citation and Order also notified Abromovich that he had violated the federal wire fraud statute by transmitting or causing to be transmitted, by means of wire, misleading or false statements with the intent to perpetrate a fraud.

According to the Commission, Abramovich ran a scheme where his spoofed calls appeared to originate from local numbers and offered, via a pre-recorded message, holiday vacations and cruises claiming to be associated with well-known American travel and hospitality companies.  The pre-recorded messages would prompt customers to “press 1” to secure their reservation.  Once a customer pressed “1”, the customer was transferred to a call center where live operators pushed vacation packages typically involving timeshare presentations, that were not affiliated with the well-known brands used in the recorded messages.  The Commission characterized Abramovich’s schemes as “one of the largest – and most dangerous – illegal robocalling campaigns the Commission has ever investigated.”  According to the Commission, in addition to defrauding consumers, the robocalling campaign also caused disruptions to an emergency medical paging service, which provides paging services for emergency room doctors, nurses, emergency medical technicians, and other first responders.

While significant in absolute terms, the $120 million proposed fine, according to the Commission, was significantly below the penalty that could have been proposed in the NAL.  Rather than fine the statutory maximum of $11,052 for each spoofing violation, or three times that amount for each day of a continuing violation, the Commission calculated the base forfeiture amount at $1,000 per unlawful spoofed call, since this was the first time the Commission used its TICIDA forfeiture authority.

Mr. Abromovitz now has an opportunity to respond to both the NAL and Citation.  Stopping illegal robocalling has been a key priority for Chairman Pai, and no doubt the Commission is expecting that the threat of huge monetary forfeiture penalties against the industry will provide a powerful incentive for roboscammers to look for other ways to make a buck.  Given the Commission’s struggle with fashioning tools to go after serial robocallers that do not have the effect of increasing TCPA exposure for established companies engaging in legitimate customer communications, we do not expect the Commission to back down from its proposed penalty, and expect this to be the start of a new enforcement initiative using TICIDA and its direct penalty provisions.

This post was written byRebecca E. Jacobs,  Martin L. Stern and  Douglas G. Bonner of Womble Carlyle Sandridge & Rice, PLLC.

The FCC Responds to Comcast’s Negative Option

FCC ComcastOn Tuesday, October 11, the Federal Communications Commission (“FCC” or “Commission”) announced the release of an Order and Consent Decree with cable behemoth Comcast Corporation (“Comcast”) in which the company agreed to pay US$2.3M to settle an FCC investigation into whether Comcast employed negative option billing to wrongfully charge for services and equipment customers never authorized.  The settlement also requires Comcast—by some accounts the largest cable company in the country with 22.3M subscribers—to adopt a sweeping, highly detailed five-year compliance plan designed to force the company to obtain customers’ affirmative informed consent prior to adding charges to their bills.  According to the FCC’s press release, the settlement amount is the largest civil penalty the agency has ever assessed against a cable operator.

What is Negative Option Billing and How Does the FCC Regulate It?

“Negative option billing” is a practice similar to “cramming” in the telecommunications context, wherein a company places unauthorized charges on a consumer’s bill, requiring subscribers to pay for services or equipment they did not affirmatively request.  In addition to the obvious nuisance of unknowingly paying for unauthorized services and equipment, the FCC’s action is also aimed at protecting consumers from “spend[ing] significant time and effort in seeking redress for any unwanted service or equipment, which is often manifested in long telephone wait times, unreturned phone calls from customer service, unmet promises of refunds, and hours of effort wasted while pursuing corrections.”  For these and other consumer protection reasons, negative option billing is illegal; it violates both Section 623(f) of the Communications Act of 1934, as amended (the Act), and Section 76.981(a) of the Commission’s rules.  Specifically, 47 U.S.C. § 543(f) explicitly prohibits negative billing options, noting also that a failure to refuse an offer is not the equivalent of accepting the offer.

As the FCC clarified in a 2011 Declaratory Ruling, while a customer does not have to know and recite specific names of equipment or service in the course of ordering those products, the cable operator must have “adequately explained and identified” the products in order for a subscriber to “knowingly accept[] the offered services and equipment by affirmative statements or actions.”

Section 76.981(b) explains that the negative billing option does not prevent a cable operator from making certain changes without consumer consent, such as modifying the mix of channels offered in a certain tier, or increasing the rate of a particular tier (unless more substantive changes are made, such as adding a tier, which then increases the price of service).

The FCC appears to have found only one violation of the negative option billing prohibition previously, and in that context, the Commission used its discretion to refrain from imposing a penalty.  More than 20 years ago, in 1995, the Commission acted on a complaint and investigated Monmouth Cablevision for allegations that the company—which had previously rented remote controls to their subscribers—violated FCC rules when it removed the leasing fee on subscriber bills and instead included a $5 sale price for the remotes. In that case, the Commission explained that, while “in a literal sense, this is the same equipment that the customer previously rented, we cannot find that these customers affirmatively requested to purchase these remotes rather than renting them.”  The Commission went on to explain that “changing the way in which existing service and equipment is offered, e.g., from leasing to selling,” did, in fact, violate the Commission’s negative option billing prohibition.  However, due to the “de minimis difference between the $ 5.00 purchase price and the total rental price” and because of the “large number of regulatory requirements that became effective on September 1, 1993, and the associated compliance difficulties,” the then Cable Services Bureau chose not to impose a penalty.  Because state governments have concurrent jurisdiction over negative billing practices, cable companies have faced court action for these and similar allegations for decades.

The FCC Investigation

Based on “numerous” consumer complaints, the FCC’s Enforcement Bureau opened an investigation in December of 2014 into whether Comcast engaged in negative option billing.  In the course of its investigation, the FCC determined that customers were billed for “unordered services or products, such as premium channels, set-top boxes, or digital video recorders (DVRs).”  Beyond not authorizing these products, in some cases the FCC claims that subscribers specifically declined additional services or upgrades, only to be billed anyway.  In fact, the Order—which is part of the settlement but generally not subject to the non-government party’s review prior to release—details numerous complainants that claim to have been given the runaround by Comcast customer service representatives, with one customer (Subscriber A) claiming that, after three hours on the phone and multiple transfers, she was ultimately transferred to a fax machine.  Another complainant (Subscriber B) asserted that he determined Comcast had wrongfully billed him for approximately 18 months for an extra cable box he never ordered, and that he spent another year calling to request (unsuccessfully) that the company remove the charge.

The Settlement

The Order and Consent Decree are striking in terms of the level of transparency exhibited throughout.  Unlike most FCC settlements, in which facts and legal arguments are closely guarded and held confidential, this Order reads more like a Notice of Apparent Liability for Forfeiture, where the FCC explains the underlying facts and legal theories in substantially more detail.  Especially noteworthy here, is that unlike majority of the other settlements released by the FCC’s Enforcement Bureau since Travis LeBlanc took the helm, neither the Order nor the Consent Decree include a statement admitting liability.  Rather than an admission of liability by Comcast, the Consent Decree includes a lengthy discussion of the perspectives of both Comcast and the Commission.  Besides arguing that most of the services were authorized and that unauthorized services inadvertently added to consumer bills were removed, Comcast—represented by FCC regular and first Enforcement Bureau Chief David Solomon—argued that the Commission itself “has cautioned against an expansive application of the Negative Option Billing Laws, stating that a broad reading of the rule could lead to harmful consequences.”  Moreover, Comcast asserted that “the Negative Option Billing Laws are not per se prohibitions, but instead are targeted only at affirmatively deceptive conduct on the part of cable operators, and Commission enforcement requires a demonstrated pattern of violation,” rather than an erroneous charge “occasioned by employee error” that does not involve deceit or intent.  For its part, the Commission asserted that it believes “the Customer Complaints and other facts adduced during the Investigation are evidence of violations of Section 623(f) of the Act and Section 76.981 of the Commission’s Rules.”

Moreover, the settlement requires that Comcast be required to comply with the terms of the Order and Consent Decree for an uncharacteristically long term—i.e., five years instead of the three years the Bureau has normally insisted upon.

In addition to the US$2.3M civil penalty, Comcast must implement a highly detailed compliance plan.  Although in many instances, Comcast is given until July 2017 to create and implement requisite processes, the level of detail applied to the cable company’s alleged transgressions is similar to that found in certain cramming and slamming settlements.  In those instances, however, the Commission is usually acting against less sophisticated targets with decidedly fewer resources that cannot retain compliance personnel with the expertise to design, develop, and implement their own expansive compliance plans.  Among other things, and as explained in five pages of detail in the Consent Decree, the company is required to:

obtain customers’ affirmative informed consent prior to charging them for new services or equipment; send customers an order confirmation, separate from any other bill, that clearly and conspicuously describes newly added services and equipment and their associated charges; offer mechanisms to customers that, at no cost, enable them to block the addition of new services or equipment to their accounts; implement a detailed program for redressing disputed charges in a standardized and expedient fashion; limit adverse actions (such as referring an account to collections or suspending service) while a disputed charge is being investigated; designate a senior corporate manager as a compliance officer; and implement a training program to ensure customer service personnel resolve customer complaints about unauthorized charges.

Going forward, it appears that the Commission will have a substantial amount of insight into the way the company conducts its business vis-à-vis its customer service responsibilities, in the form of annual reports and extended document retention requirements.

Lessons from the Settlement

Over the past two and a half years, it has become more apparent that the FCC is willing to apply old rules in new ways, and to continue to be an aggressive enforcer of the rules in general, but particularly when it comes to protecting consumers.  Although the Commission has issued Enforcement Advisories in the past, alerting companies that it is on the lookout for noncompliance in certain areas, this US$2M+ action is proof that regulatees should not wait for FCC warnings before ensuring they are compliant with the rules.  Companies should take heed and adopt a proactive approach to understanding the rules applicable to them based on their business operations.

ARTICLE BY Koyulyn K. Miller of Squire Patton Boggs (US) LLP

© Copyright 2016 Squire Patton Boggs (US) LLP

FCC’s Enforcement Bureau Commends PayPal for Modifying its User Agreement

We previously advised that the FCC’s Enforcement Bureau, in an unusual move, on June 11 published a letter it sent to PayPal warning that PayPal’s proposed changes to its User Agreement that contained robocall contact provisions might violate the TCPA.

FCC_LogoThese proposed revisions conveyed user consent for PayPal to contact its users via “autodialed or prerecorded calls and text messages … at any telephone number provided … or otherwise obtained” to notify consumers about their accounts, to troubleshoot problems, resolve disputes, collect debts, and poll for opinions, among other things. The Bureau’s letter highlighted concerns with the broad consent specified for the receipt of autodialed or prerecorded telemarketing messages and the apparent lack of notice as to a consumer’s right to refuse to provide consent to receive these types of calls.

On June 29, prior to the revisions coming into effect, PayPal posted a notice on its blog stating: “In sending our customers a notice about upcoming changes to our User Agreement we used language that did not clearly communicate how we intend to contact them.” PayPal clarified that it would modify its User Agreement to specify the circumstances under which it would make robocalls to its users, including for important non-marketing reasons relating to misuse of an account, as well as to specify that continued use of PayPal products and services would not require users to consent to receive robocalls.

The FCC’s Enforcement Bureau immediately put out a statement commending PayPal for its decision to modify its proposed contact language, noting that these changes to the User Agreement represented “significant and welcome improvements.” The Bureau’s very public actions on this matter signal to businesses everywhere of the need to review existing “consent to contact” policies. Certainly the FCC’s yet to be released Declaratory Ruling on TCPA matters that was voted on during a contentious FCC Open Meeting on June 18 may also invite that opportunity.

ARTICLE BY Laura H. Phillips of Drinker Biddle & Reath LLP

©2015 Drinker Biddle & Reath LLP. All Rights Reserved

FCC Chairman Proposes New TCPA Rules

The FCC is ready to rule on long-standing petitions seeking clarifications of the Telephone Consumer Protection Act and related FCC regulations. On May 27, 2015, FCC Chairman Tom Wheeler circulated a proposed regulatory ruling to fellow commissioners, which would address issues raised in more than 20 pending petitions. The fact sheet summarizing the chairman’s proposal foreshadows bad news for legitimate businesses using automatic telephone dialing technology.

FCC_Logo

The fact sheet lumps scammer calls like those from perky “Rachel” of the mysterious and ambiguous “Cardholder Services” with those from legitimate businesses. The fact sheet cites the 214,000 consumer complaints about robocalls. No breakdown is given as to how many of these complaints involved con artists and how many related to businesses calling, for example, to collect debt. The tone of the fact sheet provides no comfort. Its preamble states the plan is to “close loopholes and strengthen consumer protections.”

The FCC will vote on the new proposal during its Open Commission Meeting scheduled for June 18, 2015. In the meantime, companies using automatic telephone dialing technology should plan to take action to comply with whatever comes from the FCC. There will be no notice and comment period and whatever passes at the Open Commission Meeting will become effective immediately upon release.

New Provisions

If Chairman Wheeler’s proposals are adopted without changes, the new rules will provide:

  • Wireless and wired telephone consumers will have the right to revoke their consent to receive calls and text messages sent from autodialers in any reasonable way at any time. Many courts have concluded that consumers have a right to revoke consent. Some have said that revocation must be in writing. Some have said consent, once given, cannot be taken back. If this proposal passes, all courts likely will hold that consent may be revoked in any reasonable way at any time. This rule will have consequences beyond TCPA exposure. For example, it is likely to increase the cost of credit because creditors and debt collectors will have to employ more people to manually dial debtors who have failed to meet their obligations and utter the words, “Stop calling me!”

  • To prevent “inheriting” consent for unwanted calls from a previous subscriber, callers will be required to stop calling reassigned wireless and wired telephone numbers after a single request. It is not clear from the fact sheet what the individual on the other end of the line must say to notify the caller that they are not the person they seek to reach.

  • The TCPA currently prohibits the use of automatic telephone dialing systems to call wireless phones and to leave prerecorded telemarketing messages on landlines without consent. The current definition of an “automatic telephone dialing system” under the TCPA is “equipment which has the capacity to (A) to store or produce telephone numbers to be called, using a random or sequential number generator; and (B) to dial such numbers.” A 2003 FCC ruling focused on the use of the word “capacity” in the definition and broadly extended the definition to cover autodialers used to dial specific numbers. This ruling has resulted in inconsistent court decisions over whether a dialer must have a present capacity to so dial or whether a future capacity is sufficient for to trigger TCPA coverage. The new proposal appears to attempt to resolve the ambiguity by amending the definition of an “automatic telephone dialing system” to mean “any technology with the capacity to dial random or sequential numbers.” That is not much help. The industry needs an answer on the present versus future capacity issue. As it stands now, a court could conclude that a smartphone is an automatic telephone dialing system. The tone of the fact sheet suggests that this problem is not going to be solved in a way that is favorable to industry.

Existing Provisions Under TCPA

Chairman Wheeler’s proposal also provides for some very limited and specific exceptions for “urgent circumstances,” which may include free calls or text messages to wireless devices that alert consumers of potential fraud or that remind them of urgent medication refills. Consumers will still have an opportunity to opt-out of these types of calls and texts.

  • The new proposal will also leave many of the existing provisions of the TCPA intact:

  • The FTC will continue to administer the National Do-Not-Call Registry to prevent unwanted telemarketing calls

  • Wireless and home phone subscribers can continue to prevent telemarketing robocalls made without prior written consent

  • Autodialed and prerecorded telemarketing and information calls and text messages to mobile phones will still require prior consent

  • Political calls will still be subject to restrictions on prerecorded, artificial voice, and autodialed calls to wireless phones, but will continue to not be subject to the National Do-Not-Call Registry because they do not contain telephone solicitations as defined by FCC regulations

  • Consumers will still have a private right of action for violations of the TCPA along with statutory penalties

Implications

If adopted, the new regulations may significantly restrict the use of autodialing technologies by business. However, the devil will be in the details. Organizations should review the owners’ manual that came with their dialer. What can it actually do? In other words, what is its present and future capacity? Have those answers ready so you can act when the FCC rules. Companies should also have proper processes and systems in place to meet the consumer opt-out requirements of any new regulations. Policies should address steps to take when a called party claims that the number called no longer belongs to your intended recipient.

One thing is certain about these new rules, they will not stop scammers who use spoofed caller IDs and originate calls from outside of the United States and, therefore, outside of the jurisdiction of the FCC and/or FTC. They will just make to harder and more expensive for legitimate businesses to reach their customers.

ARTICLE BY Chanley T. Howell, Michael C. Lueder & Steven Millendorf of Foley & Lardner LLP

© 2015 Foley & Lardner LLP

Junk Fax Act Compliance: One Week Left to Request a Waiver for Non-Compliance

McDermott Will & Emery

Thursday, April 30, 2015, marks the last day a business can request a retroactive waiver for failing to comply with certain fax advertising requirements promulgated by theFederal Communications Commission (FCC). The scope of these requirements was clarified on October 30, 2014, when the FCC issued an Order (2014 Order) under the Junk Fax Prevention Act of 2005 (Junk Fax Act). The 2014 Order confirms that senders of all advertising faxes must include information that allows recipients to opt out of receiving future faxes from that sender.

The 2014 Order clarifies certain aspects of the FCC’s 2006 Order under the Junk Fax Act (the Junk Fax Order). Among other requirements, the Junk Fax Order established the requirement that the sender of an advertising fax provide notice and contact information that allows a recipient to “opt out” of any future fax advertising transmissions.

Following the FCC’s publication of the Junk Fax Order, some businesses interpreted the opt-out requirements as not applying to advertising faxes sent with the recipient’s prior express permission (based on footnote 154 in the Junk Fax Order). The 2014 Order provided a six-month period for senders to comply with the opt-out requirements of the Junk Fax Order for faxes sent with the recipient’s prior express permission and to request retroactive relief for failing to comply. The six-month period ends on April 30, 2015. Without a waiver, the FCC noted that “any past or future failure to comply could subject entities to enforcement sanctions, including potential fines and forfeitures, and to private litigation.”

ARTICLE BY

Julia Jacobson
Matthew R. Turnell
McDermott Will & Emery

FCC to Issue Net Neutrality Rules–Federal Communications Commission

Armstrong Teasdale Law firm

In February, Federal Communications Commission Chairman Tom Wheelerwill circulate a draft order regarding Net Neutrality to his four fellow commissioners. The Net Neutrality rules will govern whether Internet service providers (ISPs), such as Comcast or Verizon, can block access to websites or give preferential treatment to traffic from websites that pay for such treatment. To sustain the rules, the commission may change the regulatory classification of broadband service, subjecting it to rules, known as Title II, that apply to traditional phone service, rather than the less restrictive Title I rules that currently cover broadband. 47 U.S.C. §§ 153–621.

This will be the FCC’s third attempt at imposing Net Neutrality obligations. The U. S. Circuit Court reversed the commission’s first two attempts, finding that the rules were inconsistent with the classification of broadband as a Title I service. Comcast Corp. v. FCC, 600 F.3d 642 (D.C. Cir. 2010); Verizon v. FCC, 740 F.3d 623 (D.C. Cir. 2014). In the most recent opinion, the court struck down two rules, one prohibiting ISPs from blocking access to websites and one prohibiting them from unreasonably discriminating against traffic from websites or applications.

In response, the FCC published a proposal to reinstate the rules with small changes to address the Court’s concerns. The proposal was roundly criticized by Net Neutrality proponents, because it did not flatly outlaw discrimination. President Obama weighed in with a statement in favor of Net Neutrality rules. Recently, Chairman Wheeler has strongly indicated that the new proposal will reclassify broadband as a Title II service and include a rule banning unreasonable discrimination. The Chairman plans to circulate a draft order to the other commissioners, giving them a chance to comment on the draft and vote on the proposal at the FCC’s open meeting on February 26.

The effect of the rules is uncertain. Rules banning discrimination have been in place for only three of the 12 years since Net Neutrality was first proposed. Even though discrimination was allowed for more than nine years of that time, ISPs have not been able to convince content providers to pay for priority treatment. The new rules may outlaw activities that the ISPs do not have the market power to engage in anyway. But the rules will give content providers comfort that the ISPs will not be able to charge them for priority service in the future.

The bigger (and more uncertain) impact will arise if the FCC reclassifies broadband as a Title II service. If this happens, the Commission will probably forbear from applying most sections of Title II to broadband.  But the FCC’s authority to forbear from applying the statute in these circumstances is uncertain. Such a  decision  will be challenged on each section of Title II and the myriad of regulations under it. Litigation will last for years. If the FCC’s decision to forbear is reversed, the ISPs may be subject to some very onerous Title II regulations, such as obligations to resell their services, obligations to sell out of tariffs, and price restrictions. The outcome could be a messy hodge-podge of regulations that apply to some services and providers but not others.

ARTICLE BY
Andrew Crain
Charles W. Steese
Sandra L. Potter
OF
Armstrong Teasdale

FCC: The New Data Security Sheriff In Town

Proskauer Law firm

Data security seems to make headlines nearly every week, but last Friday, a new player entered the ring.  The Federal Communications Commission (“FCC”) took its first foray into the regulation of data security, an area that has been dominated by the Federal Trade Commission.  In its 3-2 vote, the FCC did not tread lightly – it assessed a $10 million fine on two telecommunications companies for failing to adequately safeguard customers’ personal information.

The companies, TerraCom, Inc. and YourTel America, Inc., provide telecommunications services to qualifying low-income consumers for a reduced charge.  The FCC found that the companies collected the names, addresses, Social Security numbers, driver’s licenses, and other personal information of over 300,000 consumers.  The data was stored on Internet servers without password protection or encryption, allowing public access to the data through Internet search engines.  This, the FCC found, exposed consumers to “an unacceptable risk of identity theft.”

The FCC charged the companies with violation of Section 222(a) of the Communications Act, which it interpreted to impose a duty on telecommunications carriers to protect customers’ “private information that customers have an interest in protecting from public exposure,” whether for economic or personal reasons.  Additionally, the companies were charged with violation of Section 201(b), which requires carriers to treat such information in a “just and reasonable” manner.

The companies were determined to have violated Sections 201(b) and 222(a) by failing to employ “even the most basic and readily available technologies and securities features.”  The companies further violated Section 201(b), the FCC found, by misrepresenting in their privacy policies and statements on their websites that they employ reasonable and updated security measures, and by failing to notify all of the affected customers of the data breach.

Commissioners Ajit Pai and Michael O’Rielly dissented, arguing that, among other things, the FCC had not before interpreted the Communications Act to impose an enforceable duty to employ data security measures and notify customers in the event of a breach.  Though now that the FCC has so-interpreted the Act, we can expect the FCC to keep its eye on data security.

The FCC made clear that protection of consumer information is “a fundamental obligation of all telecommunications carriers.”  Friday’s decision also makes clear that the FCC will enforce notification duties in the event of a breach, and will look closely at carriers’ privacy policies and online statements regarding data security.

ARTICLE BY

David A Munkittrick
OF
Proskauer Rose LLP