> ## Documentation Index
> Fetch the complete documentation index at: https://docs.deepmako.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Privacy

> What Mako stores, what it doesn't, and how to verify.

## Prompt data

Prompts and responses are **never stored**. Conversations are processed in memory, forwarded to the inference backend over HTTPS, and discarded after the response is returned. There is no prompt logging, no conversation history on the server, and no training on user data. Mako is a static fine-tune — the model weights do not change based on usage.

## Account and billing data

The gateway does store minimal account metadata for credit tracking and authentication:

| Data                     | Stored     | Purpose                                                         |
| ------------------------ | ---------- | --------------------------------------------------------------- |
| Wallet address           | ✅          | Credit balance association                                      |
| Credit balance           | ✅          | Deposit and spend tracking                                      |
| Total deposited / spent  | ✅          | Billing ledger                                                  |
| API keys                 | ✅ (hashed) | SHA-256 hashed before storage. Plaintext shown once on creation |
| Per-request token counts | ⚡ Optional | Credit deduction calculation. Disabled in privacy mode          |
| Timestamps               | ✅          | Account creation and key creation dates                         |

No personal information is linked to wallet addresses. No email, no name, no IP address logging.

## Tool data

When Mako executes tools on your behalf, those tool calls may interact with external services:

| Tool category    | External services                                     |
| ---------------- | ----------------------------------------------------- |
| On-chain queries | Public RPC endpoints (Ethereum, Base, Arbitrum, etc.) |
| Web search       | Brave Search API, DuckDuckGo                          |
| Page extraction  | Direct HTTPS fetch to target URL                      |
| Tweet reading    | Twitter/X via API                                     |
| Crypto prices    | CoinGecko API                                         |
| Knowledge search | Local — no external call                              |

These external calls are made server-side by the gateway. The third-party services receive the query parameters (addresses, search terms, URLs) but not your conversation context or wallet identity.

## Privacy mode

Set `PRIVACY_MODE=true` to enable zero-retention mode:

* **Usage logs disabled** — no per-request metadata is written to the database
* **Console logs redacted** — tool arguments, URLs, and search queries are replaced with `[redacted]`
* **Privacy headers set** — API responses include `X-Mako-Privacy: zero-retention`

### Response headers

Every API response includes headers so your client can verify the gateway's data posture:

| Header                  | Standard mode         | Privacy mode     |
| ----------------------- | --------------------- | ---------------- |
| `X-Mako-Privacy`        | `standard`            | `zero-retention` |
| `X-Mako-Data-Stored`    | `usage-metadata-only` | `none`           |
| `X-Mako-Prompt-Storage` | `none`                | `none`           |
| `X-Mako-Training-Data`  | `never`               | `never`          |

## Hosted gateway

When using the hosted gateway at `gateway.deepmako.com`:

* Prompts are not stored and not logged
* Prompts are forwarded to the inference backend over HTTPS/TLS
* The inference backend processes the request and returns a response — no data is retained
* Account metadata (wallet address, credit balance, usage totals) is stored for billing
* API keys are SHA-256 hashed before storage

## Verification

The gateway source code is available for inspection. Every privacy claim on this page is verifiable by reading the implementation.