Skip to content

It only does what you have ticked.

Everything is born switched off. A write waits for a human's approval, each workspace is isolated, and you take over in one click.

On day one

The starting values

  • Writing into your softwareOff
  • Discovered fields and operationsOff until you tick them
  • Sending an answer unreadIt proposes, you send
  • Entering without an invitationNobody
  • Reading another workspaceNot found

Every call passes three locks

Before acting in your software, the collaborator goes through the same checks as a human, in this order, redone at the moment of the call.

  • In the log: request, response, duration, status. Sensitive fields never enter it.

  • A deduplication key goes with every execution: a replayed call does not run twice.

Demonstration

An operation to try

Write, ticked

  1. Operation ticked, object switched onTicked
  2. Source in serviceIn service
  3. A human's approval, if the operation requires itA write: a human grants it, never itself.

Submitted to a human

Every workspace is isolated

An account can group several workspaces, one per agency. None reads the others: what is not yours answers “not found”, never “forbidden”.

Demonstration

Your account

One subscription, one invoice
You are in
  • North agency

    • Conversations
    • Contacts
    • Channels
  • South agency

    Not found

  • West agency

    Not found

  • Within a workspace, teams limit what each person sees: a team's channel opens only to that team, the administrators and the owner.

  • A contact does not rise to the account: two agencies can know the same person without reading each other's history.

Roles, not privileges

The role says what a person may do; the team, on what. The screen hides what a role cannot do, and the server refuses it.

The accountant
At account level: pays, and reads no conversation.
API keys
Each carries a role, never above its creator's. Shown once, refused from the first call after it is revoked.
The Nodium team
Enters a workspace only for operations and support, strictly as far as needed. Its reads go into the access log.
Demonstration
  • Today
  • Conversations
  • The collaborator
  • The account
  • Team, usage, subscription, AI keyNot in their menu
  • Hand the workspace overNot in their menu

Answers customers and tries the collaborator out; does not configure it.

Your secrets stay secret

What you deposit is encrypted, and comes out of no read.

Demonstration

Access token for your software

Deposited
  • Encrypted, never read back

    A connection's secret is encrypted in the database. A read only says whether there is one.

  • Every key in its place

    A key slipped into a field not meant for it is refused, with where to put it instead.

  • No detour through a private network

    An address leading there is refused, redirects included, and your token does not follow a change of origin.

  • Signed webhooks

    HMAC SHA-256: your software checks that the call comes from us.

Everything leaves a trace

What the collaborator read and did, what each person looked at: written, dated, without the sensitive fields.

  1. The report

    At the end of every turn, a note in the thread says what it read, did, and tried to do without succeeding.

  2. The call log

    Every call to your software, with its request, response, duration and status. Sensitive fields are masked.

  3. The access log

    Reading a conversation, its messages or a contact, changing a member, erasing a contact: every move goes in.

The call log
Demonstration
# “iban” is marked sensitive: its value never enters the log.10:02:11 voir_un_dossier 200 184 ms{ "reference": "2481" }{ "status": "confirmed", "balance_due": 180, "iban": "••••" }

Your data

It stays yours, and it stays in Europe.

Read the privacy policy
Hosted in Europe
The database in Ireland, the application in Paris.
No training
No conversation is used to train an artificial intelligence model.
Erasing a contact
An administrator retypes their name: the contact and their exchanges go in one step, and a trace of the erasure remains.
Yours
Your data, your catalogue and your conversations remain your property.

Take over, at every level

A human steps in front of the collaborator without looking for how.

Demonstration

In service: it answers according to its stage.

  1. A thread

    Take over, then hand it back. Closing the thread switches it off there.

  2. A channel

    A stage of its own: alone on WhatsApp, it can propose on email.

  3. The collaborator

    Move down a stage, at any moment and with no condition.

  4. Everything

    Stop everything, in one click. One click puts it back in service.

We claim no certification. This page describes what the software does today, and nothing else.

A security question? Write to us

Connect it: nothing switches on without you.

Start with the free plan. Reading is ticked field by field, writing stays off.