The punchline is that a factor database has the extraordinary ability to diversify the risk of a backdoor data breach across network locations. This allows you to multiply the probabilities of a breach at each location for the simple reason that both locations must be breached in order to retrieve any intelligible data. So a 5% chance of breach at location one and a 5% chance of breach at location two means the overall chance of breach is now 0.25%. That's not an insignificant reduction.
Data security efforts are usually devoted to fortification. A single location houses the treasure, and we build armies and forts to protect around it. A factor database takes a different approach.
A factor database contains no intelligible data when at rest. During data insertion, each piece of data is split into factors - a primary factor and a meta factor. The primary factor is the value in a single cell - the attribute value of a record. The meta factor contains information that connects all the values into a relational structure, but contains no value. The primary factor and meta factor can be stored at separate locations.
Location one holds an encrypted database with a single column of all primary factors with no indication of how they are related. For example - a single column of disparate patient first names, last names, and biometric information. The meta factor contains information that relates the values in the primary factor. These factors are stored in separate locations. Information from both locations is necessary to retrieve even a single piece of data.