Deactivating an ORCID Record: What Goes Away and What Stays

What deactivation actually does

This guide is for a researcher retiring one ORCID record, not for merging or resolving duplicate records. The distinction matters because deactivation changes what ORCID itself displays and stores, but it does not act as a global delete button for every system that ever received your identifier.

Start with the scope of the action. Deactivation is initiated from account settings and requires confirming through email, so it is a deliberate, two-step decision rather than an instant toggle.

ORCID deactivation requires an account-settings action and a confirmation email. Source

Before you confirm, decide whether your goal is to stop the record from being used as your public identity or to erase every trace of the identifier. Only the first goal is within ORCID’s control. If an employer profile, funder system, publisher workflow or repository entry cites your ORCID iD, that citation lives in the other system’s database, not in yours.

What is retained and what is removed

The retained identifier is the part readers most often misunderstand. The iD is designed to persist as a stable reference, so deactivation is not the same as deleting the number. Personal information is removed from the record, and a masked email value remains.

The identifier is retained after deactivation, while the record’s personal information is removed and a masked email value is retained. Source

For practical purposes, treat the outcome as a stripped-down record: the identifier can still resolve or be referenced, but it should no longer present your name, biography, employment history or other personal details as before. Because the approved facts do not describe every field-level outcome, verify the current state of your own record after the change rather than assuming a specific field will be blank. The facts also do not establish how long any step takes or whether every connected service refreshes automatically.

Inventory external associations before you confirm

The single most useful preparation step is a written inventory. ORCID is one system among many, and the associations that matter are the ones held elsewhere.

Use a table like this, filled with what you can actually observe:

Two cautions when building this list. First, a search result showing your name beside an iD is a lead, not proof that the page is under your control or that the association is current. Second, a public profile match does not by itself prove ownership of an account, so confirm each entry against a source you trust before sending removal requests.

If your inventory work turns into a broader question about which public profiles are tied to your name, the guide on how to find all accounts linked to a name explains how to approach that separately. Keep that task distinct from the ORCID decision; it is about discovery, not about the deactivation itself.

Confirm the deactivation decision

Before acting, write down your answers to three questions:

1. What problem am I solving? If the problem is a duplicate record, deactivation is the wrong tool; the approved facts here cover retirement of a record, not duplicate resolution.
2. Who still needs this iD? Co-authors, editors and funders may have the identifier in pending paperwork. Ask them before you change your record.
3. What will I tell people afterward? If colleagues cite your iD, a short note that the record has been deactivated and that the identifier is retained prevents confusion.

Then follow the account-settings action and the confirmation email. The approved facts do not specify the exact menu labels or the wording of the confirmation message, so rely on what your own account settings show rather than on a remembered path from an older interface.

Distinguish removal at ORCID from requests elsewhere

This is the core limit of the task. ORCID can change its own record; it cannot be assumed to reach into every external system that once connected to it.

Deactivation does not necessarily remove name-and-identifier associations from external systems previously connected to ORCID. Source

Plan your follow-up as separate requests, each with its own owner and evidence trail:

• Ask each external system directly. Contact the publisher, repository, institution or funder that displays the iD and ask what their process is for updating or removing the association.
• Keep the request record. Note the date, the channel, the person or team you contacted and any reference number. This is your evidence if the association reappears.
• Update what you control. Edit your own website, CV and public profiles so they no longer present the iD as current contact information.
• Recheck later. Because the approved facts do not establish any automatic propagation, revisit the systems on your inventory table after a reasonable interval and record what changed.

Do not treat removal of a login connection, an edited profile or an empty page as proof that stored data has been deleted. Those are different events, and only the system holding the data can confirm deletion.

What not to expect

• Do not expect the identifier to vanish. It is retained by design.
• Do not expect search engines to drop every mention. The approved facts make no promise about search-result removal, and pages you do not control are outside ORCID’s reach.
• Do not expect external systems to update themselves. The approved facts explicitly leave open that associations in previously connected systems may persist.
• Do not expect a duplicate problem to be solved. Deactivation is a retirement action, not a merge.

A short checklist

• Confirm your goal is retiring one record, not resolving duplicates.
• Build the external-association table with what you can observe.
• Ask co-authors, editors and funders whether they still need the iD.
• Complete the account-settings action and the confirmation email.
• Record the date and what the record shows afterward.
• Send separate, documented requests to each external system.
• Update your own pages and profiles.
• Recheck the inventory after a reasonable interval and note any association that remains.

TraceSeek, the app covered by TruthsSeek, is a username search tool rather than an ORCID management tool. Its relevance here is narrow: if your inventory work raises a separate question about public accounts using your name, it can help surface public username matches as leads for your own verification. Public matches are not proof of ownership, and a username search is not a complete account inventory.