TRUECLAIMRATES
Transparency · Solidarity · Accountability
Process

Verification, transparency, and the PII wall.

Two paths into the ledger. One standard for what publishes.

Verified shop path

  1. 01Shop registers and creates a profile.
  2. 02Admin reviews business identity (registration, license, address).
  3. 03Once verified, the shop publishes bills directly to its public record.
  4. 04Future bills auto-approve. Random audits continue.

Public submission path

  1. 01Anyone uploads a bill. Email confirmed.
  2. 02Submission queues for admin review.
  3. 03Reviewer scrubs customer PII server-side.
  4. 04Approved record appears against the shop / insurer.

The PII wall

Customer name, address, phone, email, VIN, license plate, claim number, and policy number live in an isolated table protected by row-level security. They are accessible only to admins and the shop that uploaded the document. They are never returned to anonymous queries — not via the API, not via export, not via inspection of the public ledger.

Never publicly visible
No public endpoint returns PII columns.
Server-side only
Storage bucket is private. Originals require admin signing.
Auditable access
Every read is governed by a database policy.