Privacy notice: Kleidos Contributor Agreement

Aviso de privacidad en español

  1. Controller. José M. Requena Plens, a natural person resident in Spain. Contact: mail@kleidos.dev.
  2. What we process.
    • Signers: the numeric id of your GitHub account and its login when you sign; the agreement version and its SHA-256; the date and time of your acceptance as recorded by GitHub; the address of the pull request and of your acceptance comment, and a SHA-256 of its text; and whether you signed on this site or by typing the comment.
    • While you sign at cla.kleidos.dev: GitHub tells us your account id and login. One cookie, strictly necessary for the signing you asked for, keeps you signed in for up to one hour. It holds, encrypted, the temporary token GitHub issued. We use that token for two things only: to read your account id and login, and to post your acceptance line on the pull request when you click "I agree". We revoke it as soon as that is done. There are no analytics and no third-party content on this site.
    • Companies: also the company name and, kept offline, the name and position of the person who signs for it.
    • We do not collect your email, postal address or real name, and we do not store your IP address. The email of your commits is read only to find your GitHub account; it is never stored or shown.
  3. Purposes and legal bases.
    • (a) Recording your acceptance and checking that every author of a pull request has accepted: performance of the agreement you enter into (GDPR art. 6.1(b)).
    • (b) Keeping proof of the agreement and of the contributions it covers, in a public register that anyone can verify, to defend the licences granted on them: our legitimate interest in being able to show who licensed what (art. 6.1(f)).
    • (c) Processing the data of commit co-authors who have not accepted yet, and showing who has accepted on the pull request: legitimate interest (art. 6.1(f)).
    • For company representatives, art. 19 of the Spanish Organic Law 3/2018 applies.
  4. Where the data comes from. From you, through your GitHub sign-in and your acceptance. For co-authors, from the commit metadata of the pull request.
  5. Who receives it.
    • The record is public: it is kept in the repository github.com/kleidos-dev/cla, and your acceptance comment and our confirmation are public like everything in a public pull request.
    • GitHub, Inc. runs the platform where you sign in and comment and hosts that repository, as an independent controller under its own Privacy Statement; it is established in the USA and states that it relies on the EU-U.S. Data Privacy Framework and on standard contractual clauses.
    • Cloudflare, Inc. runs this site and the program that talks to GitHub, as our processor under its Data Processing Addendum. To deliver the pages and to limit abuse it processes your IP address; we keep no record of it.
    • We give the record to a court or authority when the law requires it, and we may show it to a licensee to prove the chain of rights.
  6. How long. For as long as Kleidos distributes, or licenses on any terms, a contribution covered by your acceptance, and five more years (Civil Code art. 1964.2 and Intellectual Property Act art. 140.3). After that the entry is removed from the register. If you sign in and do not accept, nothing is kept once the cookie expires.
  7. Your rights. Access, rectification, erasure, restriction, objection and portability (GDPR arts. 15 to 22), free of charge and answered within one month, by writing to the contact above. Erasure and objection may be refused for the part of the record needed to establish, exercise or defend legal claims (art. 17.3(e) and art. 21.1); in that case we keep only that part, and out of public view if you ask and no overriding reason requires it to stay public. A public git history cannot be recalled from the copies others have made; we can remove an entry from the current files and from the history of our own repository. You can revoke the app's authorization at any time in your GitHub settings; that does not undo an acceptance. You may lodge a complaint with the Agencia Española de Protección de Datos (www.aepd.es).
  8. Is it required? These data are a condition for having your contribution merged: without the acceptance it cannot be merged. No decision with legal or similarly significant effects is taken by automated means: the program only checks whether an acceptance exists, and a person decides every merge.