Changes to the TOS web site behavior
Based on discussions with our lawyers and legal partner (Els), I've updated the ToS documentation that is required for Users (i.e. people registering into the platform). Things to do:
@Kanma: URGENT: Update the ToS using the new
In the ToS, a "Contact Form" is mentioned. This form should be used to notify Idiap of problems with the use or management of the BEAT platform. Currently, this contact form does not exist in our platform. It must be created (with a captcha to avoid spamming). Once that is established, one should replace the placeholder for the contact form in the ToS with the final address. Currently it is set to https://beat-eu.org/platform/contact
legal_disclaimer.rstfile in the
docsdirectory. The file should be displayed like the ToS, as a pop-up. Users that dismiss the banner, get a cookie indicating they have accepted the disclaimer, with a given version number.
In the Legal Disclaimer, a link to the ToS should be made available. A place holder pointing to "https://beat-eu.org/platform/tos" is there, but should be updated if that changes. Action Point: We should create a URL that points to the ToS like stated.
Both the "ToS" and our "Legal Disclaimer" have a version number. Users that access the platform after the ToS has been updated, should get a banner pointing to the new ToS. Visitors that access the platform after the "Legal Disclaimer" has been updated should also check it again. Note that Users don't need to go through the "Legal Disclaimer", just visitors. This feature can be achieved by comparing the cookie established on the user browser with the current version of the ToS/Legal Disclaimer and showing/updating it.
While we can make sure that a person that does not accept the ToS cannot register, we cannot make sure that a Visitor that does not agree with the Legal Disclaimer will not continue visiting the website. By clicking on the "banner close" button or by popping up the "Legal Disclaimer", the user implicitly agrees with what is said in there. If they don't agree, then they should just leave the website. At this point, creating a mechanism to block the contents may be tricky (@Kanma: what do you think about this?)
After all these items have been implemented, I think we can finally close this issue.