Frequently Asked Questions#

What types of data can Redactify detect?#

Redactify ships with a recommended pattern library covering SSNs, credit cards, API keys, bearer tokens, EINs, phone numbers, and common PII keywords. The library is not active by default — you copy the patterns you care about into Redactify’s settings during install. You can also add custom regex patterns for proprietary formats or industry-specific identifiers.

Is the original data stored anywhere?#

No. Redactify permanently redacts the sensitive information from the record and provides a sealed audit trail for compliance purposes. The sensitive text itself is never stored by Redactify or OrangeMage.

Can I add custom redaction patterns?#

Yes, you can define custom regex patterns tailored to your specific industry or compliance needs from the Redactify settings page.

Does Redactify scan historical data?#

Currently, Redactify listens for newly created and updated engagement records to redact sensitive data in real-time.

Can Redactify help with PCI-DSS compliance?#

Yes. Credit card numbers in email threads or call notes violate PCI-DSS. Redactify detects and silences them automatically, removing the need for manual review and reducing your compliance risk.

Which fields does Redactify scan?#

Redactify scans the standard text fields on HubSpot engagement records: email body and subject, call body, meeting body, note body, and task body. You can narrow this list in settings if you only care about a subset (for example, notes and email bodies only).