Transparent Disclosure

Transparent disclosure fundamentally requires both truth and honesty. Truth in the context of software security involves first and foremost informing consumers in plain English regarding the actual threats to security and privacy a given solution can actually thwart. Honest disclosure is a much higher hurdle, for it requires, the enumeration of the threats that a given solution cannot effectively address. We have labeled this combination of truthful and honest disclosure, Transparent Disclosure.

Conceptual Disclosure involves outlining the possible weaknesses of a given security solution, irrespective of their practical risk or probability of success. The purpose of this document is to outline and explain the conceptual threats to FN’s protection of User data. Further, the reader should be aware that even after enumerating all of the conceptual issues that we currently understand could compromise our solutions, we have no proof, that other yet to be discovered or yet to be known to us tools or method s don’t exist that can circumvent FN’s protection scheme. Said another way, “we don’t know what we don’t know’.

As related to both of the above disclosures, we would note that cyber-security is a very broad topic and one which is dynamically evolving. As such, we fully expect to routinely update our disclosures, so please consider the above representation as a continuous work in progress. If you have any thoughts, concerns or feedback related to FN’s disclosures, we would welcome your thoughts and you can publicly provide your comments here, or feel free to email us if you would prefer a more confidential dialogue.