# How we protect your data

> Every part of Restless is designed to keep our customers and their data safe from the start.

Source: https://www.restless.ai/security

## Features

- Sensitive headers and fields are redacted on your server, before a log is uploaded.
- Recovery hints pass a secrets scan and two separate AI reviews before an agent sees one.
- Opening an end user's requests or profile in the dashboard is recorded in an audit trail.

## How we handle personal data

Restless records every call to your API. Sensitive values are stripped on your own server, so they never reach ours.

### Redacted on your server

The SDK redacts inside your own process, from requests and responses alike, before a log is batched for upload.

### Credentials stripped

Authorization, Cookie, Set-Cookie, Proxy-Authorization, X-API-Key and X-Auth-Token headers are redacted on every call.

### Sensitive fields too

Keys like password, token, secret, ssn, creditcard and cvv are redacted in query strings and JSON bodies, however deeply they're nested.

### Your rules on top

Add your own headers, body keys and query params in settings or in code. They add to the defaults, which always apply.

### Masked, not erased

A redacted value keeps its length, and a longer one its last four characters, so you can tell two keys apart without holding either.

### No caller IPs

The SDK doesn't send your callers' IP addresses to Restless.

### Every lookup on record

Opening an end user's requests or profile in the dashboard is recorded in an audit trail, with their email stored as a hash.

## When an agent reads sensitive data

An agent calling your API sees what your API sends it. What Restless keeps of that exchange goes through the same redaction as every other call.

### Your API decides what it returns

Restless doesn't rewrite your responses. It adds debug headers to every call and a debug block to errors, and the rest is exactly what your API sent.

### The logged copy is redacted

The copy Restless keeps is redacted whether the sensitive value went out in the request or came back in the response.

### Fingerprints carry no values

Errors are grouped from the redacted copy. A fingerprint built from an error message drops numbers, emails, URLs and quoted values first.

## Keeping it out of recovery hints

A recovery hint is written once per kind of error, not built per request, so a caller's data has no way into it. Every hint is scanned and reviewed before an agent sees it.

### Written once per error

A hint is saved against an error fingerprint, and every matching error gets that same text, word for word.

### No request data filled in

Values from the request or response, headers, query params and the caller's identity are never inserted into a hint.

### Links use the route, not the values

A hint's docs link uses the route template, like /users/{id}, never the real id. The page it opens shows only what’s in your OpenAPI spec.

### Checked for prompt injection

Restless checks an error for prompt injection before a model reads it, so a malicious request can't steer what the hint says.

### AI sees the error, not the caller

The model drafts from the method, status, route template, error reason, your OpenAPI operation, scrubbed support answers and the code that throws the error. Never full bodies, raw URLs or who called.

### Scanned for secrets

A scan catches emails, phone numbers, SSNs, card numbers, API keys, tokens, connection strings, internal hosts and IPs, and record IDs. It decodes base64, hex and URL encoding first.

## Related features

- [Agent Recovery](https://www.restless.ai/agent-recovery) — When an agent hits an error, the response tells it how to fix it.
- [Live Debug](https://www.restless.ai/live-debug) — See every call to your API, with the patterns behind your errors surfaced.
- [Workbench](https://www.restless.ai/workbench) — Filter your logs and replay any request to see exactly what failed.

## Setup

Setup is a breeze. Restless is tightly integrated with your API, so we install a small SDK. Don't worry, we walk you through every step of the way.

Run this in your API's repo:

```sh
npx restless init
```

Or hand the setup to your coding agent with this prompt:

```text
Set up Restless in this repo by running `npx restless init` and following the steps.
```

To try it on a demo API instead:

```sh
git clone git@github.com:restlesshq/demo.git && cd demo && npx restless init
```

Nothing is uploaded without your permission.

The CLI runs four steps:

1. **Map out APIs.** Locate your APIs, generate an OpenAPI (OAS) file, and write it to `.restless/`. An OAS file is the shape of your API: every endpoint, parameter, and response. Later steps use it to install the right adapter and wire up the middleware exactly. The scan points Claude Code, running locally on your machine, at your codebase to find your routes. Commit the `.restless/` folder along with your code; it's meant to live there.
2. **Install SDK.** The CLI detects the project runtime, selects its adapter, installs the Restless SDK and wires the request middleware.
3. **Test your setup.** Local traffic capture starts, and the CLI confirms requests are reaching Restless.
4. **Set up account.** Log in to claim your project on Restless.

Privacy: scanning runs entirely on your machine via your own Claude Code install. We don't see a single line of your code, and nothing gets sent to our servers at that step.

## More from Restless

- [Restless](https://www.restless.ai/index.md): Restless makes your API self-improving. Every API call, support question, and error leaves it better for the next request.
- [Features](https://www.restless.ai/features.md): A new surface for your API: a public, LLM-first hub that gets every caller started and keeps them moving.
- [Documentation](https://www.restless.ai/documentation.md): Restless generates your API documentation from your endpoints and the tools your team already uses, and keeps it current every time your API changes.
- [Getting Started](https://www.restless.ai/getting-started.md): Onboarding is the most important part of your developer experience. Restless makes it easy for your developers to get their agent set up and ready to build.
- [Agentic docs](https://www.restless.ai/agentic-docs.md): Restless isn't just agent-friendly docs. It's the only documentation platform built AI-first. There's a UI for humans, but the docs are shaped to make agents successful.
- [Workbench](https://www.restless.ai/workbench.md): The Workbench sits at the bottom of your docs and gives developers a view into everything that's happening: view and filter logs, see what went wrong, and fix issues.
- [Agent recovery](https://www.restless.ai/agent-recovery.md): When an agent hits an error on your API, it usually gives up and you never hear about it. Restless catches the failed call and tells the agent how to fix its request and retry.
- [Human support](https://www.restless.ai/human-support.md): When a developer hits something AI can't fix, a human can step in and answer the question. Every answer becomes part of the context, and makes the next question easier!
- [Live Debug](https://www.restless.ai/live-debug.md): Your users build on your API with agents, and those agents hit errors in production. Live Debug gives them every request in full, over MCP and the Workbench, so a failing call is quick to trace and fix.
- [MCP server](https://www.restless.ai/mcp-server.md): Give agents the ability to do more than just write code. Give them access to do everything they need to build on your product, such as reading docs, debugging API calls and updating settings.
- [AI Traffic](https://www.restless.ai/ai-traffic.md): Your API and docs get a lot of AI traffic now, and most of it is invisible. Restless shows you what AI is actually looking for, broken down by who is asking.
- [Self-updating docs](https://www.restless.ai/self-updating-docs.md): Restless reads resolved support conversations, pulls out the part that applies to everyone, and drops it in an inbox to review. Approve it and it becomes context the next person finds on their own.
- [Solicit feedback](https://www.restless.ai/solicit-feedback.md): When an agent hits something confusing in your API, it usually just gives up. Restless adds a send_feedback tool to your MCP server, so the agent can tell you what tripped it up.
- [Sign up](https://app.restless.ai/signup)
