Guides / Identities

How FiveM Player Identity Correlation Works

A player on FiveM is not one value, they are several: Discord, Steam, licence, hardware, IP and more. Identity correlation links those values into a single record so a person is recognised even when one of them changes. This guide explains how the linking works and why it beats a single-identifier ban.

The identifiers FiveM exposes

Each connection carries more than one way to be recognised. Treat every item below as a signal rather than a verdict:

  • Discord. A stable, human-facing identity that a player rarely abandons.
  • Steam. A long-lived account that survives many returns.
  • Licence. The FiveM identifier tied to the player's installation.
  • Hardware (HWID). The machine signature, useful but changeable.
  • IP and network signals. Connection context that can corroborate a match.

How records connect: the shared identifier

Correlation links records that share an identifier. If two records carry the same Steam account, or the same licence, or the same Discord user, they are treated as connected. The more identifiers two records share, the stronger the link.

The result is a small family of records around one person rather than a set of unrelated rows. New connections are compared against that family, so a fresh login that shares even one identifier is pulled back into the cluster it belongs to.

Why correlation beats single-identifier bans

A single-identifier ban holds only while that identifier holds. A player changes it and the ban stops matching. Correlation spreads the weight across several identifiers, so no single change breaks the link.

  • Changing an account leaves the licence and hardware threads in place.
  • Changing hardware leaves the Discord, Steam and licence threads in place.
  • Changing everything at once is far rarer and far harder than changing one value.

How foreign data stays masked across the network

Correlation is most useful when it can learn from a shared network, but that raises a fair question about privacy between communities. SentryX Guard answers it with masking: records that belong to other servers stay foreign to you.

  • Discord IDs remain visible, because they identify the person and support fair review.
  • Every other foreign identifier is masked, so you cannot read another community's data.
  • You see that a connection exists and how it links, without exposing other servers.

Masking is enforced server-side, so a masked value is never sent to the client in the first place. That policy is described further on the protections overview.

Privacy considerations

Correlation works best with restraint. Its purpose is defensive: recognising a returning player, not building a profile for its own sake. A sound approach keeps the data minimal, masks foreign identifiers by default, and limits who can see full details inside your own panel.

Access control matters here too. Decisions and full identifiers should be visible only to the people who need them, which is why role-based access sits alongside masking in SentryX Guard.

What you can do with it

  • Link a new connection to an existing record instead of starting from zero.
  • Screen every connection before it reaches the server, using the linked record.
  • Apply enforcement decisions consistently, backed by an audit trail.
  • Keep other communities' data masked while still benefiting from the shared signal.

SentryX Guard fingerprints connections across these identifiers, correlates them across the shared network, and screens every connection at the handshake. Start with the setup guide; the free tier supports servers up to 200 players, with paid tiers on the pricing page.

Frequently asked questions

How does one identifier link two separate records?

If two records share an identifier, such as the same Discord account or the same licence, correlation treats them as connected. The more identifiers two records share, the stronger the link, and the more confident the match.

Can I see other servers player data?

No. Across the shared network, records that belong to other servers stay masked. Discord IDs remain visible, and every other foreign identifier is masked. You can see that a connection exists; you cannot read the other community issues details.

Is correlation the same as fingerprinting?

They work together. Fingerprinting observes several identifiers at connection time. Correlation links the resulting records to each other and to known ones. Fingerprinting gathers the signals, and correlation makes sense of them.

Related guides

Recognise the person, not just the login

See everything SentryX Guard protects, screen your first connection with the setup guide, or compare tiers on the pricing page.