Tokenized Input Fields
Any input field on a Deck task can now be tokenized. Rather than limiting tokenization to a fixed set of fields, you choose exactly which inputs get protected. Sensitive values like account numbers, personal identifiers, or payment information stay encrypted and never appear in plaintext in logs, webhooks, or API responses.
- Field-level control: Tokenize any input field on any task. You decide what’s sensitive, not the platform.
- Universal coverage: Works across all task types and sources. No special configuration per integration.
- End-to-end protection: Tokenized values are encrypted at rest and in transit.
Available on Enterprise plans only.