Skip to main content

PII Data Protection

CrawlDesk’s default Personally Identifiable Information (PII) protection safeguards sensitive user data, such as names, emails, phone numbers, addresses, passwords, and other identifiers, within your data sources during crawling, indexing, and AI-driven interactions (e.g., via the "Ask AI" widget or API). This built-in feature ensures that sensitive information is automatically detected and handled to prevent unauthorized exposure in search results or API responses, aligning with privacy regulations like GDPR, CCPA, and HIPAA.

Integrated seamlessly into CrawlDesk’s workflows, PII protection applies predefined rules to secure sensitive data without requiring manual setup. For custom PII handling or specific compliance needs (e.g., unique data types or regulatory requirements), contact the CrawlDesk support team at contact@crawldesk.com.

Key Benefits of PII Protection:

  • Compliance: Meets global privacy standards to ensure regulatory adherence.
  • Data Security: Prevents sensitive data, including PII and passwords, from appearing in AI outputs or logs.
  • User Trust: Builds confidence by automatically protecting personal and sensitive information.

Managing PII Protection​

CrawlDesk’s PII protection operates as a default system behavior, requiring no manual configuration. Below are steps to leverage this feature.

Understanding Default PII Protection​

CrawlDesk automatically scans data sources (e.g., websites, PDFs, Google Docs, Confluence) during crawling for sensitive information, including:

  • Names
  • Emails
  • Phone numbers
  • Addresses
  • Passwords
  • Other custom identifiers Detected PII is either masked (e.g., replaced with [REDACTED]) or excluded from indexing, ensuring it does not appear in "Ask AI" widget responses or API outputs.

Requesting Custom PII Handling​

For tailored PII protection (e.g., detecting company-specific IDs, passwords, or unique patterns), submit a request via contact@crawldesk.com. Include details such as:

  • PII types to protect (e.g., employee IDs, proprietary identifiers).
  • Data sources involved (e.g., Notion, Google Drive).
  • Compliance requirements (e.g., GDPR, HIPAA).