How SCDB knows

Steam Community Database (SCDB) records what a Steam surface showed when it was read. This page is how those records are named. It is not a Steam catalog, not a market index, and not an operations console.

One account, one identifier

SCDB joins on SteamID64. A vanity URL, a persona, SteamID2, and SteamID3 are display forms. They become useful after Steam resolves the number. Search accepts those forms; storage does not treat them as keys.

Eight surfaces

People, Communities, Library, Published, Progress, Collection, Audience, and Trust stay separate. SCDB names a surface only from a stored field. A missing module is omitted or marked not indexed, private, unavailable, or stale. There is no composite coverage score.

Layer and state

Every rendered value carries a layer (where it came from) and a state (how complete it is). Public Steam, the SCDB bot once you add it as a friend, and SCDB Companion reading as you are different sources. A comment or award is other people's action, never the account owner's speech. A derived replay establishes nothing beyond its inputs.

Last successful first

If a later read fails or Steam starts hiding a surface, SCDB keeps the last successful observation and says so. Private is not empty. Empty is not private. Unknown is not zero. Guessing between them invents history.

Many-party facts stay whole

A match is one event with everyone who was in it. Flattening it into pairs would claim people are each connected to each other. They share that event. Hide and unshare apply only to extras you authorized. They do not take a match you were in.

What SCDB will not invent

SCDB does not guess alt accounts. It does not rank people by ban history. A ban is the fact Steam published, with the date we saw it. The design page shows the state vocabulary on a fictional subject so no real person is used as a demo.

The four connect steps are on How it works. What this host currently serves is Data status. What is stored, and how to erase a record you control, is Privacy.