The link is to a self-published whitepaper, and the 'stanford.edu' affiliation is through a visiting postdoc at the Graduate School of Education (nothing CS related).
So yes, her PhD is in psychology, and she's a visiting research scientist at Stanford's School of Education.
Meanwhile, I work on the computer science side, although am not an academic (although I interact with plenty of academics, MIT, Berkeley, Stanford, and some European schools). The tech talk I linked to explains how the algorithms work (CRDTs), you don't need to be an academic to understand how it works.
The system has been used on Navy warships, as well. If you'd like to talk to the Sergeant Major who deployed the system in production in the industry, shoot me an email and I'll happily connect you. :)
Please take into account that I am respecting you for your work but this field involves more than a claim. If you look, for example, to simmetric encryption algorithms history, there were a lot of proposals and people involved in trying to crack them. Many of them sounded great but were break by professional cryptographers. The blockchain scene is full of proposals but there are very few security reviews.
We're not writing our own cryptography, lol, we're using existing libraries based around OpenSSL using industry accepted and standardized algorithms and curves (ECDSA 256, AES 256, ECDH 256, PBKDF, etc.)
So yes, please email me the moment those get broken/cracked and we'll upgrade to whatever new standards are available.
Do you have any vulnerability to report? Please send it in. Security is an always evolving process.