Evidence Guide

Duplicate Database Guide

DejaVu turns messy evidence into clean public labels. This page explains what those labels mean and how traders should read them.

Local Database

Local Database means DejaVu matched the target against records maintained inside the DejaVu system. These records can include known duplicate-risk patterns, manually reviewed information and structured lists used by the scanner.

Live Database

Live Database means DejaVu checked a live intelligence layer at scan time. Live checks are useful because trading information can change, but live systems can also fail, rate-limit or temporarily return incomplete results.

Why private source names are hidden

Source names are simplified to protect the system from abuse. If every internal source and matching rule were exposed, bad actors could learn how to avoid detection or target the weakest part of the pipeline.

Understanding duplicate hits

A hit means DejaVu found evidence connected to the scanned target. The strength of that hit depends on the evidence type, how many records match and whether the result appears in one layer or multiple layers. More evidence usually means higher concern, but context still matters.

Understanding clean scans

A clean scan means no known hit was returned by the available evidence layers. It should be treated as useful information, not proof that the account or item is safe forever.

Confidence levels explained

Not every hit carries the same weight. A single, older, unconfirmed record is weaker evidence than several independent matches that agree with each other. DejaVu tries to reflect that difference in how a result is labeled, so a "possible" flag and a strongly-evidenced flag should not be treated as equally serious.

Why results can change over time

Duplicate-risk evidence is not fixed. New reports get reviewed and added, live sources get rechecked, and old records can be corrected if they turn out to be wrong. A username or item that scanned clean last week can return a hit later if new evidence appears, and the reverse can also happen if a report turns out to be a false alarm.

What DejaVu cannot see

DejaVu has no access to private trade logs, Roblox's internal systems or anything outside of its own database and public/community evidence. Items or accounts with no trading history anywhere in the community are harder to evaluate, and a clean result for a very new or very inactive account carries less weight than one with a longer trading footprint.

Best use: Treat DejaVu as a risk filter before trading, then combine the result with value checks, screenshots and normal community verification.