13 November 2026

Notice of Security Incident at TwineData

TwineData provides identity data that helps companies connect and measure their digital advertising. The company was acquired by ID5 in October 2025. Since then, ID5 has initiated a deep compliance program to bring TwineData in line with its own privacy standards. This work has included encrypting directly identifiable information, sunsetting many audience categories, and simplifying individuals' data deletion requests at any time through the TwineData opt-out portal.

On November 9, ID5 identified that a Russia-based criminal hacking group had used stolen TwineData credentials to access cloud storage that TwineData uses to deliver audience data to clients and receive data from suppliers. The credential has since been disabled.

Based on our investigation to date, the data accessed mostly consisted of pseudonymous identifiers, such as hashed email addresses and mobile advertising IDs, linked to audience segments for individuals in the United States and Canada. It did not include any sensitive data. ID5’s own systems and the ID5 ID were not affected by this incident.

We have informed our clients and data partners directly. In addition to disabling the credential involved, we are replacing all access credentials, including those where no issue was found, and reviewing every access point to remove any that are no longer needed. We are adding additional security controls across our systems and completing an extensive forensic analysis to fully understand the incident and prevent it from happening again.

Privacy is at the core of how ID5 operates, and our standards are among the strongest in the industry. ID5 minimizes the data it holds, excludes sensitive categories, deletes data after 100 days, and honors individuals’ choices. This attack reinforces our conviction in privacy-enhancing technologies, and we will accelerate the deployment of ID5’s technologies and practices within TwineData.

Our investigation is ongoing, and we will update this statement if we learn new information. For questions about the incident, please contact ciso@id5.io.