Five steps.
Two keys. One reader.
- 1
Keys are made in your browser
Selecting Generate keys creates a 3072-bit RSA keypair and a random 32-byte access token with the WebCrypto API. You download a recovery file containing them before anything is sent.
- 2
The request is sealed to staff
Your search fields are encrypted with AES-256-GCM; that key is wrapped with RSA-OAEP to the staff public key. The server stores ciphertext plus your public key — never your private key or the plain search details.
- 3
You pay by address, not by wallet
On the tracking page you choose to create a payment. You get an address, QR code, exact amount and network to send from any wallet. No browser wallet connection is requested.
- 4
Staff fulfil and seal the report
A staff member decrypts the request on their own device, researches it through lawful sources, and encrypts the report to your public key in their browser before upload.
- 5
You decrypt locally
Tracking polls every 15 seconds. When a report arrives, your private key decrypts it in this tab. Downloading plaintext needs an explicit click.
What this does not promise
- It is not anonymity. The server sees your IP address, timing, module type, price, payment metadata and refund address.
- It is not zero-knowledge. Authorised staff decrypt and read every request in order to fulfil it.
- Public blockchains are public. Payments can be traced on-chain.
- We do not claim direct integrations with any government registry.
Refused requests
Requests that look like stalking, intimate-partner surveillance, harassment, locating a person who does not want to be found, or monitoring a partner or former partner are refused. Public-record availability does not override access restrictions or privacy obligations.