Last updated: April 6, 2026
The Protocol collects the minimum data necessary to provide verifiable AI usage records. Here is the complete list:
| Data | How Obtained | Stored? | Public? |
|---|---|---|---|
| API Key Hash | SHA-256 of your API key, computed at the gateway | Yes (D1 database) | Yes (leaderboard) |
| Model Name | Extracted from AI provider response | Yes | Yes |
| Token Count | Extracted from AI provider response (.usage field only) | Yes | Yes |
| Wallet Address | Provided by you (optional) | Yes | Yes |
| Timestamp | Time of request | Yes | Yes (via API) |
| API Endpoint Path | e.g., /v1/messages | Yes | No |
| Cryptographic Signatures | Generated by gateway | Yes | Yes (for verification) |
We do not read, parse, store, log, or retain the content of your AI prompts or responses. Ever.
The gateway pipes your request and response bodies as opaque byte streams. The only field extracted from the response is the .usage object (token counts). This is verifiable by auditing the open-source gateway code.
We also do not collect or store:
During the processing of each API request, the following data exists temporarily in memory within a Cloudflare Worker V8 isolate:
This data exists only in volatile memory, is scoped to a single request, and is garbage-collected when the request completes. It is never written to persistent storage. Cloudflare's Worker runtime provides memory isolation between requests.
If you provide a wallet address, it is stored alongside your usage records and displayed on the public leaderboard. Wallet-to-hash bindings are permanent once established.
Important: If your wallet address is publicly linked to your identity (e.g., through ENS domains, public transactions, or social media), your AI usage patterns — including which models you use, how much you use them, and when — become publicly attributable to you.
We recommend using a dedicated wallet that is not linked to your public identity if you wish to maintain pseudonymity.
When you mint a Token-20 Proof, the following data is permanently recorded on the Base blockchain:
Blockchain data is permanent and cannot be deleted. This is an inherent property of blockchain technology, not a policy choice. Do not mint Token-20 Proofs if you are not comfortable with this data being permanently and publicly recorded.
Usage records in the gateway database are retained indefinitely to support ongoing verification and Merkle tree integrity. We do not currently offer a deletion mechanism because:
If regulations in your jurisdiction require data deletion rights (e.g., GDPR Article 17), please contact us. We will work to find a solution that balances your rights with the technical constraints of cryptographic verification systems.
| Service | Role | What They Access |
|---|---|---|
| Cloudflare | Worker hosting, D1 database | All gateway data passes through Cloudflare infrastructure. See Cloudflare Privacy Policy. |
| AI Providers (OpenAI, Anthropic, etc.) | Upstream API providers | Your API key and request content. We are a transparent proxy — your relationship with the AI provider is governed by their terms. |
| Base / Ethereum | Blockchain | On-chain transaction data is public by nature. We do not control the blockchain. |
The token.nousai.cc dashboard uses localStorage to store your wallet address for convenience. We do not use cookies, analytics trackers, advertising pixels, or any third-party tracking scripts.
You have the right to:
We may update this Privacy Notice. Changes take effect when posted. We will update the date at the top of this page.
Questions about this Privacy Notice: github.com/nousworld/nous-token