# Security and compliance

> What each key can do, what to protect, and your responsibilities as a business on USD.NET.

## What can move money

| Who | Can | Can't |
| --- | --- | --- |
| A user | Everything in their own account; revoke your mandate at any time | Touch your wallets |
| Your server key | Spend the server wallet; charge users within their mandates | Charge above a mandate's limits, charge a user without one, read users without `read: true`, change the partner record |
| Your business wallet | Change the partner record (sites, server wallets, webhook, pause); spend its own balance | Charge users |
| Your page with connect.js | Ask the user to approve something | Sign anything itself |
| USD.NET | Run the network, seal blocks, deliver webhooks, apply [issuer controls](/usdt/issuer-controls) | Sign for any account |

## Protect

- **The server key.** In a secret manager, server only. If it leaks: **Pause** the record (charges stop at once), move the funds, replace the key ([how](/business/accounts#replace-a-server-key)).
- **The webhook secret.** Rotate it in usd.net/wallet/business if it leaks; the old one stops at once.
- **The business wallet.** A passkey wallet, or a recovery phrase kept offline. It controls the record.

## Don't

- Don't ask users for their recovery phrase or try to hold their keys. USD.NET never needs them and neither do you.
- Don't trust an address, amount or "paid" flag from a browser. Check on the server: `usd.mandate`, the transaction, the webhook.
- Don't use random ids for charges and payouts; use ids from your own records so retries can't double-charge or double-pay.

## Users' privacy

Accounts are [confidential](/wallet/confidential). You see a user's address, the payments between you and, with `read: true`, their balance. Nothing else about their account, and the public sees only that transactions happened. Treat what you learn as personal data under your privacy policy.

## Compliance

USD.NET screens bridge deposits and withdrawals against sanctions lists and may freeze addresses under its [issuer policy](/compliance/freezes); a frozen account can't be charged or paid. You remain responsible for your product and your users: the law where you operate and where they live, consumer protection and refunds, and any licence, age check or identity check your business needs. If you need to identify your users, do it in your own sign-up; USD.NET doesn't share who a wallet belongs to.
