Skip to content

Main content

Security Record Retention Date Tool

Apply an explicit calendar-day retention duration to a security record date without selecting a compliance rule or deleting records.

Loading tool…

Description

Parse recordDate as a real YYYY-MM-DD date, add retentionDays in 0-100000 using UTC calendar arithmetic, and require output no later than year 9999.

Security administration uses retention periods, control owners, acknowledgments, recovery targets, and test records. Arithmetic and labels can make these records consistent, but they do not demonstrate that a control works or that a policy is adequate.

Parse recordDate as a real YYYY-MM-DD date, add retentionDays in 0-100000 using UTC calendar arithmetic, and require output no later than year 9999.

When to use this tool

Use Security Record Retention Date when you need a narrow security-record calculation or formatter under supplied policy values.

How to use the tool and how it works

  1. Enter recordDate, retentionDays. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read retentionThroughDate. Use the output convention below.

Parse recordDate as a real YYYY-MM-DD date, add retentionDays in 0-100000 using UTC calendar arithmetic, and require output no later than year 9999.1

Input fieldMeaning and unitsAccepted input
recordDateRecord DateRequired. Text; maximum UTF-16 length 8192.
retentionDaysRetention DaysRequired. Safe integer; minimum 0; maximum 100000.
Output fieldInterpretationReturned shape
retentionThroughDateRetention Through DateRequired. Text; maximum UTF-16 length 8192.
json
{
  "input": {
    "recordDate": "2026-11-01",
    "retentionDays": 30
  },
  "output": {
    "retentionThroughDate": "2026-12-01"
  }
}

Limitations and assumptions

  • Retention duration is caller supplied; the date does not authorize deletion, establish a legal retention period, or account for holds.
  • 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 the complete control evidence, applicable policy, and operational tests before making a security decision.

References

  1. Calculation and input contract: security-studies/security-record-retention-date — tool.io

Similar or alternative tools