In this week’s episode of In-Ear Insights, Katie and Chris tackle the thorny issues of user data privacy and what expectations a company should plan to meet when it comes to protecting users – even when the users make bad choices. Learn the different types of private data – PII, SPI, and PHI – as well as hear about a massive dataset in the wild that probably shouldn’t be.

Sponsor: Knowledge Matters

In-Ear Insights is brought to you by Knowledge Matters.

Do you teach marketing at the collegiate level? Imagine using immersive, visual, interactive marketing simulations designed for today’s digitally-native students.

Besides bringing marketing concepts to life, it’s cloud based and includes automatic grading and easy integration with all the popular collegiate learning management systems such as Canvas, Blackboard or Moodle.

If you would like to check out case simulations that cover all the key concepts for an Intro to Marketing course like Pricing, Promotion, Market Research, Market Segmentation, and much more, sign up today for a demo at: www.knowledgematters.com/podcast

Listen to the audio here:

http://traffic.libsyn.com/inearinsights/tipodcast-dataprotection.mp3

Download the MP3 audio here.

Need help with your company’s data and analytics? Let us know!

Join our free Slack group for marketers interested in analytics!

Machine-Generated Transcript

What follows is an AI-generated transcript. The transcript may contain errors and is not a substitute for listening to the episode.

Christopher Penn

In this week’s episode of insights, we are talking about data protection users, user responsibilities, vendor responsibilities, and all things related to essentially preventing marketing disasters, because the data that you are not protecting, to give a bit of context, a little bit of table setting, we were looking at a massive data set released by a consultant who mind the public, completely public, no API keys needed no security violations, no hacking, this, this person pulled out 10 billion, then mo transactions from then most public logs of what people were paying money for. Everything from paying for pizza, to paying for intimate relationships with other people. And so we want to talk today about what a sort of the things that are important to keep in mind when you’re working with user data, everything from the marketing aspect to the system aspects to gosh, you just shouldn’t have done that. So Katie, why don’t you kick us off with when you hear about this kind of a data set, what comes to mind,

Katie Robbert

my first thought was that what’s the responsibility of the company to protect their user data, the fact that somebody can just without any sort of security keys download, that type of personally identifying information to that level of detail to me is super concerning. And something you would shared with me was that actually with invent mo and and it’s not a system that I use, with invent Mo, it’s the user who actually has to check certain boxes, and the ability to keep their data private is not the default setting. And that was just hugely concerning to me. And I understand, as long as companies, you know, bury in the fire print of, you know, their terms and their use in their privacy of things that people are never going to read that this is the way that they operate, then technically, it’s all legal. But does that make it right, knowing that the consumer isn’t going to read all of that paperwork, when they just want to send money to someone else for buying them a pizza that night?

Christopher Penn

So originally, event mode, I think the idea was it was supposed to be this, we can debate the wisdom of this idea. It was supposed to be a social network for payment, where you could see what your friends were doing. You know, and and be able to point out like a you hung out with, you know, so last night and bought like three things of