Soon enough I’ll be releasing JDHQ v26 which will allow you – if you so choose – to store your own data. Think textual data: notes, the titles of IDs and categories, that sort of thing.[1] (I have no plans to build a file storage service.)
But data is data. Even the title of an ID you create is potentially sensitive: it might relate to a medical procedure, for example.
It would be disastrous to leak or otherwise allow this data to be exposed. There’s the obvious moral motivation, but also an economic one: nobody’s going to pay to use an insecure platform!
I’m particularly sensitive to security issues given last month’s leak of email addresses. So here’s an in-depth look at my security practices. In the hope of making it readable by the layperson, I’ll give background where necessary. I welcome feedback.
This will be a very early beta-style release. I expect almost nobody will use it. But the only way for me to get this thing from no-product to useful-product is to build it, and start using it. So that’s what I’m gonna do. ↩︎