Numbers
What has moved through this deployment, live from the same counters the server keeps. Counting.
Fetching the counters.
Secrets sealed in a browser or terminal and handed to this server as ciphertext.
POST /api/secret·total accepted
Reads that handed ciphertext back. Decryption happens on the reader's device, so this is where our knowledge ends.
GET /api/secret/{id}·views spent
Secrets that spent their final view. The ciphertext is dropped in the same step, so there is nothing left to steal.
atomic consume·final view spent
Everything ever accepted, measured after encryption. We can weigh it, but we cannot read a byte of it.
sealed client-side·running total
Of everything created, · were answers to an ask link, sealed to a keypair the asking browser made.
Who sent anything, who opened it, what any of it said, or which secret was a file rather than text. The server stores ciphertext it cannot read and keeps no per-secret records beyond the burn receipt each sender can already see. These totals are the whole dataset: there is no second, more detailed one.
no accounts·no cookies·no per-secret logs·curl /api/stats and check