What you wrote
What a guarded app reads
Turning it on
Guard is set per connection:- Settings → Connected apps — flip the Guard switch beside an app you’ve already connected (the same switch is in Edit access). It applies on the app’s next request; nothing needs reconnecting.
- The consent page — when you connect a new app, the same switch is offered before you approve.
What is hidden
The built-in policy (Standard) replaces:
Strict adds email addresses and phone numbers.
Free-standing numbers are only treated as a card, IBAN or routing number when their checksum is valid, so order numbers and version strings are left alone.
Pay figures err on the side of hiding: an amount next to a word like “annual” or “offered” is replaced even when it isn’t a salary.
The team policy
A team owner or admin shapes the policy in Settings → Dexi Guard. It governs every note that belongs to a member of the team.- Level — Standard or Strict.
- Always hide these words — client names, project codenames, anything else. Matched as whole words, ignoring case.
- Property rules — match a property by name (
*matches anything, e.g.client*) and choose what a guarded app gets:- Hide the value — a placeholder.
- Replace with a code — a stable code such as
h_3f9a…. The same value always gives the same code within your team, so an assistant can group or match on it without reading it. - Always show — exempt a property the built-in rules would hide (say,
salary_band).
- When a note has restricted values — replace them with placeholders (the default), or hide the whole note from guarded apps.
How a guarded connection behaves
- Reading — every tool that returns note content returns the de-identified copy. Items carry
"guarded": true, andredactionswhen anything was replaced (see the note item). - Searching — keyword, regular-expression and semantic search, similar-note lookup, tag filters and tag counts all run on the de-identified copy. A search for a hidden value finds nothing.
- Writing — creating a note and appending to one work normally: what the assistant writes is stored as written, and the response shows it de-identified. Replacing a title or body that contains hidden values is refused, because writing back the placeholders would overwrite the originals; append instead.
- Bases —
query_base,get_base,create_base,update_baseanddelete_baseare not available, since a base filters and summarises on the real property values.list_basesstill answers. - Not yet checked means not visible — a note appears to guarded apps only once its de-identified copy exists. Notes you write or edit are checked within moments, and ones that arrive by feed, email or the web clipper within a few minutes; turning Guard on for the first time, or changing the policy, re-checks the whole library in the background, and each note reappears as it’s done. Settings → Dexi Guard shows the progress.
What Guard does not cover
Guard applies to apps connected over MCP. It does not change:- what you or your teammates see in the Dexi app,
- share links and published feeds, which show a note as written to whoever you give them to,
- exports and digest emails, which go only to the note’s owner.