Revenue plan pushes data protection limit


Revenue plan pushes data protection limit

We should all be alarmed by the Inland Revenue's refusal to rule out the possibility that tax work might in future be contracted out abroad.

The Revenue has long maintained that no sensitive personal data should be allowed outside the UK. Now there are signs on its Web site that it is moving towards a relaxation of that policy.

The Data Protection Act 1998 states that "personal data shall not be transferred to a country or territory outside the European Economic Area", though this principle is open to exemptions and interpretations in certain cases. It is to these exemptions and interpretations that the Revenue would need to look if it wished to enter into a contract that sees records outsourced to other continents.

In other words, the Government may countenance operating out on the margins of UK legislation, which would result in the bending of UK data protection principles, in order to process sensitive data more cheaply.

What if IT workers in another country pass on data for gain?
Currently, anyone leaking or selling on sensitive revenue information would be subject to criminal proceedings under UK law. But no such legislation may apply overseas. The Revenue denies that anything other than development work could be sent abroad. However, it admits on its Web site that "all current arrangements are being reviewed".

Should live tax records go abroad, the Revenue will have set a worrying precedent. What data will follow them across the globe - health data? Criminal records? Whatever their nature, they would never be as secure as they are today.

Email Alerts

Register now to receive IT-related news, guides and more, delivered to your inbox.
By submitting your personal information, you agree to receive emails regarding relevant products and special offers from TechTarget and its partners. You also agree that your personal information may be transferred and processed in the United States, and that you have read and agree to the Terms of Use and the Privacy Policy.

This was first published in April 2002


COMMENTS powered by Disqus  //  Commenting policy