<a href="https://www.consol.io/encryption/" rel="nofollow">https://www.consol.io/encryption/</a><p>> At this time, Consol supports encryption only of certain content types, viz. notes, code blocks, and images, for users who have subscribed to the E2EE component. The other content types available in Consol are not yet encryptable.<p>> Notably, Consol E2EE does not yet support encryption of the titles of any content types. For example, if you create a Consol note and encrypt it, the text you add to the note’s body will be encrypted but its title will not be encrypted. For now, you should operate accordingly. We plan to improve this in the future.<p>> You acknowledge that if you encrypt an item after you create and add content to it, there may be a period of time in which your item’s body content is not encrypted while being stored in our database. To ensure the greatest security currently available in Consol’s system, you should, where possible, encrypt an item in its pageview before you begin adding content to it. It is better practice in Consol to encrypt an item first and only then begin work by adding content.<p>> This means that for certain content types that require creation and upload before the pageview is visible, such as uploadable or linkable images, Consol does not yet provide a way to encrypt such body data beforehand. You acknowledge and consent to the attendant risk that you must manually designate certain content for encryption after it has been uploaded.<p>I don't appreciate having to dig through your FAQ to find the holes and caveats. There is literally no technical reason for this.<p>If you are going to make security promises like this you need to:<p>1) Actually have them implemented.<p>2) Have them secure by default.