Practise the standard verbs for handling a GDPR subject access request correctly.
0 / 5 completed
1 / 5
Fill in: 'We ___ every subject access request within the statutory one-month window, since missing the legal deadline itself becomes a separate compliance problem.'
We 'process a request' — the standard, simple collocation for handling a data access request through to completion. The other options are less idiomatic here.
2 / 5
Fill in: 'Treating a subject access request as low priority can ___ the statutory deadline missed entirely, turning a routine request into an active regulatory risk.'
We say a deprioritised request will 'leave' the legal deadline missed — the standard, natural collocation for the resulting compliance risk. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ the requester's identity carefully before releasing any personal data, since handing information to the wrong person is itself a serious breach.'
We 'verify identity' — the standard, simple collocation for confirming who is actually making a data request. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ every system holding personal data about that individual, not just the obvious primary database, since a partial response doesn't actually satisfy the request.'
We 'search a system' — the standard, simple collocation for locating all relevant personal data across an organisation. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ the final response in plain, readable language, rather than a raw data export nobody outside engineering could actually make sense of.'
We 'compile a response' — the standard, simple collocation for assembling a clear, complete answer to a data request. The other options aren't idiomatic here.