Question B: What is P3P (Platform for Privacy Preferences), and how do we implement it on our Web site?

Our advice: P3P is an XML-based mechanism which enables a user's web browser to retrieve and interpret your Web site privacy policy. The browser can automatically compare your privacy policy with the user's preference settings, warn the user if your policies conflict with their preferences, and restrict the use of cookies. Most Webmasters first became aware of P3P in late 2001, when Microsoft Internet Explorer version 6.0 (IE6) appeared. Because IE6 restricts the use of cookies based on a Web site's P3P policies (or lack thereof), some Web sites stopped working properly with IE6's default settings.

As a formal, structured specification, P3P requires you to describe your privacy policy in explicit detail. Most elements of P3P are straightforward, such as giving the legal name of your business, how to contact you off-line, and where on your Web site to find your human-readable privacy policy. The policy also should specify how disputes will be resolved. You must then identify each type of information you collect, why you collect it, who will have access to it, and how long it will be retained. This includes data that's automatically collected in server logs, such as IP addresses. You can, and should, define different policies for different areas of your Web site (e.g., informational pages versus customer order-entry).

There are a variety of tools and services--some free, some not--that you can use to construct your P3P files after you've collected your policy details. Then load the files into the specified location on your Web site, test it using the World Wide Web Consortium's P3P Validator (or other tool), and you're in business.

-- Peter Schay

Question C: How do we ensure that our employees don't violate our privacy policies?

Our advice: People are more sensitive about their privacy than ever. Between the Health Insurance Portability and Accountability Act on one hand, and the Patriot Act on the other, privacy guidelines are becoming more significant to the business world. There are two components to the enforcement of any corporate privacy policy: technical and procedural. Both must be in place to ensure proper compliance with corporate privacy policies.

The technical component, which can be as draconian or liberal as you wish, doesn't assume a level of trust on the part of your staff. The software either does its job or not. If you do have a policy breach, then you have the evidence to sanction the parties responsible. Watch out for overly complex technical policies, however. If the technical solution makes it difficult for users to do their jobs, users will fix the problem--you just might not like their fix! While technical methods involve combinations of setting appropriate access permissions on the data, user authentication, encryption, usage auditing, and other standard techniques, unless you have a good human-resource policy to match, compliance can be painfully difficult to enforce.

The trickier, but equally important, component is the creation of enforceable and enforced human-resource policies that reflect the stated goals of your company. Of course, having the employees sign binding contracts with sanctions for violating the privacy policies is crucial. In addition, many companies impose privacy policies by limiting the right to use sensitive information to only people who have job requirements for access. The "need to know" methodology has long been used in military and government circles as a technique to limit the exposure of sensitive data. As one wag recently put it, "Those who violate the policies are shot and killed. This does two things: thins the herd and sends a message to the rest." That approach may be extreme, but the level of compliance would, not doubt, be extremely high!

Take advantage of the standard technical systems to insure compliance, but be prepared to back up your policy enforcement with matching compulsory human resources policies. Only then will your staff will get the message that your privacy policy is important, and that you're serious about the reputation and trustworthiness of your company in its ability to handle personal data appropriately.

-- Beth Cohen

Sourabh Hajela, TAC Expert, has more than 15 years of experience in strategy, planning, and delivery of IT capability to maximize shareholder value for corporations in major industries across North America, Europe, and Asia. He is a member of the faculty at the University of Phoenix, where he teaches courses in strategy, marketing, E-business, and leadership. Most recently, he was VP and the head of E-business with Prudential Financial.

Peter Schay, TAC executive VP and chief operating officer, has 30 years of experience as a senior IT executive in IT vendor and research industries. He was most recently VP and chief technology officer of SiteShell Corp. Previously at Gartner, he was group VP of global research infrastructure and support, and launched coverage of client/server computing in the early 1990s.

Beth Cohen, TAC Thought Leader, has more than 20 years of experience building strong IT delivery organizations from user and vendor perspectives. Having worked as a technologist for BBN, the company that literally invented the Internet, she not only knows where technology is today but where it's heading in the future.