We have moved to a new Sailfish OS Forum. Please start new discussions there.
29

Do android apps have access to private data?

asked 2014-10-15 14:44:52 +0300

wim de vries gravatar image

If so, that is very LIKE and I will remove them immediately. Please give us some more insight on the policy. There are very different statements about this. Do they have access, to what data? Can I block that in a simple manner? Thanks.

edit retag flag offensive close delete

Comments

1

What data do you mean exactly?

juiceme ( 2014-10-16 12:46:54 +0300 )edit
1

I believe Android rights management is the matter. E.g.: 1. Can Android Apps read Jolla contacts? 2. Can Android Apps activate GPS? 3. Can Android Apps access your account data stored in SailfishOS?

And so on...

ramoth ( 2014-10-16 18:51:10 +0300 )edit
1

Thanks Ramoth. Indeed esp contacts, email, calendar, documents, personal settings and account. I know they can read GPS data. It is very worrying that there is still no answer.

wim de vries ( 2014-10-26 09:46:26 +0300 )edit
2

Evenmore, why is a GOOD app like Syncevolution not allowed in the harbour store. This disables us a secure use of private data synchronization eg with Owncloud. We are now forced to use (unsecure pirate) services like Google.

wim de vries ( 2014-10-26 09:51:59 +0300 )edit

Interesting question...

JonnJonz ( 2014-11-07 23:25:35 +0300 )edit

2 Answers

Sort by » oldest newest most voted
18

answered 2014-11-13 21:28:57 +0300

Aard gravatar image

The Android runtime has access to _some_ private data, most importantly contacts. The access there is read only, and only a subset of the contacts database (contacts from services like Facebook are excluded) is made available to the Android runtime. It also has access to files in the home directory (to use pictures, videos, ... from Android apps), where the full access level depends on the "world" permissions of the file -- so usually it's only read only access.

Additional interfaces which _might_ be counted towards "private data" are gps/agps, some parts of SIM information, and the list of available WIFI networks. Access to network information is read only as well.

Interfaces like "make a call" or "send an SMS" from Android can't be counted here -- they're going through xdg-open, and end up in native applications, where the user needs to confirm any action before it happens.

TL;DR: We're trying to keep as much data as possible from the Android runtime, what currently is available is required for the applications the majority of users want to use to work. We are currently working on a settings interface where some aspects of the runtime can be configured (including privacy settings, like contact access), to make more privacy-aware users comfortable with using Android applications as well. We don't have an ETA for this yet, though.

edit flag offensive delete publish link more

Comments

Obviously there is a need for the android runtime to have access to private data, equally so even a read only access to someones private data might be bad enough. What I would like to see is a fine control over which data will be accessible with different applications, e.g. flag which contacts and which fields of a contact should have read only access. Similar story with synchronisation with other services accounts e.g. FB, google accounts.

pmelas ( 2014-11-13 21:41:13 +0300 )edit

While I don't want to say "this will never happen", at least I can say if it happens it'll be quite a while away. We're controlling the interfaces between the native Sailfish APIs and the Android world, so it's not too hard to control those -- for the whole runtime. Now what you're asking for would require a significant amount of work inside of the Android runtime itself. Which definitely would be doable, but I think improving the native API offering is more important than building a better Android than Android.

Aard ( 2014-11-13 21:48:41 +0300 )edit

With regard to Android compatibility going forward, what are plans? AFAIK, Dalvik (which Alien Dalvik relies on) is being completely replaced by ART in Android 5.0 (Lollipop). Obviously most recent devices will be running it soon, and all future devices and the majority of applications (and updates) will be pitched at it. Can you share what's likely to happen with Jolla / Sailfish, and whether when paid app support is implemented, Alien Dalvik will be available to buy for Android phones running ports of Sailfish?

midnightoil ( 2014-11-13 21:50:58 +0300 )edit

Thanks for the answer. BTW, for now, Android WhatsApp is not able to read my contacts. I like that. It only gets contacts that I want it to use!

wim de vries ( 2014-11-13 22:15:47 +0300 )edit

For me, this is good idea to block ALL access to sailfish data (except internet connectivity) for android apps, at least until we can't control permissions per each android app.

Wickedsten ( 2014-11-13 22:50:05 +0300 )edit
8

answered 2014-11-07 19:15:16 +0300

wim de vries gravatar image

Unfortunately, the answer is YES.

Since there is no answer from Jolla, I did a test. I installed the Android Telegram app and it just picked up all my contacts. I find this very disturbing. Sailfish OS app (developers) get no access to private data, whereas (mostly) data plundering Android apps do get this access. (BTW Telegram is not plundering, that's why I used it for testing). Sorry, Jolla, I think you should seriously reconsider your privacy policy. Or convince us that I am completely wrong (which I do hope).

edit flag offensive delete publish link more

Comments

3

You want to use a messaging app and you are wondering that this has access to your contacts, really?

torcida ( 2014-11-07 20:50:04 +0300 )edit
2

Please stay on topic. Read the above question & comments.

wim de vries ( 2014-11-07 21:46:50 +0300 )edit
1

No answer is an answer... But not really a surprise.

JonnJonz ( 2014-11-07 23:24:49 +0300 )edit
5

Jolla’s privacy principles: "You have the right to the utmost protection of your privacy. It should be for you to decide what personal data you want to share and when."

wim de vries ( 2014-11-07 23:46:10 +0300 )edit
3

The reason why Android apps have contacts access, while native apps don't is rather simple: The Android apps access the contacts through a stable Android API, and we're controlling what is made available through that API on our side if the runtime integration glue.

For native apps we rely on the contacts API of Qt PIM -- which is not stable yet. We don't want to roll our custom APIs, but use standard upstream Qt APIs, and we're working with upstream on that. The other infrastructure parts (like privileged/non-privileged contacts access) are already implemented, and have been on the device for a while. We are fully aware of the API problem.

Aard ( 2014-11-13 21:33:42 +0300 )edit
Login/Signup to Answer

Question tools

Follow
9 followers

Stats

Asked: 2014-10-15 14:44:52 +0300

Seen: 1,164 times

Last updated: Nov 13 '14