Determann’s Field Guide to International Data Privacy Law Compliance

Determann’s Field Guide to International Data Privacy Law Compliance

Lothar Determann

Companies, lawyers, privacy officers, developers, marketing and IT professionals face privacy issues more and more frequently. Much information is freely available, but it can be difficult to get a grasp on a problem quickly, without getting lost in details and advocacy. This is where Determann’s Field Guide to International Data Privacy Law Compliance comes into its own – helping to identify issues and provide concise practical guidance in an increasingly complex field shaped by rapid change in international laws, technology and society.

Chapter 3: Drafting Documentation

Lothar Determann

Subjects: law - academic, information and media law, internet and technology law, law -professional, technology, media and telecommunications law


Before you set out to create documentation relating to privacy law compliance and you put pen to paper, consider two threshold questions: Why are you creating the document? Who is your audience? After answering these two threshold questions, you can proceed to preparing an outline and then consider the next two questions: What requirements and considerations apply regarding content, form and organization? What traps and pitfalls should you avoid? In this chapter, you will find suggestions on how to answer these threshold questions, suggestions regarding documentation that companies tend to need and not need, as well as guidance and considerations regarding the drafting of documents. 3.1 3.01 Why are you creating the document? As a general matter, businesses prefer to create less rather than more documentation for a number of reasons: it takes resources to prepare, review, follow and maintain documentation. Published documentation can limit what a company may do with personal data. Plaintiffs and regulators may exploit any failures to comply with promises and representations in written documentation. Companies create data privacy-related documentation primarily for three reasons: laws, market demands and organizational necessities. More specifically: To satisfy legal requirements or enjoy benefits that are legally conditioned on having certain documentation 3.02 DETERMANN PRINT.indd 48 06/07/2012 13:43 Drafting documentation · 49 To respond to market demands (for example, from customers, suppliers, or employees) To communicate and memorialize rules, instructions and restrictions internally within the organization. Sometimes, it can be possible and efficient to pursue more than one of these three...

You are not authenticated to view the full text of this chapter or article.

Elgaronline requires a subscription or purchase to access the full text of books or journals. Please login through your library system or with your personal username and password on the homepage.

Non-subscribers can freely search the site, view abstracts/ extracts and download selected front matter and introductory chapters for personal use.

Your library may not have purchased all subject areas. If you are authenticated and think you should have access to this title, please contact your librarian.

Further information