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.

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