Skip to content

Field Masking and Export

If the source datastore contains masked fields, the platform applies the masking policy before the exported data leaves the platform. This page explains exactly what gets masked, what does not, and how to opt out per export.

What gets masked

Field masking only affects histogram values inside Field Profile exports.

  • Field Profile exports: in the histogram_buckets column, the bucket value for any field under field masking is replaced with a sentinel placeholder so the statistical distribution of sensitive values is not exposed.
  • Anomaly exports and Quality Check exports are not affected by field masking. They don't contain raw field values.
  • Anomalies merged with source records carry source rows in their RECORD column. These are written to the enrichment destination as the source records output already stores them, so the export has no Reveal Masked Values option. In Qualytics row previews, RECORD stays masked even when masked values are revealed, and cannot be used to filter or sort the preview. This also applies to the source records output. Its RECORD field is marked masked, so profile histogram values are hidden by default.

Profile values can be revealed by Editors

The preview restriction does not prevent privileged access to stored profile values. A user with the Editor team permission on the enrichment destination can reveal the RECORD field's histogram values through GET /field-profiles/{id}?include_masked=true, or include them in a Field Profile export with Reveal Masked Values (include_masked: true). These values can contain full JSON records. Both reveal actions are recorded in the Platform Audit.

Where the masking is applied

Masking is applied while the platform prepares the export payload, before the data is handed off for writing. When masking is in effect, everything downstream (the write step, the network hop, and the enrichment destination) only ever sees the masked values for fields designated as sensitive.

How to reveal masked values

Two ways to opt out per export:

  • In the Export Operation modal: when you select Field Profiles as the asset type, a Reveal Masked Values toggle appears. Turn it on to include the raw histogram values in the exported output.
  • Via the API: pass include_masked: true on the POST /operations/run request. See API for the full request shape.

The toggle defaults to off. Revealing masked values requires the Editor team permission on the source datastore.

Audit trail

Every revealed masked export is recorded in the Platform Audit. See Settings → Audit for the audit log.