In this scenario, an app developer named "Acme" wishes to share data with a third party app developer named "BCorp". Passing actual estimate data between separate companies is not permitted, however, the CCC Secure Share™ Program (CCC Secure Share) does permit the passing of the BMS //DocumentID which is 128-bit UUID/GUID defined in the BMS specification. Using this public identifier, Acme can share a reference to the estimate data with BCorp, then BCorp can call the CCC Secure Share API to retrieve the estimate. At the point of retrieval CCC Secure Share will validate the security credentials of BCorp and also verify that the shop has agreed to share data with BCorp - and only then return the appropriately formatted BMS document to BCorp.

Consequently, CCC Secure Share offers a mechanism for registered apps from different companies to safely pass references in a manner that ensures security of repair shop data.

In this model, estimate data is pushed from the CCC ONE® Estimating software to App 1 which then passes a document ID to App 2. App 2 uses the BMS //DocumentID (which is a 128-bit UUID/GUID) to "pull" estimate data from CCC Secure Share.