Privacy

The add-on Privacy keeps customers’ personal data — phones, emails and domains — away from the employees who do not need it, and records who looked at what and when. It also holds the global blocklist: addresses and domains the product must never write to, whatever the channel.

Privacy add-on, Settings tab: the masking rules for contact channels and company domains and the manager-only reveal verb

Why you need it

A CRM holds all the contacts at once: customer phones, addresses and domains, plus their own employees’ details. Usually everyone with access sees everything. That is not always right — a contractor or a new intern has no reason to know every client’s personal data — and personal-data requirements ask you to show not only that you hid the data, but who looked at it and when.

The old choice was all or nothing: either a person sees everything or they are not let into the CRM at all. Privacy adds the middle option. A colleague works as usual — answers customers and runs deals — but a phone or an address shows as a mask instead of a value. If a value is really needed, it is revealed one row at a time, and every reveal leaves a journal entry.

What it does

  • A hide flag on an employee or on everyone. The hiding can be set for a specific person, or as the default for everyone: then everyone inherits it unless separately allowed the opposite. The interface shows who set the setting and when.
  • The mask is the same everywhere. Channel values are replaced identically on all surfaces: on screens, in API answers, in report rows and even in the export file. It is built in one place, not promised in words, so “visible in the report but not on the screen” cannot happen. Next to the value it shows what exactly is hidden: “channels masked”, “domains masked” or both.
  • Work does not break. Even behind the mask, a letter goes to the real address and a call dials the real number. Masking is about what is visible, not about what can be done. That is why an operator calmly answers a customer without memorising their phone number.
  • A value is revealed one at a time. Only an administrator can reveal a value, and every reveal is written to the journal: who opened which value and when. There is no mass “show all” button — that is deliberate, so access is always piece-by-piece and explainable.
  • The access journal. A separate Access Journal tab shows who viewed sensitive data: listenings of conversation recordings, reveals of values, reads of private notes. The journal is assembled from identifiers and words — the values themselves never enter it, so the journal does not become the very leak it guards.
  • The journal lives a year. Journal rows are kept for 365 days, after which a daily sweep removes them. The journal deliberately lives longer than the recordings it describes.
  • The global blocklist. The Blocklist tab keeps addresses and domains that must not be written to: every row carries a reason, a date and an author. Every sender asks this list — letters, mailings, messenger messages, the website chat. A refusal comes back with the same reason you entered, not with a bare error code.
  • The blocklist cannot be dodged by respelling. A domain row closes every address inside it at once. Phones are compared by digits, emails and handles case-insensitively. So adding a plus to a number or rewriting an address in capital letters will not slip past the ban.
  • One workplace. The Privacy section is assembled from the tabs Settings, Blocklist and Access Journal and is available to administrators only. The section only reads: changes are made by commands to the AI agent, which can be copied from the interface.

How it relates to other add-ons

Privacy depends on nothing and installs separately. A workspace that has not installed it behaves exactly as before: everything is read as it is, the blocklist is empty, the journal is empty. Protection appears only when somebody has switched it on.

Every sender asks the blocklist: Email, Marketing, Messaging and the website chat widget — so a ban works at once in every channel, not in one. And access to recordings and sensitive rows adds events to the journal from Telephony and other contours.

Honest limits

  • Masking is about visibility, not about a ban: an employee behind the mask can still write to the customer and call them. If a customer’s work has to be closed completely, that is decided not here but by roles and access.
  • Revealing is manual and piece-by-piece; there is no mass “show all”. Every reveal is written to the journal — looking at the data secretly will not work.
  • The journal speaks in identifiers and words; the values themselves do not enter it. That is by design: the journal must not become the leak it is guarding against.
  • The journal is not eternal: after 365 days its rows are removed by the daily sweep. A longer archive has to be exported separately.
  • Until the flag is set, everyone reads the values as they are — exactly as before the add-on was installed. Protection does not switch itself on and is not set by default.
  • The blocklist is about outgoing messages, not about access: it does not stop an employee who is allowed to see the values from seeing them. These are two different things, and they should not be confused.
  • The section is available to administrators only: an employee cannot change their own data visibility. The setting is placed by an administrator — for a specific person or as the common default for everyone.
  • The section only reads, and that is deliberate: even a value reveal is shown as a command to the AI agent. That way every action on sensitive data always carries a responsible trace.

All add-ons → Add-ons catalogue

← CRM documentation