GDPR-Style Personal Data Retention Conflict Flag Checker
Audit conflicting independently established retention/deletion deadlines and preserve legal holds for separate review; no GDPR interpretation, precedence resolution or deletion advice.
Description
A retention requirement and a deletion target can conflict when their independently established dates differ.
A retention requirement and a deletion target can conflict when their independently established dates differ. Legal holds are a separate review condition and should remain visible rather than being used to silently resolve the date conflict.1
Audit conflicting independently established retention/deletion deadlines and preserve legal holds for separate review; no GDPR interpretation, precedence resolution or deletion advice.
When to use GDPR-Style Personal Data Retention Conflict Flag Checker
Use this tool to audit conflicting independently established retention/deletion deadlines and preserve legal holds for separate review; no GDPR interpretation, precedence resolution or deletion advice.
Prepare the inventory, measurements or policy dates for the collection and reporting period. Confirm units, record order and any independently established thresholds or permissions.
How to use GDPR-Style Personal Data Retention Conflict Flag Checker and understand its results
- Prepare the inventory, measurements or policy dates for the collection and reporting period. Confirm units, record order and any independently established thresholds or permissions.
- Enter requiredRetentionUntilOrdinals, callerPrivacyDeleteByOrdinals, legalHoldFlags using the field table and calculation rules, then run the tool.
- Read retentionPrivacyConflictFlags, signedRetentionBeyondDeletionDays, holdRequiresSeparateReviewFlags. The explanation below defines the units, signs, ordering and any flags or placeholder values.
- If the tool reports an input issue, correct the values and run it again. Apply the stated assumptions when interpreting a successfully returned result.
| Input field | Meaning | Value type; see rules below | Requirement |
|---|---|---|---|
| requiredRetentionUntilOrdinals | Required retention until ordinals | list of number | Required |
| callerPrivacyDeleteByOrdinals | Caller privacy delete by ordinals | list of number | Required |
| legalHoldFlags | Legal hold flags | list of number | Required |
Pair nonnegative integer retention and deletion ordinals with binary hold flags. Return signed retention-beyond-deletion days, strict positive conflict flags and a copy of hold flags for separate review. Equal deadlines produce no date conflict, and hold status does not change that comparison.
Paired lists must be nonempty and have equal lengths.
signed difference = retentionUntil−deleteBy; conflict = difference>0 Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.
| Output field | Meaning | Value type |
|---|---|---|
| retentionPrivacyConflictFlags | Retention privacy conflict flags | list of number |
| signedRetentionBeyondDeletionDays | Signed retention beyond deletion days | list of number |
| holdRequiresSeparateReviewFlags | Hold requires separate review flags | list of number |
{
"input": {
"requiredRetentionUntilOrdinals": [
30,
20
],
"callerPrivacyDeleteByOrdinals": [
25,
25
],
"legalHoldFlags": [
0,
1
]
},
"output": {
"retentionPrivacyConflictFlags": [
1,
0
],
"signedRetentionBeyondDeletionDays": [
5,
-5
],
"holdRequiresSeparateReviewFlags": [
0,
1
]
}
}Limitations and assumptions
The caller must establish applicable dates and holds independently. Despite GDPR in the title, this tool does not interpret legislation, resolve precedence or recommend deletion. Use a common day-ordinal origin.
Numeric inputs must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Numeric lists are limited to 100,000 entries; the rules above may require smaller limits. Missing required fields, extra fields, wrong value types and violations of the calculation rules are input errors.
Alternative or Complementary methods
Use Retention Period Expiry Eligibility Checker: Separate declared expiry from caller hold/review gating, preserving expired-but-held records; eligibility flags are workflow policy, not lawful destruction permission. For a complementary task, use Orphan Works Risk Tier Classifier: Map missing documented rights-search steps into caller weighted workflow risk tier; not an orphan-works legal status, diligent-search certification or permission to publish.
References
Similar or alternative tools
- Retention Period Expiry Eligibility Checker
Separate declared expiry from caller hold/review gating, preserving expired-but-held records; eligibility flags are workflow policy, not lawful destruction permission.
- Orphan Works Risk Tier Classifier
Map missing documented rights-search steps into caller weighted workflow risk tier; not an orphan-works legal status, diligent-search certification or permission to publish.