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

# Overview

The Storage endpoints provide two complementary mechanisms for persisting private data server-side:

* **Private XML** — lightweight, account-scoped XML storage keyed by element namespace. Suitable for preferences and small structured data.
* **Vault** — encrypted, PCI/DSS-compliant storage for sensitive information (e.g. payment details). Returns an opaque `vaultId` so the client never needs to store the raw data locally. Vault items can be searched, shared via time-limited links, and individually deleted.

All endpoints require a valid JWT bearer token. Vault data is encrypted at rest and accessible only to the owning account (or via an authorized vault link).

## Endpoints

| Endpoint                                                                 | Description                                                                                    |
| ------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------- |
| [Save private XML](/neuron-api/api-reference/storage/save-private-xml)   | Save (or overwrite) a private XML document on the server, scoped to the authenticated account. |
| [Load private XML](/neuron-api/api-reference/storage/load-private-xml)   | Retrieve a previously saved private XML document.                                              |
| [Store in vault](/neuron-api/api-reference/storage/store-in-vault)       | Store sensitive tagged data in the encrypted vault. Returns a `vaultId` for future retrieval.  |
| [Get from vault](/neuron-api/api-reference/storage/get-from-vault)       | Retrieve vault item data by `vaultId`, optionally returning masked values.                     |
| [Search in vault](/neuron-api/api-reference/storage/search-in-vault)     | Search vault items by type, client ID, or tag values.                                          |
| [Delete from vault](/neuron-api/api-reference/storage/delete-from-vault) | Permanently delete a vault item by `vaultId`.                                                  |
| [Create vault link](/neuron-api/api-reference/storage/create-vault-link) | Generate a signed, shareable URL for a vault item with optional TTL and use-count limits.      |
| [Content](/neuron-api/api-reference/storage/content)                     | Retrieve content referenced by a vault link URL.                                               |

## Private XML vs. vault

|            | Private XML         | Vault                              |
| ---------- | ------------------- | ---------------------------------- |
| Encryption | No                  | Yes (PCI/DSS)                      |
| Access     | Account only        | Account + vault links              |
| Key        | XML namespace       | Opaque `vaultId`                   |
| Masking    | No                  | Yes (per tag)                      |
| Shareable  | No                  | Yes (via vault links)              |
| Use case   | Preferences, config | Sensitive data (e.g. card numbers) |

## Vault links

[Create vault link](/neuron-api/api-reference/storage/create-vault-link) produces a signed URL that can be distributed to third parties. Links can be:

* **Time-limited** — expires after a configurable TTL (seconds).
* **Use-limited** — becomes invalid after a set number of accesses.
* **Masked** — returns only the masked version of tag values.

Recipients use [Content](/neuron-api/api-reference/storage/content) to retrieve the data at the link URL.

## Related

* [Cryptography](/neuron-api/api-reference/cryptography/overview) — keys used to sign vault link requests.