# Privacy policy

> What we keep about you, where your prompts go, and your choices.

Effective October 9, 2026 · Version 1.0

## At a glance

- **Prompts:** We never store the text of your prompts or the model's responses.
- **Routing:** Your prompt passes through OpenRouter to the model's provider, which keeps data under its own policy.
- **Requests:** We keep a record of every request: model, tokens, cost, API key, client and time.
- **Chain activity:** Your wallet activity on Ethereum is public, and nobody can delete it.
- **Deletion:** Deleting your account clears your name, email and API keys. Request records stay.
- **Tracking:** We run no analytics or advertising, and we never sell personal data.

## 1. Who this covers

This policy covers three groups:

- **Account holders**, who sign in.
- **Token holders**, whose wallets hold INFERENCE or the launch token. You may never sign in, but your address and reward amounts appear in public reward files.
- **Visitors**, who read the site without signing in. We store nothing about you.

Deference is for people aged 18 and over.

## 2. What we keep

| What | Why | How long |
| --- | --- | --- |
| **Your account:** wallet address, display name, email, sign-up time and credit | Runs your account | Name and email until you delete the account; the rest stays |
| **Sign-in identity:** Privy user ID, email in normalized form, Google account ID | Gives free credit once per person, and opens the same account for every sign-in method | Kept after deletion |
| **Linked wallets** | Credits activations and claims from any of your wallets | Kept after deletion |
| **Sign-in sessions:** session ID, first and last use | Lets you sign out everywhere | 35 days after last use or sign-out |
| **API keys:** name, first and last four characters, a hash, limit, expiry, last use | Checks requests without storing the key | Kept, marked deleted |
| **Request records:** time, model, provider, endpoint, API key, token counts, cost, status, speed, and the client name and coding-session ID your tool sends | Billing, Activity, Usage and the reserve's spending reports | No end date; kept after deletion |
| **Credit records:** activations, charges and free-credit grants | Keeps the books | No end date |
| **Chain records we copy:** purchases, activations, transfers, reward shares and claims | Shows your history and computes rewards | No end date; public on Ethereum anyway |
| **Network statistics** | The Stats and Status pages | Totals only. A model or tool appears by name once it has 50 requests from 5 accounts. |
| **Test faucet claims:** address and time | One claim per address every 24 hours | Replaced by your next claim |

## 3. What we never keep

- The text of prompts and responses.
- Full API keys.
- IP addresses. We use them in memory for rate limits and never store them; our hosting provider sees the address your connection comes from.
- Passwords or card details. Deference has neither.

We run no analytics, advertising or session-replay scripts, and we never sell or rent personal data. Privy's sign-in code keeps its own analytics ID ([Who receives data](https://deference.si/privacy#recipients)). Everything stored in your browser is listed in [Cookies and storage](https://deference.si/cookies).

## 4. Where your prompts go

Deference sees each prompt in passing and keeps only the record.

1. Your tool sends the request to Deference with your API key. We check the key and your credit and hold the cost.
2. We forward the request to OpenRouter. On chat completions, embeddings and images we add an account tag: the first 32 characters of a SHA-256 hash of your account ID, never your name, email or address. On Messages and Responses the body goes exactly as your tool sent it, with any identifiers your tool put in it.
3. OpenRouter sends it to a provider that runs the model. OpenRouter keeps request metadata and stores prompt text only for accounts that turn logging on; it may sample a small share of prompts to categorize them without identifying anyone. Each provider keeps, and may train on, prompts under its own policy. Deference does not restrict which providers OpenRouter chooses today.
4. The response streams back to you. If you disconnect, the provider still finishes and we keep reading until it does, so the request is charged in full.

Read a provider's policy before you send it sensitive data. OpenRouter's is at [openrouter.ai/privacy](https://openrouter.ai/privacy).

## 5. Who receives data

| Company | What it receives | Why |
| --- | --- | --- |
| OpenRouter | Prompts and outputs in transit, the account tag, our site name | Routes requests to models |
| The model's provider | Prompts and outputs | Runs the model |
| Privy | Email, Google profile, linked wallets, passkeys, IP address and device details, and a client analytics ID its code stores on your device | Sign-in and embedded wallets |
| Google | The standard sign-in exchange, when you choose Google | Sign-in |
| Our Ethereum RPC provider | Your IP address and the addresses your browser reads, because your browser calls it directly | Reads and sends chain data |
| Our hosting provider | Everything in [What we keep](https://deference.si/privacy#keep), and connection logs | Runs Deference |

**Across borders.** OpenRouter, Privy and Google are based in the United States, so your data goes there.

**Authorities.** We share data with authorities only when the law requires it.

## 6. Your chain activity is public

Purchases, activations, transfers, swaps and reward claims are Ethereum transactions. Anyone can see them, link them to your address and keep copies, and we cannot change or delete them. Activation records which wallet's INFERENCE became Deference credit.

After every rewards epoch we publish the addresses and amounts of everyone who received rewards.

## 7. How we use data

- Run the API and the dashboard, and show your activity · contract
- Charge requests and settle credit · contract
- Give free credit once per person · legitimate interest
- Compute and publish rewards · legitimate interest
- Publish network statistics, folded as in [What we keep](https://deference.si/privacy#keep) · legitimate interest
- Stop abuse and enforce the [acceptable use policy](https://deference.si/acceptable-use) · legitimate interest
- Keep the books the law requires · legal duty

## 8. Deleting your account

**Delete account** is in Settings; you confirm by typing your address. It waits until none of your requests is running.

**Removed:** every API key is disabled and deleted, your name and email are cleared, every session ends, and all credit is given up.

**Kept:** the account with its wallet address, request and credit records, your sign-in identity and your linked wallets. The books and the reserve's spending reports depend on the records, and the identity stops the same person collecting free credit twice. Signing in again opens the same account, empty.

**At Privy:** your Privy account is separate. To delete it too, write to [support@deference.so](mailto:support@deference.so) and we will delete it through Privy.

## 9. Your rights

You can see, correct, export and delete your data, object to how we use it, and complain to your data protection authority.

**Correct:** change your display name in Settings.

**Export:** Usage has a CSV download of your requests.

**Delete:** see [Deleting your account](https://deference.si/privacy#deleting).

**Anything else:** write to [support@deference.so](mailto:support@deference.so) from the email on your account. If your account has no email, we ask you to sign a message with its wallet. We answer within one month.

## 10. How we protect data

- API keys are stored as SHA-256 hashes and shown once.
- Your session lives in an encrypted cookie that page scripts cannot read, and **Sign out everywhere** ends every session.
- All traffic uses TLS.
- The reserve's owner and operator use separate keys, and the contracts cannot be upgraded.
- If a breach affects your data, we tell you by email where we have your address, and on this site.

## 11. Changes and contact

Each new version is published here with its effective date and listed in the version history below. Questions go to [support@deference.so](mailto:support@deference.so).

## Version history

- October 9, 2026 · 1.0 · First published version.

Questions: support@deference.so