-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Account for legal issues? #212
Comments
Suggestions:
|
In addition, we can allow providers to add links to ToS / GDPR / ... with respective rel types (copyright, disclosure, privacy-policy, terms-of-service?) in the capabilities. |
I added this to the API specification with remarks for clients to handle them properly. Do we need to send the agreement to the back-end at some point or is it fine to just handle it on client-side? |
as a developer, this feels like a silly approach :) Couldn't we just tackle it during the "registration" of a user (the first time a backend sees a user): forward to a page to consent/agree. For example:
|
@soxofaan It's still up to the back-end to decide. The current draft (see 99e4655) just gives the possibility to define terms of services and privacy policies in the capabilities and obliges the clients to ask for consent (in whatever form) when they are set. If the back-end doesn't set this (because it's part of the registration process) the client doesn't need to promt for consent. At the moment the client doesn't even send the consent to the back-end, but that may still need to be considered. (I guess we need a lawyer to decide this.) |
I'll leave it as it is for now. Communicating the consent to the server can be considered again for 1.0-final. |
We had a comment at the PhiWeek workshop that we should inform the user that there's data passed to a third party through openEO, e.g. to GEE or Vito. So we should see to which extent and how we inform the user about legal and property issues (terms of services, ...)...
The text was updated successfully, but these errors were encountered: