Skip to main content
PII detection metadata is attached to text content when your network has PII detection enabled server-side. The native SDK helpers let apps read detected entities and produce redacted display text without changing the original post, comment, or message.
This page covers the client SDK surface only. Feature enablement, quota, billing, and moderation-console behavior are product or backend concerns and are intentionally not documented here.

SDK Surface

Data Model

Each detected entity is represented as a PII item.

Categories

The current native SDK helpers define dedicated categories for these values.
Handle unknown categories deliberately. The server can introduce category strings before every client UI has a named enum case.

Parameters

Read and Redact

Use getPIIData() when you need entity metadata for moderation UI, highlighting, or audit views. Use redactedText(...) when the app should display masked text.

Behavior Notes

  • Redaction is non-destructive: it returns a string for display and does not change the stored text.
  • The native helpers skip PII ranges that overlap with mention ranges so user and channel mentions are not accidentally masked.
  • Metadata can be empty even when content is text. Treat an empty list as “no PII metadata on this object”, not as a detection failure.
  • Android redaction is available on Data.TEXT; non-text post, comment, or message data returns no redacted text through this helper.
  • TypeScript and Flutter do not expose public PII helper methods in the current SDK source, so do not document getPIIData() or redactedText() for those SDKs.