> For the complete documentation index, see [llms.txt](https://docs.useprivatus.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.useprivatus.com/overview/account-types.md).

# Account Types

Privatus serves two kinds of account holders, humans and AI agents, across four tiers. Every account runs on the same foundation: a non-custodial, PDA-based smart account on Solana with confidential transfers on by default. The tiers differ in privacy depth, verification requirements, and agent capabilities, not in who holds the keys. That is always you.

***

## Human accounts

The account type for individuals and teams: your money, your keys, your privacy.

**Capabilities:**

* Hold USDG, USDC, and SOL; send and receive confidential transfers
* Claim a human-readable `.privatus` handle; your account address is a deterministic PDA derived from it, so the handle is the account
* Generate request links and QR codes
* Export decrypted transaction history for tax purposes
* Squads-based multisig for social recovery and hardware key rotation

**Tiers:**

* **Shadow Lite**: the default tier. Confidential amounts (Token-2022 confidential balances) on every transfer. Requires only an email and an on-chain wallet attestation.
* **Shadow Pro**: adds Layer 3 shielded state, committing balances and history to a commitment-tree shielded pool, with stealth meta-addresses so recipients are unlinkable by on-chain analysis. Requires identity verification and includes multisig by default.

**Privacy profile:**

* Confidential transfers on by default at every tier
* Full control over selective disclosure. Nothing is shared with a third party unless you generate a proof for it

***

## Agent accounts (Shadow Agent)

A wallet designed from the ground up to be held by an AI agent rather than a person: a first-class citizen of the agent economy.

**Capabilities:**

* Its own PDA-based smart account on Solana and a DID-compatible Privatus Agent ID, owned by the deploying operator's account
* Operates under a spend policy enforced on-chain by the Privatus agent program, not a server-side rule: per-request and daily limits, allowed domains and recipients, asset types, time windows
* Sends and receives x402 payments natively, with MPP for split-path settlement
* Supports multi-agent hierarchies: a parent agent can allocate budgets to child agents
* Surfaces every transaction to the operator's feed in real time

**Privacy profile:**

* Confidential transfers by default, same as any other account
* Optional human-in-the-loop approval gate above a threshold you set

See [Agent Accounts Overview](/agents-and-automation/agent-accounts-overview.md) for the full detail on how agent wallets are provisioned and governed.

***

## Shadow Enterprise

For organizations running humans and agent fleets together.

**Capabilities:**

* Everything in Shadow Pro and Shadow Agent, plus bulk agent deployment via API
* Multiple authorized signers with role-based permissions through Squads multisig
* Layer 4 full privacy: shielded pools with sender and recipient anonymity, kept clean of illicit funds through association sets
* Audit export formatted for standard bookkeeping and tax tools

Shadow Enterprise is gated by KYB verification and jurisdiction-specific compliance review.

***

## Choosing a tier

| Need                                                                | Tier              |
| ------------------------------------------------------------------- | ----------------- |
| Send and receive USDG privately as an individual                    | Shadow Lite       |
| Shielded account state and stealth addresses                        | Shadow Pro        |
| Let an AI system transact on your behalf, within limits you control | Shadow Agent      |
| Deploy agent fleets with full privacy and bulk tooling              | Shadow Enterprise |

A Shadow Agent account always answers to the operator account that deployed it. It cannot exist independently, and its spend policy is always set and modifiable by that operator, on-chain. Autonomy for the agent, authority for you.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.useprivatus.com/overview/account-types.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.