Review Si's proposal

Mask personal data

The data and personal-data step — choose which columns to mask, decide whether raw values may be stored, pick the processing region and consent to sending a masked sample to Si.

Once DataxLand has read your source, the Choose data and personal data step asks which columns hold personal data. An Admin or the Owner completes this step.

Choose the columns to mask

The Choose columns to mask screen has two groups:

  • Columns that may contain personal data: names, phone numbers, emails, addresses and so on that DataxLand detected.
  • Other columns: add a mask here if a column holds personal data that DataxLand missed.

Columns flagged pii in data_dictionary show From the data dictionary, always masked and cannot be unmasked. Free-text columns (notes, message bodies) are masked by default because they often contain phone numbers or addresses.

What masking and hashing mean

  • Masking: the value never enters Si's prompt; Si only sees the masked form.
  • Hashing: as soon as the data is loaded, the value is replaced by a hash with a salt unique to your workspace. You can still count unique customers and join tables, but nobody can read the original value back.

Storing raw values

The box Allow storing the original values of these columns in the workspace's own warehouse for later use is off by default. Turn it on and the original values are kept in your private warehouse (still masked from Si and never returned through the API, Si or MCP). The change applies from the next read. Only turn it on when you have a legal basis for storing them.

  1. Pick the Data processing region.
  2. Tick I agree to send up to 1,000 masked sample rows per table to the model above. so Si can read the sample.
  3. Click Confirm and let Si analyse. Si starts its analysis, which usually takes 1–3 minutes.

Whenever you add or remove a source, you come back to this step for the new data.

Markdown