Overview
The Alchemer 'Redact sensitive data' integration uses Google’s 'Sensitive Data Protection' capabilities to automatically detect and redact sensitive information from survey data. This integration allows organizations to protect personal and confidential data by identifying sensitive content and applying de-identification rules before data is stored, routed, or passed to downstream system.
Common uses for the Alchemer Redact sensitive data integration
- Detect and redact personally identifiable information (PII) from survey data
- Protect sensitive survey responses before routing or storage
- Apply consistent de-identification rules across workflows
- Prepare sanitized data for downstream integrations and analytics
- Reduce compliance risk when handling sensitive information
What can the Redact sensitive data integration do?
- Inspect survey data for sensitive content
- Redact or transform detected sensitive values
- Return sanitized outputs for use in survey
You will need
- An inspectConfig object defining what sensitive data to detect
- A deifentifyConfig object defining how detected data should be redacted or transformed
-
An Alchemer plan that includes integrations and the Integration Manager permission enabled.
- Contact us if you are unsure if your plan includes integrations.
Setup Redact sensitive data integration in workflow
Tools & Utilities | Redact sensitive data
You will need:
- A valid inspectConfig object
- A valid deifentifyConfig object
- Survey fields containing data to inspect and redact
Configure the action
- Open your survey in Survey builder.
- Select Add New: Action.
- In the Add Action modal, scroll to the Integrations section.
- Select Tools & Utilities.
- Select Tools & Utilities | Redact sensitive data.
- Tools | Deidentify configuration: Enter your inspectConfig and deidentifyConfig objects in the respective textbox. The default is set to redact an email address.
- Tools | Select question to redact: Select the field in this survey that you want to redact. Only one field can be redacted per action. Add additional actions as needed.
- Save the action.
Status codes
- 200: Successfully redacted sensitive data
- 400: The external integration returned an error
Testing & Support
Testing and Validation
How to test
- Submit a survey response that triggers the integration action.
- Confirm the expected field has been redacted in the results.
- Use metadata for verification and debugging
How to verify results
- Inspect returned metadata values for redacted content.
- Use sanitized outputs in routing, conditions, or merge codes.
Monitoring Integration Activity
Where to find logs
- Go to Results → Individual Responses.
- Select the Redact sensitive data integration step.
What logs display
- Inspection inputs and redacted outputs
Troubleshooting
Configuration issues
-
Invalid or improperly formatted
inspectConfigobject -
Invalid or improperly formatted
deidentifyConfigobject
Redaction issues
- Sensitive data types not included in the inspection configuration
- Unexpected redaction behavior due to de-identification rules
FAQs
What permissions do I need?
Integration Manager permission in Alchemer and access to Google sensitive-data-protection features.
Integration Manager permission in Alchemer and access to Google sensitive-data-protection features.
When does the integration run?
When the workflow reaches the Redact sensitive data integration step.
When the workflow reaches the Redact sensitive data integration step.
Can I use multiple Redact sensitive data actions in one workflow?
Yes. Each action runs independently and can be chained as needed.
Yes. Each action runs independently and can be chained as needed.
Why isn’t my data being redacted?
Check that your
Check that your
inspectConfig includes the correct infoTypes and your deidentifyConfig defines valid transformation rules.
What if I need additional functionality?
Contact Alchemer Support for enhancement requests.
Contact Alchemer Support for enhancement requests.
