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

# Data handling

> What Lasso Cloud records for each RPC request, where it lives and how long it is kept, and how it holds the provider credentials in a Custom profile.

# Data handling

This page lists what Lasso Cloud records when you send it an RPC request, and
how long each record is kept. Use it to answer a security review or decide what
can travel through a shared endpoint. The [privacy policy](https://lasso.sh/privacy)
covers account, billing and website data.

## Per request

| Record | What it holds | Kept |
| - | - | - |
| Usage totals | Per key, UTC day and profile: request count, compute units and USD charged. No per-request rows | With the account's billing records, with no automatic expiry |
| Key activity | Per key: hourly request and charge counts, and failures grouped by error code, category and provider | In memory on each node, 24 hours |
| Error log line | For a failed request: chain, method, provider, latency, retries, error code and category | In the hosting platform's rolling log window; Lasso doesn't archive logs |
| Dashboard activity | Routing events: account, chain, method, strategy, provider, transport, duration and result. No params | In memory on each node, 60 seconds |
| Operational metrics | Request counts and latency by profile, chain, provider, method and transport. Custom profiles count as `custom`, and account, key and request IDs are never labels | As aggregates in the metrics store |

Successful requests aren't logged. No log line, usage record or metric holds
JSON-RPC params or results.

## Request contents

* **Params and results** are sent to the provider that serves the request and
  returned to you. Lasso keeps neither. On a Custom profile, that provider is
  one you configured.
* **Signed transactions** are forwarded as the same bytes and not logged.
  When a provider rejects one with an error Lasso doesn't recognize, Lasso
  logs up to 512 bytes of the provider's error text, with any values from your
  request masked out.
* **Server errors:** when a request causes an error inside Lasso, the error
  report sent to the error-tracking service holds no request body, request
  headers or client IP address.

## IP addresses and credentials

* **Client IP addresses** rate-limit keyless key creation, purchases and guest
  dashboard access. The counters live in memory and expire within two hours.
  IPs aren't logged or stored.
* **API keys** are stored encrypted, with a SHA-256 hash for lookup.
* **Provider URLs, keys and headers** in a Custom profile: see
  [how Lasso holds your provider credentials](#how-lasso-holds-your-provider-credentials).
* **Feedback** sent to `/api/v1/feedback` keeps your message and a SHA-256
  digest of the key or IP that sent it, for 180 days.

## How Lasso holds your provider credentials

A Custom profile holds the URLs, API keys and headers you give it for your
providers. Many providers put the key in the URL path or query, so Lasso
treats the whole URL as a credential.

| Where | What Lasso does |
| - | - |
| Database | Provider URLs, WebSocket URLs, API keys and headers are encrypted with AES-256-GCM by the application before they're written. Lasso decrypts them in memory to send your requests |
| API responses | Provider names, status and learned knowledge only. URLs and header values are never returned, and the YAML export replaces them with environment references |
| Revisions | Each saved revision keeps an encrypted snapshot of the document. Snapshots are never printed in logs |
| Logs and error reports | A provider appears as its origin (`https://host:port`). The path, query and user info are removed before a log line or error report is written |
| Metrics | Custom providers count as `custom`; no provider URL or host is a metric label |
| Deletion | `DELETE /api/v1/profiles/{slug}` removes the profile with its chains, providers and every revision, and every Lasso server drops its in-memory copy |
| Backups | Database backups expire on the database host's retention schedule. Credentials stay encrypted in them |
| Staff access | Encryption is done by the application. Only Lasso's operator holds production access, and customer credentials are not read outside an incident you report |

## Limits

* To delete usage records with your account, email `support@lasso.sh`. Billing
  and legal obligations can require keeping some records.
* To keep request data entirely on your own infrastructure, run
  [Lasso RPC Core](https://docs.lasso.sh/introduction.md) yourself.

## Next

* [Routing evidence](https://docs.lasso.sh/cloud/observability.md): what each response tells you about
  where it went.
* [Support, security and lifecycle](https://docs.lasso.sh/support-security-lifecycle.md): live status,
  incidents and vulnerability reports.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.