Masked in Your Tab
Detectors run as you type and replace each sensitive value with a placeholder. You read the masked text before anything is sent, and switch any kind off when the answer needs it.
Opaq is building privacy-focused AI inference on Robinhood Chain. Today it takes the emails, keys, numbers and names out of a prompt inside your own browser, shows you exactly what would leave, and turns every answer into a receipt you can anchor and check later.
Opaq reduces what a prompt exposes and lets you prove what was asked and answered.
What is Opaq? A private request page and a small proof layer on Robinhood Chain. Your browser masks the request, a responder answers the masked text, and your wallet can anchor a hash of both. The bigger plan is confidential inference, where even the machine running the model cannot read the request; that part is planned and labelled as such everywhere on this site.
Detectors run as you type and replace each sensitive value with a placeholder. You read the masked text before anything is sent, and switch any kind off when the answer needs it.
One 32-byte hash binds the masked request, the answer, the model and a salt only you hold. Your wallet records it on Robinhood Chain; the texts never go on chain.
This site stores no request and no answer. Your word list and receipts stay in your browser.
Keys, secrets, cards, emails, bank numbers, addresses, phones and IPs, plus the names you add yourself.
Open the private request page, paste a draft and watch the masked version appear. No wallet needed until you seal.
Masking, answering and proof, connected in one flow you can follow step by step.
Nine detectors run on every keystroke: private keys, API secrets, card numbers that pass the Luhn check, emails, IBANs, wallet addresses, phone numbers, IP addresses and the words on your own list. Each value becomes a numbered placeholder, and the same value always gets the same one, so an answer stays coherent.
[EMAIL_1]sk-proj-a1b2… → [SECRET_1]+44 20 7946… → [PHONE_1]Dana Reyes → [NAME_1]Without a provider key on the server, a small deterministic demo answers inside your browser and nothing leaves at all. With one, only the masked text is forwarded over HTTPS to a third-party model provider, which can read it while it answers. The server refuses any text that still holds a key, a secret or a card.
Every answer can be sealed into one 32-byte hash of the masked request, the answer, the model id, a random salt and your address. Your wallet records the hash on a tiny ledger with no admin. Whoever holds the receipt file can recompute it and match the record; one changed character breaks it.
Figures on this section are read from Robinhood Chain when the page loads, not typed in.
The latest block, the gas price and the Chainlink ETH price come from Robinhood Chain through this site's read-only relay. Once the receipt ledger is deployed, its record count shows here too.
| Field | Value |
|---|---|
| network | Robinhood Chain · 4663 |
| latest block | reading… |
| block time | — |
| gas price | — |
| ETH / USD | — |
| receipt ledger | live · … receipts |
Each record on the ledger is small and public. The author address is the only identity it carries, and the hash reveals nothing without the texts and salt you keep.
Masking and the demo answer are free. Anchoring is one small transaction your wallet pays to the network; the estimate uses the live gas and ETH prices.
An honest side-by-side with the two usual options.
| Paste into a chat | Run a model yourself | Opaq | |
|---|---|---|---|
| Privacy | |||
| Sensitive details removed before sending | Nothing leaves your machine | ||
| You see the exact text that leaves | Nothing leaves your machine | ||
| Requests kept by this service | Often stored for a period | On your own disks | None |
| Who can read the text while it runs | The provider reads all of it | Only you | Provider reads masked text; confidential compute planned |
| Proof of what was asked and answered | |||
| Effort | |||
| Account to create | Yes | No | No, a wallet only to seal receipts |
| Cost today | Plan or credits | Hardware up front | Free; gas only to anchor |
| Setup time | Minutes | Weeks | Open a page |
| Answer quality | Full model | Depends on your hardware | Demo now; full model when the operator adds one |
Want the full picture of what this does and does not protect?
Read the honest limitsPaste a receipt file. The hash is recomputed in your browser and, once the ledger is live, matched to the author's record.
The file holds the masked request, the answer, the model id, the salt and the author. Change any byte and the hash no longer matches.
Your browser reads the code deployed at the ledger address and compares it with the contract compiled from this site's open source, byte for byte. A full check with the creation transaction runs from the repository.
Nothing below is live. $OPAQ is not needed for anything on this site, and no rewards, discounts or returns are promised.
Planned: $OPAQ as credits for inference once paid requests exist, as the unit for fees on the developer gateway, and for access to service features. None of these is built; each will be described in the docs and the open code before it goes live.
The receipt ledger does not use the token, takes no fee and has no owner.
The developer side of the plan. Shown as a preview; nothing in this section is live.
The planned secure API gateway would apply the same detectors on the way in, forward only masked text, return a receipt with every answer, and show usage in a developer workspace. Today the same logic is open source and runs in the browser.
The detectors, the receipt formula, the ledger and its tests are open source. Encryption in transit is not privacy while a model runs, and a chain is public, not private; Opaq says which layer each part covers.
About Opaq, masking, receipts and what stays private.
No sign-up. Paste a draft, read the masked version, and keep a receipt of the answer.
Send a Private Request