Configure Data Privacy

Configure cardholder data redaction at ingestion, on SignalControl Edge, or both. Before enabling it, review About Data Privacy for its coverage, masking rules, and limitations.

Enable Cardholder Data Redaction

Redaction is off by default. You configure it per dataset under Settings → Datasets. To edit dataset settings, you need the Maintainer role on the dataset. Admin members always have it.

1. Open Settings → Datasets.
2. Select the dataset.
3. On the Overview tab, find the Cardholder data redaction section.
4. Enable Redact cardholder data.
5. Save the dataset.

Dash0 redacts telemetry that arrives after you save. It does not go back over telemetry it already stored. To stop redaction, disable Redact cardholder data. Values that Dash0 already masked stay masked.

Redact on SignalControl Edge

To mask cardholder data before telemetry leaves your network, add the dash0redaction processor to the pipelines of your edge collector. On the edge, the processor redacts everything it receives. It does not read the dataset setting. Adding the processor to a pipeline turns redaction on.

This example adds the processor to the logs pipeline of the reference collector configuration. Add it to the traces and metrics pipelines in the same way:

processors:
  dash0redaction:
    metric_recorder: dash0metricrecorder/metering   # records the redaction metrics; without it the processor still redacts but records none

service:
  pipelines:
    logs:
      receivers:
        - otlp
      processors:
        - memory_limiter
        - dash0resource
        - dash0metering/logs
        - dash0filter
        - dash0redaction   # after every processor that adds or rewrites telemetry content
        - batch
      exporters:
        - dash0signaltometrics
        - otlp/dash0

Follow these rules when you add the processor:

• Place it after every processor that changes content: The collector marks each resource as redacted as soon as dash0redaction has run on it, and Dash0 does not scan marked resources again. A processor after dash0redaction that adds or rewrites content can therefore send unscanned values to Dash0.
• Reuse the existing metric recorder: Point metric_recorder at the dash0metricrecorder/metering extension that the metering setup already runs. A recorder extension supports exactly one drain receiver, so do not add a second one.
• Run the standalone edge collector: The processor ships in the standalone SignalControl Edge collector image. The edge collector that the Dash0 operator deploys on Kubernetes does not include it.

Combine Edge and Ingestion Redaction

When an edge collector has scanned a resource, Dash0 skips that resource at ingestion. It neither scans it again nor counts it again in the redaction metrics.

A single dataset can receive telemetry from an edge collector and from sources that send to Dash0 directly, such as a cloud integration. Dash0 decides for each resource:

• Telemetry that passed dash0redaction on an edge collector: The edge collector already redacted it. Dash0 does not scan it again, whatever the dataset setting.
• All other telemetry: Dash0 redacts it only if the dataset has Redact cardholder data enabled.

If a dataset receives telemetry from any source that does not pass through your edge collector, enable the dataset setting as well.

What Gets Redacted

See redaction coverage and masking rules for the fields scanned and the values Dash0 stores.

Limitations

Review the redaction limitations before relying on this control. Redaction does not certify a dataset as free of cardholder data.

Monitor Redaction

Use Monitor Data Privacy to verify that redaction ran and distinguish scanned, redacted, and skipped items.

Further Reading

• About SignalControl Edge — Process telemetry inside your own network before it leaves, where you can add source-side redaction.
• Access Control — Roles and dataset permissions, including who can edit dataset settings.
• Datasets — How datasets separate telemetry and how to route data into them.
• Filter Out Spam — Drop telemetry by explicit rule when you want a signal gone rather than masked.
• Understand Web SDK and Data Privacy — Source-side filtering and IP anonymization for browser telemetry.