Big Problems, Short Codes: A Potential Solution to GDPR's Info Privacy Challenges

Looking ahead to GDPR, ARMs and trading venues are developing ways to better protect the personal data they are required to collect, report and store under Mifid II, while investment firms tasked with providing personally identifiable information to the venues they trade on, are pushing for an industry-wide solution. Kirsten Hyde reports.

The EU’s regulators insisted on putting personal data requirements into Mifid II, which came into effect on January 3, because they wanted a means of more quickly identifying individuals in cases of suspected market abuse. 

Under Mifid II’s RTS 22 requirements for transaction reporting, investment firms must include personal data and identifiers—such as passport numbers, national ID numbers or tax codes—of the client and the trader responsible for the investment decision and execution of a

Only users who have a paid subscription or are part of a corporate subscription are able to print or copy content.

To access these options, along with all other subscription benefits, please contact [email protected] or view our subscription options here:

You are currently unable to copy this content. Please contact [email protected] to find out more.

To continue reading...

You need to sign in to use this feature. If you don’t have a WatersTechnology account, please register for a trial.

Sign in
You are currently on corporate access.

To use this feature you will need an individual account. If you have one already please sign in.

Sign in.

Alternatively you can request an individual account here: