Sensitive Fields: Store Tax File Numbers and ID Numbers Safely

Some details should never sit in plain text where every user, every export and every integration can read them: tax file numbers, driver licence and passport numbers, Medicare numbers, bank account numbers. Mark the field that holds them as Sensitive and TrustPager stores the value encrypted and only ever shows a masked copy, like ••••••782.

Mark a custom field as Sensitive

Open your CRM settings at https://app.trustpager.com/settings/crm, go to the custom fields for contacts, companies or opportunities, and add or edit a field. Tick Sensitive (next to the lock icon) and save. Only Text and Long Text fields can be Sensitive, and a Sensitive field cannot also be Must be unique.

Any values the field already holds are encrypted straight away. From then on, the field shows a Sensitive badge in your settings.

Once a field is Sensitive it stays Sensitive. To stop protecting a field, delete it.

What everyone sees

The real value is never kept on the record itself, so everything that reads the record sees only the masked copy:

• The contact, company and opportunity pages, and the lists and tables
• Exports, spreadsheets and reports
• The API and connected tools, including AI connectors
• Merge fields in emails and documents, and automation variables
• Fill with AI, which skips Sensitive fields

Anyone who can edit the record can still type a new value into the field. It saves as soon as you click away, and the field then shows the new masked copy. Use the x in the field to clear it.

Reveal the real value

Workspace admins see an eye button inside a Sensitive field. Click it to show the real value for 30 seconds. Every reveal is logged with who revealed it and when.

To let another role reveal values, open the role at https://app.trustpager.com/settings/permissions and set Sensitive Fields (reveal) to Read. Editors and viewers cannot reveal values unless you do this.

API keys never get this permission automatically, not even keys with full access, and AI connectors never get it by default. If an integration genuinely needs the real value, tick Sensitive Fields (reveal) on that key at https://app.trustpager.com/settings/api. It can then read a value with the reveal_sensitive_field tool (POST /v1/sensitive-fields/reveal), and every read is logged the same way.

Sensitive answers on forms

A form field that fills a Sensitive custom field becomes Sensitive automatically. You can also mark any Text or Long Text form field as Sensitive on its own: select the field in the form builder at https://app.trustpager.com/operations/forms and turn on Sensitive in its settings panel.

• The person filling in the form types into a hidden box, with an eye button to check what they typed.
• The answer is encrypted the moment it is saved. If they come back to the form later, it shows as saved and masked, and they can type over it.
• The submission page, the submission PDF, notification emails, the AI summary, automations and webhooks all receive the masked copy. Admins can reveal it from the submission page with the eye button.

Good to know

• A change waiting in your approval queue at https://app.trustpager.com/settings/approvals shows the masked copy too, and so do its notifications. The real value is only applied when the change is approved, and it is deleted if the change is rejected or expires.
• Copies made before a field was marked Sensitive (for example in an email that was already sent) are not changed.
• Because only the masked copy is stored on the record, a document or merge field prints the masked copy, not the real number.
• Searching and filtering on a Sensitive field only matches the masked copy.