I built a no-KYC privacy directory with incident‑based trust scoring (and a map of who's been sanctioned)

Description and use

A no‑KYC directory that assigns dynamic trust scores from an incident log and visualizes sanctions on a world map, helping users avoid services that require ID verification.

Problem

Users sign up for services that later require ID verification, often after payment, and existing lists do not disclose this upfront.

Outcome

A privacy‑focused directory that transparently shows KYC levels, trust scores derived from incident history, and a sanctions map, enabling users to make informed choices without ID verification.

Workflow

• Collect service data and note KYC requirements
• Store incidents with date, source, and score impact
• Calculate current trust score from incidents
• Derive trust score trajectory by walking incidents chronologically
• Render trust score chart only if incidents exist
• Build sanctions radar map from incident log filtered by country
• Provide side‑by‑side maps for 3/6/12 month snapshots
• Allow users to suggest edits for corrections

Evidence

It currently covers 400 services across 30 categories, 251 of which have a KYC level of 0 (no ID required at all).

Source

Every listing gets a privacy score, a trust score, and an explicit KYC level (0–2).

Source

The trust score isn't a static field an admin edits whenever they feel like it. It's tied to a service_incidents table…

Source

The second piece is the Sanctions & Restrictions Radar — a world map built from the same incident log…

Source