Description
Return an expiry envelope from uncertain retention duration.
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.
Return an expiry envelope from uncertain retention duration.
When to use this tool
Use Template Retention Window Bound when checking the stated permission, withdrawal, retention or disclosure-record convention.
How to use the tool and how it works
- Enter created, retentionLower, retentionUpper, now. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read expiryLower, expiryUpper, certainlyExpired, possiblyExpired. Inspect certainlyExpired, possiblyExpired before interpreting the associated values.
Return an expiry envelope from uncertain retention duration. Require whole 0 <= retentionLower <= retentionUpper; expiry endpoints add creation time, certainlyExpired uses now > upper expiry, possiblyExpired uses now > lower.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| created | Created | Required. Safe integer. |
| retentionLower | Retention Lower | Required. Safe integer; minimum 0. |
| retentionUpper | Retention Upper | Required. Safe integer. |
| now | Now | Required. Safe integer. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| expiryLower | Expiry Lower | Required. Safe integer. |
| expiryUpper | Expiry Upper | Required. Safe integer. |
| certainlyExpired | now strictly greater than the upper expiry; exact equality is not expired here. | Required. Boolean. |
| possiblyExpired | Possibly Expired | Required. Boolean. |
{
"input": {
"created": 10,
"retentionLower": 20,
"retentionUpper": 30,
"now": 35
},
"output": {
"expiryLower": 30,
"expiryUpper": 40,
"certainlyExpired": false,
"possiblyExpired": true
}
}Limitations and assumptions
- Equality is not expired under these strict comparisons; no deletion occurs and no legally appropriate retention policy is selected.
- 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.
- Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.
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
- Biometric Template Explicit Retention Window
Return template age and deletion-due record flags.
- Biometric Comparison Pair Identity Consent
Return literal comparison identity and shared-purpose consent flags.