Built to be questioned.

The more Decern reads, the better it knows your deals. So every source has a switch, every read leaves a line in your log, and everything it holds can be erased.

What it reads. You set the rules.

Switch a source on and Decern reads it. Switch it off and that door closes. Your rules apply before anything is read, and every read leaves a line you can check.

Six sources, each with its own switch: meetings, mail, documents, Slack, CRM and calendar. What passes through an open door is read and written to the read log. A switched-off source closes its door, and anything your rules keep out stops at the door and is logged as not read. One button pauses all reading.

Read logNordhavn Energi
Every read is logged.

Never reads what you keep out

Words, addresses and channels you name. From a calendar it takes time, title and attendee domains.

Try a rule before it applies

Decern shows what the rule would have kept out of your last 30 days of mail and meetings.

Names stay out of the model

Masked on the way to the model, and put back when the answer returns.

A person approves, if you want

Someone on your team approves each new finding before it is saved.

Your model. Or no model at all.

A model reads what comes in and words what goes out. The record in between, and every rule on it, is Decern’s own. Swap the model and the record stays exactly as it is.

What comes in passes a model, reaches your record, and a model words what you read. Three choices: your own key, a provider hosted in the EU, or no model, where Decern’s own rules read and each finding is quoted as said. The record is the same in all three. Names are masked before a model reads them.

What comes in

Alignment call
Proposal v2
RFI, section 2.1
Your provider
Reads on your account

Person 1: “Anything over two million goes to the board.”

Your record
  • Phase 1 covers Nord and HamnConfirmed, RFI
  • Over two million goes to the boardSaid once, Per Lind
  • Go-live: before summer → after budget reviewContested, two sources
  • Karin Ek’s positionUnknown
The same, whichever you choose
Your provider
Words on your account

Person 1 set the limit. Keep phase 1 under it.

What you read

Keep phase 1 under 2 MSEK and the board drops out.

Per Lind, controller
Your material goes toThe provider on your key
What you give upNothing

Decern does not train on your data

And no provider does either, on any route Decern offers.

Your deals feed no one else’s

Nothing you bring in reaches another customer, as a line, a pattern or a benchmark.

The same answer twice

The wording can vary between models. The facts and their sources come from the record, so they hold.

An honest record. What was said stays as said.

Every line keeps who said it, where and when. A correction lands beside the original, so your team and your agents can trust what they read. The database itself refuses a rewrite, whoever asks.

A stack of statements where new ones can only land on top. A database session tries to rewrite one underneath and is refused: statements is append-only and the row cannot be rewritten. Adding the correction as a new statement beside it succeeds.

“Our dispatchers spend 2 hours on this, not 3.5.”

Per Lind, Controller. Kept as said, beside the 3.5 hours in your own figures.

Take it back. Everything it holds can be erased.

Bringing a source in is a decision you can undo. That is what makes it easy to bring in the next one. Each erasure ends with a receipt, checked against the database afterwards.

One deal as a field of small cells, sealed with your workspace’s key. Holding the button erases it, and a receipt is left: 38 sources, 214 statements and 11 files erased, checked against the database with nothing left.

Nordhavn EnergiSealed with your workspace’s key

Erasure receipt

Erased
38 sources, 214 statements, 11 files
Checked
Against the database, nothing left
Kept
This receipt, and that you asked for it

Erase a deal

Every source, every finding and every word read from them, from your Data page.

Erase a person

Someone on the buyer’s side asks to be forgotten. Their name and words leave the record.

Choose how long it stays

Nothing goes on a timer unless you set one. Raw text can go after 30, 90 or 365 days, and the sentences it proved stay.

Destroy the key

Each workspace has its own key. Destroy it, and your original files can no longer be read by anyone.

Who gets in. Your team, and who you let in.

Every workspace is sealed from every other. People and agents both sign in. Decern’s support opens a deal only after someone on your side lets them, and you can read what they looked at.

A dial with twelve marks, one for each hour support may stay. Closed by default. Someone on your team can let support in, read-only, for up to twelve hours. Each request is listed as it happens, and a change is refused. Access ends on its own, or when you end it.

Decern support has no access

Someone on your team can let support in, read-only, for up to 12 hours.

  • Ended by youClosed
  • Support tried to change a lineRefused
  • Support read Nordhavn EnergiRead

One workspace, sealed

A deal is visible only inside its own workspace. The boundary is tested on every change to the code.

Agents sign in too

An agent connects with your sign-in, or an API key you name, can set to expire, and can revoke at any time.

Ask us anything

Send your security team’s questionnaire. We answer it ourselves, at info@getdecern.co.

Bring one deal. See what you missed.

We’re opening Decern to a few design partners. Tell us about the deals you sell.

We read every request and reply by email. Nothing else is sent to you.