Möbius
Guides

How Möbius masks personal data

Where personal data is shown as stored, where it is masked, and how to give one system the raw value.

Möbius masks personal data whenever it leaves Möbius. Inside the app, people who can read a table see it as it is. Access that goes around Möbius is governed by the warehouse.

Masking applies to columns classed personal or sensitive. To classify a column and choose its mask strategy (redact, hash or partial), see Meaning and personal data.

Where the data lands decides

What matters is where the rows end up, not who asks for them. The same person can see a value as stored on screen and receive it masked in a file.

How you read the dataWhere it landsPersonal columns
The web app's data gridA Möbius screenAs stored
The mobile appA Möbius screenAs stored
The in-app preview of a dataset held in placeA Möbius screenAs stored
Export CSV from the web appA fileMasked, always
An export to your S3 bucket, scheduled or Export nowA file outside MöbiusMasked, always
The Data API (REST, GraphQL) and Data MCP, with a service tokenAnother programMasked
The in-app assistant and your own AI tool over MCPA model or another programMasked
The certified view Möbius publishes in your own warehouseYour warehouseAs stored; your warehouse's controls apply

Who may read a dataset at all is unchanged: the dataset's access permissions decide that, on every one of these doors. Masking only decides what a permitted reader receives.

Export CSV is always masked

Export CSV on a dataset's Data View produces a file, so every personal or sensitive column in it is masked, even for the dataset's owner or a workspace Admin. Non-personal columns are exported as stored. The export is recorded in the audit trail together with the list of columns that were masked.

If someone needs a file with the raw values, the export is the wrong route: give a service token an unmask grant and pull the data through the Data API (below).

The same holds for exports to your S3 bucket: every column classed personal or sensitive is masked in every file, and an unmask grant never applies to an export.

AI tools always receive masked values

Answers from the in-app assistant and reads by AI tools connected over MCP return personal columns masked. There is no setting that turns this off. If an AI system genuinely needs a raw value, it reads through the Data API or Data MCP on a service token that holds an unmask grant for that column, like any other system.

Reading rows from a program

A program that needs a dataset's rows reads them through the Data API (REST or GraphQL) or Data MCP with a Data API service token. These doors serve certified datasets. Personal columns arrive masked. The Workspace API does not serve rows to tokens: a personal token (the one mb signs in with) or a Data or Management token is refused when it asks for a dataset's records, and mb has no command that reads rows.

Giving one system the raw value

When a system genuinely needs the raw value of a column, a workspace Admin gives that system's Data API service token an unmask grant on that column:

  1. In Settings → Integrations, open the token.
  2. Under PII unmask grants, tick the columns it may receive unmasked.

A grant is for one token, one dataset and one column at a time. Every query that returns unmasked values is recorded in the audit trail. Revoking the grant masks the next read again. The full steps are in Meaning and personal data.

Access that goes around Möbius

If someone queries your warehouse directly rather than through Möbius, Möbius does not see that read and cannot mask it. Use your warehouse's own access controls and masking for that path.

Example

Ana can read the customers dataset, whose mobile column is classed personal.

  • On the web data grid she sees mobile as stored.
  • She selects Export CSV: in the file, mobile is masked.
  • A script she writes with a Data API service token reads the same rows through the Data API: mobile arrives masked, for example 0412345678 as ••••••5678 with the partial strategy.
  • A partner system holds a service token with an Admin-created unmask grant on customers.mobile. Through the Data API it receives the raw value, and that query is recorded.

On this page