Personal Record ReviewU.S. EDITION
OCTOBER 2026

This publication is not affiliated with, sponsored by or operated by the University of Utah. Subject names identify the subjects of the articles, not the publisher.

No university record changes, account services or personal-data intake.

Cookie settings

Record concepts

One change, four different questions

A displayed name, a legal record, directory visibility and consent answer different questions. Choose the layer before choosing a form.

In this article

“I updated my profile” is a beginning, not an explanation of what another person can now see. A profile can contain several kinds of facts and several decisions about those facts. Treating them as one switch makes a correct change feel like a broken promise.

This dossier uses four layers to read University of Utah personal-record instructions. The layers are our editorial comparison, not university terminology. They help you describe your aim without sharing your actual name, address or record.

The four questions

01 / Representation
What name appears in a particular setting? A chosen-name setting concerns presentation in named systems. It is not proof of a legal-name change.
02 / Record accuracy
What value belongs in the university’s official record? A correction may require a documented process. “The label I prefer” and “the underlying fact is wrong” can be different requests.
03 / Public visibility
Can directory information be released publicly? A privacy restriction is about disclosure. It is not a request to erase the underlying record.
04 / Specific disclosure
May an identified person receive information? Consent concerns a recipient and a scope. It is not a shared password or authority to make every decision for you.

Read the boundary before the button

The Registrar publishes separate instructions for chosen names, official personal information and privacy and consent. Their separation matters. If the desired outcome spans layers, plan more than one question rather than assuming the first saved setting completes the whole job.

Make the result observable

Before making a change, finish this sentence privately: “I will know this worked when…” Name the specific output: a particular display, an official value, a restriction status, or a consent recipient. “Everything everywhere is fixed” is not a useful test because the public documentation does not promise that.

If a system is missing from the chosen-name list, ask its responsible department. If the question is about disclosure, ask the Registrar rather than testing privacy by sending private details to someone else. A clear question is safer than a broad screenshot.

Try the record-boundary comparison on the home page. It uses only abstract choices. It neither inspects your record nor decides your legal rights. For a mixed situation, run each intended outcome separately and keep the answers distinct.

Evidence & limits

Public sources checked October 15, 2026. This is independent editorial explanation, not legal advice or a test of an authenticated university account.

Have a public source that changes this analysis? Suggest a correction. Please don’t send names, addresses, contact details, education records, identity documents or account credentials.