Description
Check requested purposes against granted and expressly excluded labels.
Consent, privacy and retention records encode supplied purposes, audiences, withdrawal status and timing rules. Literal membership or a true local predicate can organize these assertions while valid informed consent, adequate de-identification and lawful processing require separate contextual assessment.
Check requested purposes against granted and expressly excluded labels.
When to use this tool
Use Consent Scope Purpose Subsumption when checking the stated permission, withdrawal, retention or disclosure-record convention.
How to use the tool and how it works
- Enter requested, granted, expresslyExcluded. Follow any array-alignment requirements below. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read uncovered, excluded, coveredUnderTokens. Inspect coveredUnderTokens before interpreting the associated values.
Check requested purposes against granted and expressly excluded labels. Return distinct uncovered and excluded requested purposes; coveredUnderTokens requires neither list to contain an entry.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| requested | Requested | Required. Array of text; maximum UTF-16 length 8192; maximum items 256. |
| granted | Granted | Required. Array of text; maximum UTF-16 length 8192; maximum items 256. |
| expresslyExcluded | Expressly Excluded | Required. Array of text; maximum UTF-16 length 8192; maximum items 256. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| uncovered | Uncovered | Required. Array of text; maximum UTF-16 length 8192; maximum items 256. |
| excluded | Excluded | Required. Array of text; maximum UTF-16 length 8192; maximum items 256. |
| coveredUnderTokens | No requested purpose is absent or expressly excluded; empty requested list passes vacuously. | Required. Boolean. |
{
"input": {
"requested": [
"analysis",
"share"
],
"granted": [
"analysis",
"share"
],
"expresslyExcluded": [
"share"
]
},
"output": {
"uncovered": [],
"excluded": [
"share"
],
"coveredUnderTokens": false
}
}Limitations and assumptions
- Express exclusions override grants; empty requested purposes pass vacuously without establishing meaningful or lawful permission.
- Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
Alternative or Complementary methods
Review original permissions, participant choices and applicable organizational/legal requirements with the responsible professionals before actual use, disclosure or deletion.
References
Similar or alternative tools
- Consent Scope Intersection Size
Return the number of distinct scope labels shared by two consent lists.
- Consent Recontact Scope Flag
Check a requested recontact purpose and knowledge flags.