Compile-time macros do indeed seem to be what provides the necessary client/server separation for sensitive data. That does mean you are trusting the library t

Compile-time macros do indeed seem to be what provides the necessary client/server separation for sensitive data. That does mean you are trusting the library to implement these macros correctly. In that sense, data security for these symbol bindings is a responsibility of the library, and therefore a risk, as is called out lower on the page. Once the library is complete however, and a larger part of the community has been able to inspect it, this type of bug should not be an issue. It's one of the most fundamental concerns of the library.