Skip to content
New: simulate any flow against real records before it goes live. See what's new →

Personal and sensitive data

Last updated 15 October 2026

Every field says what kind of data it holds. Solstral uses that to decide who sees it, where it may go, and how it is stored.

1. Classify a field

Go to Settings ▸ Objects & fields, open the record type, edit the field and choose its Data classification:

  • Not personal: ordinary business data.
  • Personal data: about a person and enough to identify them. A contact's name, email, phone and address start here.
  • Sensitive: personal data that would hurt if it leaked, such as a salary, a health note or an ID number. Only text, number, amount, date and link fields can be sensitive, and not the field a record is named by.

The field list shows a badge for each classified field.

2. Sensitive fields

A sensitive value is stored encrypted with your workspace's own key, so the database and its backups only hold scrambled text. Admins and the people who own the record (created it or co-own it) see the real value; everyone else sees dots and can't change it. It is never searched, put in a report or an email, copied into a flow's trigger, or sent to the AI. Making an existing field sensitive encrypts what is already there within a few minutes, and clears its change history, which held the values readable. A field that a formula, lookup or rollup shows can't be made sensitive until that field is changed.

3. Hide personal data from members

In Settings ▸ Members & access ▸ Access & visibility, turn on Hide personal data from members. Members then see emails, phone numbers and addresses masked (j•••@acme.com, •••• 1234) on records they don't own, and can't change them. Admins and a record's owners see everything. To let a team see personal data in full, turn on team permissions and give the team See personal data.

Everywhere else

  • The AI assistant and connected AI tools see personal data as the person using them would, and sensitive data never.
  • Solstral support sessions never see personal or sensitive data.
  • Values of classified fields are hidden in Solstral's own logs.
  • A report shared outside the workspace masks them.