← All posts

Privacy Documentation Retention: The six-year retention rule for privacy records

May 19, 2026 · Ken Armstrong

45 CFR 164.530(j) covers privacy documentation retention. In most assessments the control itself is present and the record proving it is not, which is why this requirement produces findings at organizations that are, in practice, doing the work.

What the rule says

(1) Standard: Documentation. A covered entity must: (i) Maintain the policies and procedures provided for in paragraph (i) of this section in written or electronic form; (ii) If a communication is required by this subpart to be in writing, maintain such writing, or an electronic copy, as documentation; and (iii) If an action, activity, or designation is required by this subpart to be documented, maintain a written or electronic record of such action, activity, or designation. (iv) Maintain documentation sufficient to meet its burden of proof under § 164.414(b). (2) Implementation specification: Retention period. A covered entity must retain the documentation required by paragraph (j)(1) of this section for six years from the date of its creation or the date when it last was in effect, whichever is later.

That is the text of 45 CFR 164.530(j). Read each condition in it: it says what must be in place, and the method is yours only where the text leaves it open.

What this looks like in practice

In an assessment, 45 CFR 164.530(j) is not one question. It resolves into several, and each one is really asking for different evidence. These are among the questions asked about it:

  • Does the organization retain the documentation needed to demonstrate that required breach notifications were made, or that an impermissible use or disclosure did not rise to a notifiable breach?
  • Does the organization maintain written privacy policies and procedures and retain required privacy records for the required minimum period?

Ownership usually sits with the privacy and security officials, though the evidence is often produced by someone else, which is where the trail breaks. A control that works but has no owner tends to stop working the month the person who quietly maintained it changes roles.

Who this applies to

Covered entities. A business associate is bound directly by the provisions that name it (for example 45 CFR 164.502(a)(3), the minimum necessary standard at 164.502(b), and 164.410) and otherwise through its business associate agreement, so read the provision for whom it names. The Privacy Rule has no counterpart to the Security Rule's flexibility-of-approach clause (164.306(b)). Instead, 45 CFR 164.530(i)(1) requires policies and procedures reasonably designed for the size and type of your activities, and any deadline a provision sets applies at every size.

Building it, in order

The sequence below is the order that produces evidence as a by-product rather than as a separate documentation exercise:

  1. Document each impermissible use or disclosure and the four-factor risk assessment used to determine whether it compromised the security or privacy of the information.
  2. Retain evidence of any notifications made to individuals, regulators, and the media, including dates and content.
  3. Retain the analysis supporting any determination that notification was not required.
  4. If the organization is a covered entity, retain this documentation for six years from the date of its creation or the date when it last was in effect, whichever is later (45 CFR 164.530(j)(2), applied by § 164.414(a)). A business associate, which § 164.414(a) does not reach, bears the same burden of proof under § 164.414(b), so retain the documentation long enough to meet it and for any period its business associate agreements require; where the event was a security incident involving ePHI, the business associate's record of the incident and its outcome is kept for six years under 45 CFR 164.308(a)(6)(ii) and 164.316(b)(2)(i), which bind it directly.
  5. Maintain all required privacy policies, procedures, and notices in writing, including electronic form.
  6. Retain records of privacy-related communications, actions, activities, and designations for six years from the date of their creation or the date when they last were in effect, whichever is later (§164.530(j)(2)).

Evidence an assessor asks for

For this requirement the evidence types that satisfy it are log and policy. The distinction matters more than it looks: a policy states what you intend to do, a procedure states how, and a record proves it happened on a date. Auditors ask for all three, and a practice that has written the first two often has nothing for the third.

Date every document and keep the superseded versions. Under 45 CFR 164.530(j)(2) the documentation 164.530(j)(1) requires is kept six years from the date of its creation or the date when it last was in effect, whichever is later. It is the same period the Security Rule sets at 164.316(b)(2)(i), under a different provision, so cite the one that governs the document you are holding.

Where this usually goes wrong

In our question bank this is weighted Critical: a gap here is raised as a critical finding (a partial answer as high). The usual cause of a gap is drift: the control was implemented once, the environment changed, and nothing re-checked it. A dated review on a fixed cadence is cheaper than the remediation.

What to do about it

  • Produce the evidence, not the intention. For 45 CFR 164.530(j) that means retained logs plus evidence somebody actually reviewed them and a signed, dated policy with a named owner and a review date. If the only evidence is that someone knows how this works, you have a practice and not a record.
  • Put a name on it. Your privacy and security officials should be recorded as the owners. Where the work is done by someone else, say so in the document: the split between who owns it and who performs it is where the trail usually breaks. A control with no owner stops working the month the person who quietly maintained it changes roles, and nobody notices.
  • Review it on a fixed date, not when you remember. In our question bank this is weighted Critical: a gap here is raised as a critical finding (a partial answer as high). Put the review on the calendar with an owner, and keep the dated output of each one.

The practical test for 45 CFR 164.530(j) is whether someone unfamiliar with your organization could read your documentation and tell what you do, who does it, and when it last happened. If they can, the documentation will hold up; whether the requirement is met is a judgment about what it shows, and your counsel owns that conclusion. If they need you in the room to explain it, it will not.

Related requirements

References

  • 45 CFR 164.530(j), in 45 CFR 164.530 on eCFR. Quoted text verified against the eCFR text current as of 2026-10-06.
  • This post describes what a requirement asks for and what evidence documents it. It is not legal advice, and your counsel owns the conclusion. State law may impose stricter obligations (45 CFR 160.203).