[{"description":"i-Dressup and a data security mess-up lfair April 24, 2019 | 3:08PM i-Dressup and a data security mess-up By Lesley Fair Kids love to play dress-up, but parents wouldn’t want them rummaging through the attic or climbing to the top shelf of the wardrobe without permission and proper supervision. The i-Dressup.com website offered users – including children – a virtual way to play dress-up and design clothes without those potential dangers. But according to an FTC complaint, Unixiz, Inc. , the company behind i-Dressup, violated the Children’s Online Privacy Protection Act in ways that created different kinds of risks. COPPA puts two separate sets of protections in place to help keep parents in control of personal information collected from their kids online. First, COPPA-covered companies must clearly disclose their information policies and get parental consent before collecting personal information from children under 13. Second, companies must provide reasonable and appropriate security for the data they collect. According to an FTC settlement, i-Dressup fell short on both COPPA requirements. The complaint alleges i-Dressup failed to provide sufficient notice on its site of the information it collected online from kids, how it used it, its disclosure practices, and other specifics required by the COPPA Rule. The company’s direct notices to parents were deficient, too. Among other things, they didn’t include the COPPA-required statement that if parents don’t provide consent within a reasonable time, i-Dressup will delete their online contact information from its records. Stick with the story because that failure turned out to be particularly troubling. In addition to letting users play online games, i-Dressup featured a community where they could “explore their creativity and fashion sense with unique personal profiles” and interact with others. To register, i-Dressup required people to submit a user name, password, birthdate, and email address. If the birthdate indicated the person was under 13, the email field changed to “Parent’s Email.” Once the under-13 user filled in the required fields and clicked “Join Now,” i-Dressup collected the personal information and sent a message to the address entered into the Parent’s Email field. The person receiving the email could consent by clicking the “Activate Now!” button. However, if the parent didn’t give consent, i-Dressup retained the personal information it had collected from the child online. The FTC says the company’s failure to delete that information violated Section 312.5(c)(1) of the COPPA Rule. In addition to violating COPPA’s parental consent provisions, i-Dressup allegedly violated the Rule’s data security requirements . According to the FTC, i-Dressup stored and transmitted users’ personal information (including passwords) in plain text. In addition, the company failed to perform network vulnerability testing of its network, even for well-known threats like SQL attacks; it didn’t implement an intrusion detection and prevention system; and it didn’t monitor for potential security incidents. The upshot? The company learned that a hacker had gained entry to its network and accessed information about 2.1 million users, including approximately 245,000 users who indicated they were under 13. To settle the case , i-Dressup and its owners will pay a $35,000 civil penalty. They’re also prohibited from violating COPPA in the future, and can’t sell, share, or collect any personal information until they implement a comprehensive data security program and get independent biennial assessments. In addition, they’ll have to provide the FTC with an annual certification of compliance. The message for sites and operators covered by COPPA is that an effective system of parental consent is only the first step toward compliance. Section 312.8 of the COPPA Rule also requires you to “establish and maintain reasonable","titre":"i-Dressup and a data security mess-up","pubDate":"Thu, 08 Oct 2026 08:06:59 +0200","id":3203250,"source":"FTC USA Business Blog Posts","url":"https://www.ftc.gov/business-guidance/blog/2019/04/i-dressup-data-security-mess"},{"titre":"Stick with Security: Require secure passwords and authentication","id":3197409,"pubDate":"Mon, 05 Oct 2026 08:07:08 +0200","description":"Stick with Security: Require secure passwords and authentication lfair August 11, 2017 | 10:47AM Stick with Security: Require secure passwords and authentication By Thomas B. Pahl, Acting Director, FTC Bureau of Consumer Protection To make it harder for hackers to bluff their way onto a computer network, careful companies follow the advice of Start with Security and require strong authentication practices . We’ve considered FTC settlements, closed investigations, and the questions we get from businesses about implementing good authentication “hygiene.” Here are some tips on using effective authentication procedures to help safeguard your network. Insist on long, complex, and unique passwords. A password’s very reason for being is to be easy for a user to remember, but hard for a fraudster to figure out. Obvious choices like ABCABC, 121212, or qwerty are the digital equivalent of a “hack me” sign. Furthermore, experts have determined that passphrases or longer passwords are generally harder to crack. The smarter strategy is for companies to think through their standards, implement minimum requirements, and educate users about how to create stronger passwords. Also, when you install software, applications, or hardware on your network, computers, or devices, change the default password immediately. And if you design products that require consumers to use a password, configure the initial set-up so they have to change the default password. Example: A staff member attempts to select payroll as the password for the database that includes employee payroll information. The company sets up its system to reject an obvious choice like that. Example: To access the corporate network, a business allows employees to type in their username and a shared password common to everyone who works there. Employees are also allowed to use that shared password to access other services on the system, some of which contain sensitive personal information. The more prudent policy would be to require strong, unique passwords for each employee and to insist that they use different passwords to access different applications. Example: At a staff meeting, a company’s IT manager offers tips for employees about good password hygiene. She explains that passphrases or longer passwords are better than short passwords based on standard dictionary words or well-known information (for example, a child’s name, a pet, a birthday, or a favorite sports team). By establishing a more secure corporate password standard and educating employees about implementing it, the IT manager is taking a step to help her company reduce the risk of unauthorized access. Store passwords securely. A company’s first line of defense against data thieves is a workforce trained to keep passwords secret. But even the strongest password is ineffective if an employee writes it on a sticky note on her desk or shares it with someone else. Train your staff not to disclose passwords in response to phone calls or emails, including ones that may appear to be coming from a colleague. Con artists have been known to impersonate corporate officials by spoofing phone numbers or email addresses. A compromised password poses a particular risk if it can be used to open the door to even more sensitive information – for example, a database of other user credentials maintained on the network in plain, readable text. Make it difficult for data thieves to turn a lucky password guess into a catastrophic breach of your company’s most sensitive data by implementing policies and procedures to store credentials securely. Example: A new employee gets a call from someone who claims to be the company’s system administrator. The caller asks him to verify his network password. Because the new staffer learned about impersonation scams at an in-house security orientation, he refuses to disclose his password and instead reports the incident to the appropriate person in the company. Example: A company keeps user credentials and other passwords in plain","source":"FTC USA Business Blog Posts","url":"https://www.ftc.gov/business-guidance/blog/2017/08/stick-security-require-secure-passwords-authentication"},{"titre":"StubHub Refunding $10 Million in Fees to Consumers After Deceptive Ticket Pricing","pubDate":"Fri, 10 Apr 2026 08:08:44 +0200","id":2818173,"description":"StubHub, the nation’s largest ticket exchange and resale ticket provider, will pay $10 million to settle Federal Trade Commission charges that the company violated the FTC Act and the agency’s Rule on Unfair or Deceptive Fees by deceptively advertising ticket prices on its website without clearly and conspicuously disclosing up-front how much consumers actually would pay, including all mandatory fees. “The Commission’s Fees Rule makes it very clear that the total price of live-event tickets must be disclosed up-front to enable consumers to make fully informed purchasing decisions,” said Christopher Mufarrige, Director of the FTC’s Bureau of Consumer Protection. “Price transparency is essential to a free and competitive marketplace. Today’s settlement underscores the Commission’s commitment to ensuring that consumers pay the price they are promised.” The FTC’s action against StubHub Holdings, Inc., follows a  warning letter the agency sent the online ticket platform in May 2025 stating that multiple prices displayed on its website appeared to be in violation of the Fees Rule. Under the Rule, which took effect on May 12, 2025 , it is an unfair and deceptive practice for any business to offer, display, or advertise the price of a live-event ticket without clearly, conspicuously, and most prominently disclosing the total price, which the Rule defines as “the maximum total of all fees or charges a consumer must pay for any good(s) or service(s) and any mandatory ancillary good or service.” Misrepresenting prices also violates the FTC Act. Today’s action also follows the Administration’s recent Executive Order on Ticketing , which includes a directive for the FTC to “take appropriate action . . . to ensure price transparency at all stages of the ticket-purchase process, including the secondary ticketing market.” According to the Commission’s complaint , in mid-May 2025—after the Rule went into effect—StubHub advertised its ticket prices without disclosing the full price consumers would actually pay by failing to include mandatory fees and to disclose the total price everywhere it displayed prices. Specifically, the FTC alleges StubHub failed to provide the total price for tickets—including high-demand National Football League tickets in the lead-up to when the NFL schedule was announced on May 14, 2025—in the first three pricing displays on its website. On the initial two pricing displays, in numerous instances, the advertised price did not include all mandatory fees, and StubHub did not disclose the total price. On the third pricing display, StubHub listed multiple fees and charges but did not disclose the total price. The proposed order settling StubHub’s alleged violations of the FTC Act and the Fees Rule requires the company to pay $10 million, which the company will use to provide monetary relief to eligible consumers through a settlement and consumer redress distribution program. The order also prohibits StubHub from misrepresenting the total price of any good or service; any fee or charge, including its nature, purpose, amount, or refundability, as well as why the fee or charge is being imposed; the final payment amount for any transaction; and any other material fact including those related to refunds or cancellations. The proposed order also prohibits StubHub from: Offering, displaying, or advertising any price of a good or service without clearly and conspicuously disclosing the total price; Failing to disclose the total price more prominently than any other pricing information; Failing to clearly and conspicuously disclose the amount of any fees or charges that have been excluded from the total price and what they are for, as well as the final payment amount—before the consumer agrees to pay for a product or service; and Violating the Commission’s Fees Rule. Within 90 days of the date of the order StubHub must provide redress to two groups of eligible","source":"Federal Trade Commission - Protecting America's Consumers","url":"https://www.ftc.gov/news-events/news/press-releases/2026/04/stubhub-refunding-10-million-fees-consumers-after-deceptive-ticket-pricing"},{"pubDate":"Mon, 20 Jan 2025 15:49:16 +0100","id":1857297,"titre":"CEF 2024: EDPB identifies challenges to the full implementation of the right of access","description":"Brussels, 20 January - The European Data Protection Board (EDPB) has adopted a report on the implementation of the right of access by controllers . The report summarises the outcome of a series of coordinated national actions carried out in 2024 under the Coordinated Enforcement Framework (CEF). It lists the issues that were observed for some controllers, along with a series of recommendations to help them implement the right of access. A central element is controllers’ awareness of the EDPB Guidelines 01/2022 on data subjects rights – Right of access and whether these guidelines were followed in practice. EDPB Deputy Chair Zdravko Vukíc said: “The CEF is a valuable initiative that helps strengthen the cooperation among Data Protection Authorities (DPAs): by tackling selected topics in a coordinated fashion, they achieve greater efficiency and more consistency. How controllers implement the right of access lies at the heart of data protection and it is one of the most frequently exercised data subject rights.” Throughout 2024, 30 DPAs across Europe launched coordinated investigations into the compliance of controllers with the right of access, by opening formal investigations, assessing whether a formal investigation was warranted and/or carrying out fact-finding exercises.  A total of 1,185 controllers, consisting of small and medium-sized enterprises (SMEs) and big companies active in different industries and fields, as well as various types of public entities, responded to the action. Areas of improvement and main challenges The results suggest that more awareness raising about Guidelines 01/2022 is necessary , both at national and EU level, as the guidelines help controllers implement the right of access, explain how exercising this right can be made easier, and list the exceptions and limitations of the right to access. As a result of the 2024 CEF action, seven challenges were identified. One of them is the lack of documented internal procedures to handle access requests. In addition, inconsistent and excessive interpretations of the limits to the right of access were also observed, such as overly relying on certain exceptions to automatically refuse access requests. Another example is the barriers that individuals could encounter when exercising their right of access, such as  formal requirements or being requested to provide excessive identification documents. For each challenge identified, the report provides a list of non-binding recommendations to be taken into account by controllers and DPAs. Positive findings Despite the existing challenges, two thirds of participating DPAs evaluated the level of compliance of responding controllers with respect to the right of access from ‘average’ to ‘high’. One important factor identified as having an impact on the level of compliance was the volume of access requests received by controllers, as well as the size of the organisation. More specifically, large-sized controllers or controllers receiving more requests were more likely to reach a higher level of compliance than small organisations with less resources. Positive findings were observed across Europe. These include the implementation of best practices by controllers, such as user-friendly online forms enabling individuals to submit an access request easily as well as self-service systems to allow individuals to autonomously download their personal data in a few clicks and at any time. Background and next steps The CEF is a key action of the EDPB under its 2024-2027 Strategy, aimed at streamlining enforcement and cooperation among DPAs.  In the past three years, two previous CEF actions were carried out. The results of these national actions are aggregated and analysed together to generate deeper insight into the topic and allowing for targeted follow-up on both national and EU level. In 2023, the EDPB published the report on its first coordinated action on the use of cloud-based services by the public sector . In 2024, the EDPB also published the","url":"https://www.edpb.europa.eu/news/news/2025/cef-2024-edpb-identifies-challenges-full-implementation-right-access_en","source":"EDPB News"}]