IDENTITY AND
DATA IN COMMERCE.

Reference

Every transaction rests on an unstated assumption that the parties are who they claim to be. Identity is the infrastructure underneath commerce, and the design question is always how to prove enough without collecting more than you should hold.

GET STARTED →

What to know

Verification is graduated, not binary

Different actions need different confidence. An email confirms a channel; a document check confirms a person; an enhanced check confirms them against watchlists. Requiring the strongest check for everything excludes people who would pass a proportionate one.

Collect the minimum that answers the question

The safest data is data you never held. Confirming somebody is over eighteen does not require storing their date of birth, and confirming a taxpayer number is well-formed does not require keeping it.

Nobody verifies themselves

A check the subject can pass by asserting it is not a check. On GRAJ nobody approves their own verification, including administrators, and every decision records who made it.

Re-screening has a clock

Identity is not permanently true. Watchlist and background checks have a useful life, after which an unrepeated check is an assumption wearing the clothes of a fact.

Where to go next

KNOWING WHO IS WHO.

Every transaction rests on an assumption that the parties are who they say they are.

Read it

ONE IDENTITY, MANY ROLES.

A person is not their role.

Read it

DATA PRIVACY FOR SELLERS.

The moment you sell to a consumer you are processing personal data, and the rules follow the person rather than your address.

Read it

A RECORD NOBODY CAN EDIT.

Every meaningful action on GRAJ is written to a log that only ever grows.