Steam's review data treats playtime-at-review, recent and lifetime playtime as different fields, and keeps review creation and update timestamps separate. A public excerpt may show one or more of these; read whichever number appears with its own time anchor rather than assuming a single current total describes the moment the text was written. Neither figure reconstructs daily activity, named co-players or relationship history.
Find public social profile clues with our TraceSeek app.
Separate the records a review can expose
Steam's review data keeps the review text's creation and update timestamps separate, and treats lifetime, recent and at-review playtime as distinct values measured in minutes. Treat any figures you actually see as separate records rather than one blended number. If a review text and a playtime figure appear together, ask which field that figure is: the value captured at review time, a recent-period figure, or a lifetime total. [Steam: review and playtime field definitions]
- Note the date the review text was created, and any update date if one is shown.
- Identify which playtime field is displayed before drawing conclusions.
A newer total is not the text's original context
Playtime-at-review is captured at that moment, while a lifetime total continues to accumulate. A review written after a few hours can therefore sit beside a much larger lifetime figure, and both can be accurate for their own moment. The point is time-anchoring: ask which clock a number belongs to. Treating a later cumulative figure as the context in which the text was written misreads the artifact. [Steam: review and playtime field definitions]
Why aggregate hours cannot rebuild a day
Even a precise cumulative total compresses everything into one sum. It cannot tell you which days were played, session lengths, time of day, whether play was continuous or in bursts, or what happened during the hours. Any narrative about a specific evening, a routine, or a pattern of contact is layered on top of a total. A hypothetical illustration: 40 hours at posting and 300 shown now are two snapshots of accumulated play, nothing about the 260 hours in between.
- Label the number: at-review snapshot, recent-period figure, or lifetime total.
- Write down what the aggregate does not show before suggesting any activity pattern.
The purchase fields explain one fact and no more
Steam review data distinguishes a Steam purchase from 'received for free', where the free option reflects the reviewer's own checked self-report box. Those fields do not identify who gave a copy, what it cost, or any personal relationship behind it. Read them as classification fields about how the review was categorized, not as a story about gifts, money or ties between people. [Steam: review and playtime field definitions]
- If the label matters to your reading, quote it exactly and stop there.
- Do not infer who paid, who gifted, or who knows whom from the label.
Do not people-build from hours
Cumulative playtime invites over-reading: guesses about lifestyle, income, sociability or relationships. None of that follows from an aggregate. Matching a username or avatar to other public posts can surface further public material, but a match never confirms identity, ownership or current activity, and coverage is not guaranteed. Keep observation and interpretation separate, and let unsupported parts stay blank.
- Write observations only as: this field, this value, this timestamp.
- Leave identity, intent and relationship claims out unless public text states them explicitly.
When the record is missing or unclear, stop there
If the review text, dates, or playtime figure are absent, private, inconsistent or ambiguous, record that precise limit and end the reading. Do not seek private records, do not try to identify the reviewer, and do not substitute a guess for the missing piece. A short honest entry such as 'review shown; playtime field not identified' is more useful than an inference built on gaps.
| observation | limit | next step |
|---|---|---|
| Review text with a creation date | Text reflects that moment only | Note the date beside any playtime claim |
| Playtime figure shown | Which field it is may be unclear | Identify at-review versus lifetime before comparing |
| Lifetime total | Cumulative aggregate; no daily detail | Record it as a cumulative figure, nothing more |
| No playtime field visible | Context for the text unknown | State the absence and stop the inference |
A short honest reading
Put the pieces in the order they were produced: quote the review text, cite its dates, label any playtime figure with the field it represents, and record any purchase field as a classification only. Then stop. This keeps a public excerpt useful as a dated artifact rather than a biography, and makes clear which claims would require information the public page does not contain.
A couple more questions
Does a higher lifetime playtime mean the review was written dishonestly?
No. Playtime-at-review and lifetime playtime are separate fields, and the lifetime total accumulates afterward. A larger total does not contradict the text's original context.
Can aggregate playtime tell me who someone played with or how often they play?
No. A cumulative total carries no session times, days, durations or companions. Any statement about co-players, routines or contact patterns would be invented rather than read from the artifact.
What should I do if the excerpt shows no playtime or no dates?
Record that exact gap and end the analysis. Note what is present, mark the missing element as not shown, and avoid substituting estimates or private lookups for the absent information.
Does a 'received for free' label identify who gave the copy?
No. It reflects the reviewer's own checked self-report about how they obtained the game. It does not name a giver, a price or any personal relationship.
Sources & editorial notes
Official references checked on October 24, 2026. Checklists, comparison tables and example wording are DateClues editorial tools, not official tests or validated risk scores.
General information. No guide or tool can certify a person’s identity, intentions or safety. Read our editorial standards.