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

# Account Settings

This is where you control your profile, your linked wallet, the spending limits you choose for yourself, and your data.

***

## Your profile

* **Handle** is permanent after you claim it and can't be changed. Read more in [Handles](/using-sectoral/handles.md).
* **Display name** shows on your public profile, and you can update it at any time.
* **Email** is the address you signed up with, and it receives your receipts and alerts.

***

## Wallet link

Add or change the Robinhood Chain address that Sectoral sends payouts to and uses for on-chain activity. We check the address format before saving, so a bad address is rejected on the spot instead of being stored and causing trouble later.

***

## Personal spending limits

| Setting              | What it does                                                                                     |
| -------------------- | ------------------------------------------------------------------------------------------------ |
| Daily limit          | Blocks further outgoing payments after the day's total hits this amount. Set `0` to turn it off. |
| Monthly limit        | A firm cap for the calendar month. Set `0` to turn it off.                                       |
| Require confirmation | Adds an extra confirm step for any payment over $0.50.                                           |
| Auto top-up          | Tops the primary account back up when its balance gets low.                                      |

These apply to your own account only. Spending limits for an *agent* work through a separate system, the [Spend Policy Engine](/ai-agents/policy-engine.md), and are enforced on-chain instead of being stored as a preference. Keep the distinction in mind: agent limits are hard constraints, not settings.

***

## How runs behave

| Setting                     | What it does                                                                |
| --------------------------- | --------------------------------------------------------------------------- |
| Stream results              | Displays a payment as it progresses instead of only showing the final state |
| Save execution history      | Stores run outputs and receipts on your account so you can revisit them     |
| Share anonymised usage data | Opt-in product telemetry that never includes content                        |

***

## Exporting your data

**Export all data** gives you a single JSON file containing your accounts, payments, alerts, API keys, and webhooks, so everything you have here can go with you. It covers more than the payments-only export explained in [Showing Proof of a Payment](/privacy-and-cryptography/proving-a-payment.md). Choose this export for a full snapshot, and the other when your accountant or a regulator needs a decrypted payment history in particular.

***

## Deleting your account

When you request deletion, you are signed out immediately and your account and data are scheduled for permanent removal within 30 days. During that period, support can still undo it. After the 30 days pass, the deletion is final and cannot be recovered.

***

## Read next

* [Balance and Top-Ups](/using-sectoral/wallet-and-funding.md)
* [Showing Proof of a Payment](/privacy-and-cryptography/proving-a-payment.md)


---

# 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.sectoral.xyz/using-sectoral/settings.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.