Consent Management Hierarchy

At the top of the hierarchy sits a specific feature, or product. In a typical online experience, a user accesses several of these products or features. That user may be required to provide a new consent for each feature or product to use their data. So, the entire consent workflow begins with a feature.

Second, each feature requires a disclosure. In our simple diagram, a single disclosure maps to a single feature. In a real-life scenario, you would almost certainly have multiple disclosures per feature.

Third, each disclosure may have multiple versions since disclosures are updated regularly. So, the relationship between disclosures and versions of disclosures is “one to many”.

Similarly, each version of a disclosure requires copies for different locales. So, the relationship between a disclosure version and locale copy is also “one to many”.