How to Read Privacy Policies for Software

How to Read Privacy Policies for Software

Each time we sign up to a new productivity software, we tend to skip past the privacy policy and even terms and conditions. Even when we click into one, we freak out and leave quickly as we’re overloaded with information about our data and the many ways it is being used.

Things are getting better but many of you find this an issue and want to become more conscious about your data and how it is being used. So, this week, we chatted with Thomas Codevilla from SK&S Legal to chat about privacy policies and how to spot red flags.

First off, thanks to Thomas for taking the time out to jump on a call and chat about this.

All You Need to Know From Our Chat

  • You should be able to find the information that they take, how long they take it and what they do with this information.

  • Privacy policies should NOT be hard to read or understand - this is an indication of poorly formed and brought together policy. They should be explained in plain English.

  • With productivity software, you should look for key things like “Is a human reading my notes”, “is my calendar events being used for advertising” and other such items.

  • If a policy states the general use of your email, the company might be using your email for anything - for advertising and other such external use.

  • Try and find the contact information for the company - this is a must.

  • Broken up privacy policies are better as they help you to understand it.

  • If they are in the EU and DO NOT mention GDPR - you should be cautious. This is really important as they need to be in compliance.

  • Look for cookies and targeted ads and how they will use your email or data to apply this to their own internal systems.

  • If a company takes time to register for Privacy Shield and other such privacy government run programmers, this is good news.

Weekly News: Notion 2.6, Evernote’s Final Releases and Confluence challenges...

Weekly News: Notion 2.6, Evernote’s Final Releases and Confluence challenges...