4 Questions to Ask Before You Give a New App Access to Your Personal Data
Here’s how most of us protect our own privacy when it comes to new mobile apps: We hear about an app somewhere, we see it has a rating above 3.5 out of 5 stars, we install it, and we tap through whatever permission requests it presents.
That has a certain efficiency. Unfortunately, it’s not the safest approach. App developers don’t always know what they’re doing, and careless or rushed coding may not stand up to entry-level hacking.
If you use an insecure or hacked app on your phone, you could be exposing its personal data — like your address book, location, messages, and so on.
We saw this risk realized two years ago with Path, when a user discovered that the photo-sharing app uploaded entire address books without asking permission first. Last year, Snapchat users learned that their phone numbers had been exposed by sloppy security.
And last week, users of the vacuous app Yo learned that it was wide open to snooping — three college students told TechCrunch that they easily extracted users’ phone numbers and impersonated them on the service.
Maybe you held off on installing all or some of these apps. But can you be sure that the apps already on your phone are that much safer?
Actually, you can’t. But you can at least stop and ask a few reasonably simple questions to see if the people behind each app have the right priorities.
So before you install that next hot app, ask yourself these four things:
1. What do I need to give up to identify myself to this app?
“We don’t want your email, Facebook,” Yo brags in its release notes. Great, you may think: No more annoying usernames and passwords to remember! No worries about this spamming my Facebook friends!
But what Yo does need is your phone number. It’s technically optional, but without it you need to ask individual friends for their Yo usernames, which in turn will require confessing to them that you use Yo.
(On Snapchat and on Secret, in contrast, it is marginally easier to kick the tires without giving up a phone number.)
A phone number is an inconvenient bit of personal data to get leaked onto the Internet, should the carefully crafted defenses of a system slip up. There’s no meaningful junk filtering for most phone numbers, so you don’t want your number getting out. And changing a leaked number is a difficult, prolonged chore.
Having an email address fall prey to a data breach isn’t quite as painful since spam filters have gotten good. And using Facebook or Twitter to sign in to an app won’t expose your password if the app is later hacked. You can also yank the permission an app has to access your social accounts. Here’s how to do it on Facebook and Twitter.
2. Does the app explain why it needs my data?
Path’s original sin was not asking before uploading users’ contact lists so that it could suggest other Path users to new users. Apple ensured that other iOS apps couldn’t blindly get away with that by requiring them to get permission when they ask to peek in your address book.
In Android, apps have always had to ask permission for access to your data when they are installed. But not everybody pays rapt attention to those dialogs.
Both systems, however, leave it to developers to explain why they need to see personal data like your calendar or your location. Some do so in release notes that may not be read; the smarter ones figure out ways to explain as you use the app. See, for instance, this revealing post from the developer of the iOS app Cluster.