Proposed - Isolate contacts and permit contact access on a per-account basis

[pulser]

Would permit a user to allow an app to only access the contacts it "needs", in order to preserve privacy and reduce data leakage to permit an app to function.

Example usage - user wishes to use a VoIP or similar app (say whatsapp), but only giving it access to a small portion of the user's contacts list, to prevent business contacts from being added to a personal whatsapp account

[cobaltdr]

Thought I read this somewhere, but could not find it again when I was creating #85. Apologies.

[M66B]

It is too complicated to realize this.
It would mean per app settings and runtime evaluation of contacts.
Almost everything is possible, but this will impact performance and possibly stability.

[famewolf]

Along with this, as per our conversation, would be ensuring an app only has access to the accounts it needs vs all accounts. Apps that use gmail login would not be able to see facebook and vice versa.

[M66B]

There is no easy way to link account (types) and/or contact to applications. It would require additional Android permissions for XPrivacy to select account/contacts, which I think would be unacceptable to a lot of users.
http://developer.android.com/reference/android/accounts/AccountManager.html
http://developer.android.com/reference/android/provider/ContactsContract.html

[cobaltdr]

You might, if you had a whitelist within Xprivacy. And instead of feeding an empty list to the app, feed the whitelist to the app instead? Might involve creating a parallel contacts list which probably would be beyond the scope of Xprivacy.

[M66B]

Will be part of the next release.