Data sources
WheRe eveRy numbeR on this site comes fRom
Transparency only counts if it also applies to the numbers that flatter us. This page starts with what we do not have, and names the status of everything else. Nothing here is marketing: it is the same table the code reads to decide what it is allowed to claim.
- Customer reviewsWe don't have it
- The reviews shown are sample data for this preview, labelled as such wherever they appear, and no rating is emitted as structured data. At launch a review can only be written against an order that shipped (FTC 16 CFR 465).
- Stock levelsWe don't have it
- We have none. There is no inventory system behind this build, so no page says a part is in stock and no product page emits an availability claim to search engines. Until a real inventory ledger is wired up, the honest answer is silence rather than a green dot.
- PricesEstimated
- Our asking price — what you would actually be charged, and what the engine and checkout compute from. Its derivation is an estimate anchored to live retail listings rather than a signed supplier feed, so it can drift from the market between updates. It is published as structured data because it is the real price; the provider feed that will keep it current is not connected yet.
- Component specificationsEstimated
- Compiled from manufacturer datasheets and drafted with AI assistance, not verified part-by-part against a physical unit. Good enough for the compatibility engine to reason with, not yet substantiated to the standard a published spec claim deserves — so specs are not emitted as structured data.
- Build ScoreModeled
- Computed by our engine from the parts you chose: value, balance, thermals, PSU headroom, noise and future-proofing, each with its formula and inputs visible. It is our opinion expressed as arithmetic, not a measurement, and every sub-score shows its own working.
- Noise (dBA)Modeled
- Modeled from the loudest component plus a fixed system margin. It is a comparison tool between configurations, not a figure you should expect to reproduce with a meter.
- Power drawModeled
- Modeled peak, not measured: CPU package power where the part publishes it, board TDP times a factor where it does not, plus fixed baselines and a transient margin. It sizes the PSU with headroom on purpose.
- Delivery estimatesModeled
- Modeled from ZIP code and method, in business days. An estimate, never a promise, and labelled as one at the point it is shown.
- Frame ratesSourced
- Real measurements from the cited source, shown with that source next to them. They are measured on the graphics card, not on the machine we would ship you — which is why the number is presented as a baseline the engine reasons from, not as your result.
- Product photographySourced
- Catalog photography gathered per part and matched on brand and model. It shows the part, not the specific unit you would receive, and cosmetic details such as packaging or revision markings can differ.
The rule the code follows
A page may show an estimate to a person, because a person can read the disclosure next to it. A machine-readable claim — schema.org data, a product feed — has no room for that context, so it takes a higher bar: only sourced data and our real asking price are published that way. That distinction is a single function in the codebase, and removing a disclosure would mean deleting the check that enforces it.
Related: what we store about you · all policies