4 ms·
We are currently struggling with firebase cloud messaging as the instance id has been deemed personally identifying by our laywers which google clearly does not
by theyinwhy 8y ago
We are currently struggling with firebase cloud messaging as the instance id has been deemed personally identifying by our laywers which google clearly does not think is the case (they don't even offer a data processing contract for firebase). So, if you are currently using Firebase cloud messaging, there is a big chance you are in violation of gdpr.
- dantiberian 8y agoGoogle Cloud has a DPA if I remember correctly, that would cover Firebase usage?
- theyinwhy 8y agoThe google cloud DPA unfortunately does not cover Firebase.
- ogeidix 8y agoAre you familiar with [1] and [2]? 1. https://firebase.google.com/support/privacy/ https://firebase.google.com/support/privacy/ 2. https://firebase.google.com/support/privacy/manage-iids https://firebase.google.com/support/privacy/manage-iids
- theyinwhy 8y agoI was told the main problem is that google's view on things is not en par with gdpr. Google claims that "Data associated with Instance IDs is generally not personally-identifying" (see 2.) which our lawyers say they clearly are. In that regard, google does not talk about instance ids or, worse, data processing in between APNs and the sending backend (see 1). The current legal situation does not allow us to use firebase cloud messaging.