FTC Warns That Hashing Data is Not Anonymization - Articles

Articles

Stay at the forefront of the consumer insights and analytics industry with our Thought Leadership content. Here you’ll find timely updates on the Insights Association’s advocacy efforts, including the latest legislative and regulatory developments that impact how we work. In addition, this section offers expert perspectives on innovative research techniques and methodologies, as well as valuable analysis of evolving consumer trends. Together, these insights provide a trusted resource for professionals looking to navigate change, elevate their practice, and shape the future of our industry.

FTC Warns That Hashing Data is Not Anonymization

FTC Warns That Hashing Data is Not Anonymization

The Federal Trade Commission (FTC) recently sent a reminder that “hashing” personal data is not as protective as companies may think.

As explained in a blog post from the FTC’s Office of Technology staff, “Hashing involves taking a piece of data—like an email address, a phone number, or a user ID—and using math to turn it into a number (called a hash) in a consistent way: the same input data will always create the same hash. For example, hashing the fictional phone number “123-456-7890” transforms it into the hash “2813448ce6316cb70b38fa29c8c64130”, a hexadecimal number that might appear random, but is always what someone gets when they hash that phone number. “

Since hashed data "appears meaningless and seemingly can’t be used to find the original phone number, companies often claim that hashing allows them to preserve user privacy."

Unfortunately, the FTC staff warn, this does not make the data anonymous. Hashed data “can still be used to identify users, and their misuse can lead to harm. Companies should not act or claim as if hashing personal information renders it anonymized. FTC staff will remain vigilant to ensure companies are following the law and take action when the privacy claims they make are deceptive.”

Hashing can “obscure how a user identifier appears,” but “it still creates a unique signature that can track a person or device over time.” Hence, the FTC warned companies against relying “on hashing to reduce data sensitivity.”

As examples, the FTC blog cited the 2015 Nomi case, the 2022 BetterHelp case, the 2023 Premom case, and the 2024 InMarket case.

This is all a helpful reminder that what insights professional might think is personally identifiable often differs from what regulators and enforcers think.

Insights Association members should review IA compliance info and guidance on a range of privacy and data security issues, consider their professional and cyber liability insurance, look into ISO 27001 certification for data security, revisit/review their privacy policies, and review and update contracts and policy clauses.

This information is not intended and should not be construed as or substituted for legal advice. It is provided for informational purposes only. It is advisable to consult with private counsel on the precise scope and interpretation of any laws/regulation/legislation and their impact on your particular business.

Related

Share

Login

Members only Article - Please login to view
  • Back to top