This doesn't use machine translation. Did you look at the link?
It specifies a privacy policy with options using JSON, and then there is a set of (human-written) strings for each language to turn those options into text.
It's not machine learning, but the text in other languages also isn't written by a lawyer according to the authors responses in this thread, so the risk of mistranslation and changed legal meanings is still there.
The risk is substantial. Drafting standards are not equivalent across languages, and the translators are not legal translators.
Legal vocabulary contains words that are terms of art which are then bastardized and changed in usage when used in lay discussion, leading to differential meanings.
Let's not even raise the issue of the language having dramatically different meanings and legal effects across jurisdictional lines even if the wording of the text is unchanged. Or the fact that best practices in drafting specific clauses might be changed in a few weeks following the release of new jurisprudence.
Translations. Say, the English one is the official and legally binding one, and the Chinese and Spanish translations are only for added convenience, without any legal effect.
Ah, got it. You typically have to say that really explicitly in all the languages. Also, it depends. Generally speaking, best practice is to have one and only copy and then a phone call where it's explained however. Better practice is not to take legal advice from my Internet comments, because I am not a lawyer :D.
Totally aware of that. Reviewing individual translations again, and repeating this from time to time, is definitely something that can and should be done in the future.
So there's obviously an easy fix to the problems you outline, which are no fundamental problems.
It's a whole different matter, though. Using automatic machine translations is still not what is done here, and you can't compare human translations with that.
Regarding legal expertise, I or anybody else could go through this with a lawyer next week and have a review, including a "pull request" of required changes, no more than a week later.
For the translation, of course the process was not copying and pasting words into Google Translate one by one and using the result. The translation process has been much more thorough.
It specifies a privacy policy with options using JSON, and then there is a set of (human-written) strings for each language to turn those options into text.