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

# Data redaction

> One config per Operata account controls which CTR fields the Cloud Collector ships. Three endpoints read, replace, and remove it.

The redaction config is a single JSON document stored against your Operata account. It tells the Cloud Collector which CTR (Contact Trace Record) fields to keep or drop before contact trace records leave AWS for Operata. One config per account. Three endpoints manage it.

## Endpoints

| Operation                                                    | Endpoint                               | Use it to                                                                              |
| ------------------------------------------------------------ | -------------------------------------- | -------------------------------------------------------------------------------------- |
| [Get redaction config](/docs/api-get-redaction-config)       | `GET /v1/config/REDACTION_CONFIG/json` | Read the active config. Returns `404` if none is set.                                  |
| [Update redaction config](/docs/api-update-redaction-config) | `PUT /v1/config/json`                  | Replace the active config with a new allow-list or deny-list. Full replace, not patch. |
| [Delete redaction config](/docs/api-delete-redaction-config) | `DELETE /v1/config/REDACTION_CONFIG`   | Remove the active config. The collector reverts to the privacy-first default.          |

Each endpoint is idempotent. See [Idempotency](/docs/api-idempotency) for the per-method contract. `PUT` is a full replace — fields you omit from the new body do not survive the call.

## Config shape

The config is one of two shapes, distinguished by `value.type`:

* `WHITELIST` — allow-list. Ships only the mandatory CTR fields plus the fields you name.
* `BLACKLIST` — deny-list. Ships every CTR field except the ones you name.

```json theme={null}
{
  "key": "REDACTION_CONFIG",
  "value": {
    "type": "BLACKLIST",
    "fields": [
      "Attributes.CustomerDetails"
    ]
  }
}
```

The mandatory CTR fields (for example `ContactId`, `InitiationTimestamp`, `Queue.Name`) ship regardless. A deny-list cannot remove them; an allow-list cannot omit them.

With no config in place, the Cloud Collector applies the privacy-first default and ships only the mandatory CTR fields. The endpoints return `404` in that state.

## Related

* [Get redaction config](/docs/api-get-redaction-config) — inspect what is in effect.
* [Update redaction config](/docs/api-update-redaction-config) — replace the active config.
* [Delete redaction config](/docs/api-delete-redaction-config) — remove the config and revert to the default.
* [Configure CTR redaction](/docs/guides-configure-ctr-redaction) — the step-by-step rollout guide.
* [Contact trace records](/docs/contact-trace-records) — the CTR data model the `fields` array references.
* [Errors](/docs/api-errors), [Rate limits](/docs/api-rate-limits), [Idempotency](/docs/api-idempotency), [Versioning](/docs/api-versioning) — shared API conventions.