Data privacy requires precise legal and technical language. Practise the collocations used in GDPR documentation and compliance discussions.
0 / 5 completed
1 / 5
Fill in: 'Our platform ___ personal data in strict compliance with GDPR.'
We 'handle personal data' — 'handle' is the GDPR-aligned collocation found in legal and compliance documentation. 'Manages' is also common; 'processes' is a GDPR term (data processing) but collocates more naturally with 'data processing activities'; 'deals with' is informal.
2 / 5
Fill in: 'The DPO is responsible for ___ the data retention policy across all departments.'
We 'enforce a policy' — 'enforce' means to ensure compliance and take action when the policy is breached. 'Implementing' refers to introducing the policy; 'applying' is passive; 'following' is what individuals do, not what the DPO does organisation-wide.
3 / 5
Fill in: 'Only authorised users should be ___ access to sensitive customer records.'
We 'grant access' — 'grant' is the standard collocation in access-control and data-governance language, reflecting a formal permission decision. 'Give access' is informal; 'allowed access' and 'permitted access' are grammatically correct but less idiomatic in technical contexts.
4 / 5
Fill in: 'The system is configured to ___ logs for no more than 90 days.'
We 'retain data' — 'retain' is the GDPR and ISO 27001 standard verb for keeping data for a defined period. 'Keep' and 'store' are informal; 'hold' is used in legal contexts ('hold data') but 'retain' is the dominant compliance collocation.
5 / 5
Fill in: 'Before sharing the dataset externally, the team must ___ all personal records.'
We 'anonymise records' — 'anonymise' is the precise data-privacy collocation for removing identifying information from data. 'Remove records' deletes them entirely; 'delete records' eliminates data; 'clean records' is informal and usually refers to data quality, not privacy.