Practical guidance for developers to shape their GDPR strategy
18 Jul 2018

What final steps should system architects and developers take now to ensure they have all bases covered? Simon Crossley, director of engineering, plots a pragmatic path.
Despite the huge volume of publicity there’s been around General Data Protection Regulation (GDPR), there was a heightened sense of concern at a developer event I attended recently (the deadline for compliance is May 25).
At the end of my session, a number of people came forward, asking for clear guidance on what GDPR means at a practical level for developers and architects working with people’s personal data. Despite having made various preparations, they wanted to understand how other companies are addressing the common problems, the recommended thought processes when evaluating work, and how to more fully address the risks and issues in their decision-making.
Please login to comment.
Comments