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 (international numbers written with a
+, US and UK national formats, and unbroken digits beside a word such as “mobile”).
Free-standing numbers are only treated as a card, IBAN or routing number when their checksum is valid, and a card must also start the way an issuer’s cards do, so order numbers, version strings and device IMEIs are left alone. Cards and IBANs are recognised however they are spaced or cased.
Pay figures err on the side of hiding: an amount next to a word like “offered” or “per year” is replaced even when it isn’t a salary. The exception is a line that reads as a price or a budget. When the only cue is a rate (“per year”, “annual”, “/hr”) and the line names something commercial (a plan, a budget, revenue, a price per seat), the amount is left alone, so “$96 per year per seat” stays readable. A line that also says “salary”, “earns” or “offered” is still hidden.
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). A value a rule hides is hidden throughout that note, not only on its property line. With a rule onclient*, a note carryingclient:: Halvorsen Logisticsalso has “Halvorsen Logistics” and “Halvorsen” replaced in its title and text, by the same placeholder or code. Each capitalised word of a name is covered on its own (“Greta” forcontact:: Greta Halvorsen); generic words such as “Logistics” or “Group” are not, and neither is a nickname or a name the note never puts in a property. By default this reaches one note at a time: another note that mentions Halvorsen without the property is left as written.
- Also hide a rule’s values — Elsewhere in the same note (the default), or In every note in the library. With the library setting, a name hidden by one of your own rules in any note is hidden in every note the policy governs, yours and your teammates’, by the same placeholder (or, for Replace with a code, the same code, so an assistant can follow one client across notes without reading the name). Notes that mention a newly added name are re-checked first and are not visible to guarded apps until they have been. Only names are shared this way: numbers, and the built-in pay, card and password properties, stay within their own note. A first name that is also an ordinary word (“Will”, “Grace”) is hidden wherever it is capitalised. When the property is removed, notes checked while it existed keep the name hidden until they are next edited.
- 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.