{"action":"opened","issue":{"url":"https://api.github.com/repos/cypress-io/cypress/issues/670","repository_url":"https://api.github.com/repos/cypress-io/cypress","labels_url":"https://api.github.com/repos/cypress-io/cypress/issues/670/labels{/name}","comments_url":"https://api.github.com/repos/cypress-io/cypress/issues/670/comments","events_url":"https://api.github.com/repos/cypress-io/cypress/issues/670/events","html_url":"https://github.com/cypress-io/cypress/issues/670","id":259029172,"number":670,"title":"Concerned about binding arbitration in terms of use + suggestions","user":{"login":"rmharrison","id":4275722,"avatar_url":"https://avatars0.githubusercontent.com/u/4275722?v=4","gravatar_id":"","url":"https://api.github.com/users/rmharrison","html_url":"https://github.com/rmharrison","followers_url":"https://api.github.com/users/rmharrison/followers","following_url":"https://api.github.com/users/rmharrison/following{/other_user}","gists_url":"https://api.github.com/users/rmharrison/gists{/gist_id}","starred_url":"https://api.github.com/users/rmharrison/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rmharrison/subscriptions","organizations_url":"https://api.github.com/users/rmharrison/orgs","repos_url":"https://api.github.com/users/rmharrison/repos","events_url":"https://api.github.com/users/rmharrison/events{/privacy}","received_events_url":"https://api.github.com/users/rmharrison/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2017-09-20T03:32:13Z","updated_at":"2017-09-20T03:32:13Z","closed_at":null,"author_association":"NONE","body":"I understand that you're still in beta and probably intended to \"cover your arse\" against bad actors, but the binding arbitration provision in your [terms of use](https://www.cypress.io/terms-of-use/) gives me pause (that said, thank you for making that term clear up-front instead of burying it in the legalese).\r\n\r\nIf for whatever reason there is an issue (and I certainly hope there isn't), e.g. an undisclosed data breech or other activity that causes substantial economic damage, the recourse of individuals and small firms is substantially limited by not being able to participate in class action.\r\n\r\nEven if you choose not to alter your terms, please consider:\r\n- Providing a link to the \"PRE-DISPUTE ARBITRATION CLAUSE\" mentioned in section 19 (Binding Arbitration)\r\n- Write a short, **non-legalese** synopsis of agreements so folks have at least some understanding of what they're signing.\r\n  * Github has a good example of this, see: https://help.github.com/articles/github-terms-of-service/#b-account-terms\r\n- Add the \"Cypress CLI\" and other OSS components (Cypress Desktop is already mentioned), and ensure they are indeed released under the MIT licence.\r\n  * Folks are skittish following Facebook's unilateral BSD + Patents debacle.\r\n  * I'd feel much more comfortable if I knew the licence/right-to-use on the engine/CLI was non-revocable.\r\n  * Certainly understand monetizing the dashboard, but without some guarantees around the engine/CLI I'm left holding the bag on a rushed-migration off my entire front-end test-suite should something happen to yal. For example, folks only had a few months to transition their entire auth-stacks off [Stormpath](https://stormpath.com/blog/stormpaths-new-path). Adding to the pain, [Okta bungled](https://hackernoon.com/authentication-as-a-service-an-honest-review-of-auth0-315277abcba1#5a8e) the transition."}}
{"actor":{"display_login":"rmharrison"}}