Privacy Official Designation: Naming a privacy official and a contact person

45 CFR 164.530(a) is the requirement on privacy official designation. It is short to read and easy to underestimate, because satisfying it means producing evidence rather than holding an intention.

What the rule says

(1) Standard: Personnel designations. (i) A covered entity must designate a privacy official who is responsible for the development and implementation of the policies and procedures of the entity. (ii) A covered entity must designate a contact person or office who is responsible for receiving complaints under this section and who is able to provide further information about matters covered by the notice required by § 164.520. (2) Implementation specification: Personnel designations. A covered entity must document the personnel designations in paragraph (a)(1) of this section as required by paragraph (j) of this section.

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

Publishing the contact on your website follows from the notice of privacy practices: the notice must name the contact person or office (164.520(b)(1)(vii)), and a covered entity whose website describes its customer services or benefits must post the notice there (164.520(c)(3)(i)). Publishing the privacy official's name beyond that is practice, not the rule's text.

What this looks like in practice

In an assessment, 45 CFR 164.530(a) 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:

• Has the organization designated a contact person or office for receiving individual privacy complaints and inquiries?
• Has the organization formally designated an individual responsible for developing, implementing, and overseeing its privacy policies and procedures?

Ownership usually sits with the privacy official, 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. Designate a named contact person or office to receive privacy complaints and inquiries.
2. Publish the contact details in individual-facing privacy materials and on the organization's website.
3. Document the contact designation and keep it current.
4. Designate a privacy officer in writing, specifying the role's scope, authority, and escalation paths.
5. Define the officer's responsibilities for developing, maintaining, and enforcing privacy policies.
6. Publish the officer's name or office in internal directories and externally facing privacy materials (practice, not the rule's text).

Evidence an assessor asks for

For this requirement the evidence type that satisfies it is a record. 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

The usual gap is a control that exists in practice and nowhere in writing. Someone does the work, reliably, and it has never been written down, so the organization cannot demonstrate it and cannot notice when it stops. The fix is not more control, it is a dated record and a named owner.

What to do about it

• Produce the evidence, not the intention. For 45 CFR 164.530(a) that means dated records of each occurrence, not a description of the process. 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 official should be recorded as the owner. A control with no owner stops working the month the person who quietly maintained it changes roles, and nobody notices.
• Set a review cadence and keep the evidence of each review. An annual date with a dated output is a common floor; what fails an assessment is a control implemented once and never re-checked against a changed environment.

Work backward from the evidence. Decide what evidence would prove privacy official designation to someone who does not already trust you, then build the control that produces it. Programs built in that order tend to stay current, because the evidence goes stale visibly.

Related requirements

• Accounting of Disclosures: The six-year accounting and its exclusions
• Privacy Training: The privacy half of workforce training, which security training misses
• Right to Amend: Handling an amendment request and a denial

References

• 45 CFR 164.530(a), 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).