@maschera Thanks for sharing - I hope that it will get some attention from Glide.
@david It seems obvious that Glide does have an issue with GDPR - and I cannot understand why you are not adressing it - or sharing when and how you will adress it.
Glide (in my understanding without a legal background) serves as a data processor for us as data responsible. The app owner (us) are responsible for the personal data that people leave in our app. When Glide uses’ different 3rd party APIs - we are still responsible for all the personal data that is transferred to the third parties. So if fx mapbox stores - and loses - all the location that the user has saved in Glide - and this data can be traced back to the user (e.g. the data is not anonymous) - well, then we will be responsible. We will have to tell the user that we have lost their data.
Further, the user has a number of rights in relation to GDPR (in my understanding):
- which processing do we do with the personal data (including what the data processor and their third parties do)
- rights to know which personal data that we process
- rights to stop us from processing their personal data (this might mean that they cannot use our app)
- rights to have data corrected
- rights to be deleted including all their data
- rights to limiting the use of the personal data
- rights to data portability
- rights to withdraw a consent
Glide could help us as developers to be able to fulfil the GDPR requirements by stating how we can comply. Glide could deliver a data processor agreement telling exactly what Glide does with the personal data - and which 3th party that have access to the data.
I would think that Europe is such that big business oppotunity for Glide that it is not acceptable that only apps without personal data can be created in Europe.