Our website uses cookies so we can analyse our site usage and give you the best experience. Click "Accept" if you’re happy with this, or click "More" for information about cookies on our site, how to opt out, and how to disable cookies altogether.

We respect your Do Not Track preference.

Making apps that don't suck too much Charles Mabbett
1 August 2014 at 09:44

2519 1 news feed elite 196 in 1 news

Apps can be convenient and fun to use. It is a world of incredible choice but one that also sets off privacy alarm bells. When a New Zealand news media organisation upgraded its app for Android phones earlier this year, one person was concerned enough to contact us.

The man said he had questions about why the app sought consent for some types of privacy permissions before it was downloaded onto a phone. The app asked for access to a number of data sources on his phone that he found “concerning and inappropriate” because it made no attempt to explain the reasons why it collected the data, or how it planned to protect that personal information.

Included among the permissions was access to a user’s social information such as the contacts list and the call log, access to the phone’s web browser history, and the app’s capacity to connect and disconnect the device from local Wi-Fi.

The man’s unease highlighted concerns around principles 1-5 of the Privacy Act. He said there was no justification given as to why those permissions were sought, and no assurance that the data would be secure or how it would be used.

The man believed the app’s permissions fell short of the expectations set out above. He had written to the media organisation for an explanation of the permissions and for a copy of the organisation’s data security provisions. When he did not get a response, he contacted us, although he was reluctant to make a formal complaint.

We decided to begin our own investigation into the app. Soon after, the man informed us he had heard back from the media organisation which said it had removed the contentious permissions from the app. Given that the news organisation had changed the app, we decided not to notify it of our investigation and we took no further action.

The case highlighted for us the growing fears about mobile apps and the range of permissions they seek. We decided we had to do more work at all sections of the app development spectrum - from the people who make them, the businesses that market them, to the consumers that use them.

We recently published our online Need to Know or Nice to Have guide for businesses and mobile app developers. You can find it here. The Asia Pacific Privacy Authorities (APPA) – an international privacy network that we belong to – also promoted the issue during Privacy Week in May with a ‘protect your privacy on your mobile device’ theme.

At the International Conference of Data Protection and Privacy Commissioners in Warsaw, Poland, last year, a resolution about the ‘appification’ of society was passed. It observed that app developers “are often unaware of the privacy implications of their work and unfamiliar with concepts like privacy by design and default”.

Smartphones have only been with us for a short time but millions have now been sold around the world. Some estimates are that there are nearly two billion smartphones in people’s hands and one in five people have at least one. The number of mobile apps has grown exponentially. It was estimated there were six million apps available in 2013 - a number that is growing by 30,000 a day.

Here’s the thing. Apps access and use your personal information and many will send it on to third parties. It is up to privacy regulators to remind app developers of their privacy obligations. Consumers, on the other hand, need to be mindful of the terms and conditions that come with apps - in many cases these might be more than they seem.

Back