Skip to content
Skip to main content
First Response & Preservation Operational Explainer

What should be recorded about visible usernames and account IDs?

Record the exact stable account identifier, the display name and the service and screen on which each appeared. Their relationship is more useful than either value in isolation.

Preserve exact values and account context

Capture visible usernames, handles, email addresses, telephone numbers, profile URLs, account numbers and provider-generated IDs with punctuation, symbols, capitalisation and leading zeros intact. If a value is partial, retain only what can be seen and label it incomplete.

A contact-list name may be a label saved locally by another user. A public display name can be duplicated or changed. Where an underlying handle or provider ID is shown, preserve both it and the friendly name.

Record the device, application, webpage, profile, workspace or tenant associated with the value. If several accounts are visible, note which one is active without switching between them.

Identifiers anchor enquiries but do not prove users

Avoid entering settings or opening profiles solely to find more detail; those actions may create audit records or reveal activity to another user. Provider or acquired device records can supply missing identifiers later.

A person's claim that an account is theirs is a separate reported fact. Linking an identifier to a person requires supporting provider, device and contextual evidence.

Key takeaway

Preserve stable account identifiers exactly and with their service context, while separating them from changeable labels and claims about who used the account.

Reference: FRP-025First Response & Preservation