In planning the upcoming All Analytics Academy program: Data Privacy for You, for All, we chose to look at some of the faces of data privacy. We have sessions focused on protecting the privacy of customers and of employees. Our five expert presenters will look at building privacy into the computing infrastructure and corporate processes. We will look at the privacy considerations for companies doing business on a multinational scale, and at how marketers can balance the need to strengthen brand awareness while not abusing their lists.
Then there are the faces of those who are responsible for privacy. It might be easy to point to someone with a title like chief privacy officer or someone in legal who writes policies or even the chief security officer (CSO).
But really, privacy is ingrained in all of our jobs. If we cut corners for the sake of efficiency and thus put customer data at risk, are we doing our jobs? If the CEO and CIO place unrealistic deadlines on the dev team to get an application out the door without additional testing, how can any of the parties say they did their job? If that marketing intern breaks policy and saturates a list with emails, how can we say they are doing their job?
Oh, everyone has their fallback excuses: "We'll fix that bug later," "But I had to send it today," "Nobody complained last time."
As your mom might have said, "Excuses don't cut it."
We have to own privacy, all of us. We have to treat the data of our customers and coworkers as we would want someone to treat ours. You know, the old "do unto others" thing. So, even if you don't have "privacy" in your title or job description, check out the agenda for the A2 Academy that launches on Tuesday. I'm sure you will find a topic or two that can help you do your job better.