DAYLIGHTING

Security, safety & privacy

Your client's drawings never leave your hands.

Daylighting is built so that you never hand a model to anyone — not to us, and not to the network in between. This is what that means for you.

  • No NDA · statelessnothing of your client's for us to hold
  • Unreadable in transitthree pieces, none meaningful alone
  • A record for your protectionevery report sealed, never rewritten

ANo NDA

No NDA needed: what stays with you, and a stateless engine

Your computer

  • The model file
  • Your photographs
  • The job and the client record
  • The finished report

stays here

only the measurements taken from your model
the answer, back the same way

Our engine

  • Computes the BRE 209 tests
  • Sends the answer back
  • Holds nothing between runs — a stateless machine, by design

stateless · keeps nothing

The report itself is put together on your computer, from the answer. Our engine is stateless: it keeps nothing, not because we delete it, but because it is built to hold nothing. There is nothing of your client's on our side — so there is nothing to sign an NDA about.

Stateless by design: we cannot keep what we are built not to hold

Our engine is a stateless machine. Every run starts empty and ends empty, so nothing of yours survives from one run to the next.

  1. Before the runEmpty
  2. 1Measurements arrive
  3. 2The tests are computed
  4. 3The answer leaves
  5. After the runEmpty again

What our engine does not have

  • A database of your jobs
  • A copy of your model
  • An archive of your reports
  • A record of your clients

Why this is proof, not a promise

Most services promise to delete your data. We don't have to: a machine that starts every run empty and ends it empty cannot hand over, leak or lose what it never holds. That is what lets us say it by design — and why there is nothing to put under an NDA.

BIn transit

Nothing lost or read on the way

  1. Split into three. Everything that crosses is cut into three encrypted pieces, each travelling its own way.
  2. Noise on its own. One piece, or any two together, means nothing — there is nothing in it to read or to lose.
  3. Whole only at the other end. The three make sense only when they meet where they are meant to.
  4. On top of the standard. All of this sits above ordinary HTTPS, so a break in one layer is not a break in the other.

CThe ledger

A record for your protection

Every report, revision, verification and delivery is an entry on your ledger, and each entry is sealed to the one before it.

  1. Entry 1Rev 0 issued14 Ashgrove Road
  2. Entry 2Reading verifiedby you
  3. Entry 3Sent to the councilto whom, and when
  4. Entry 4Refusedon the ground they gave
  5. Entry 5Rev 1 issuednames what it replaces
  • Nothing is ever rewritten. A correction is a new entry that names what it replaces; the old one stays exactly as it was.
  • Check it at any time. The chain reads either intact or tampered — there is no in between.
  • Proof when you need it. If a report is challenged, you can show exactly what you sent, when, and from which inputs.

DFor you

What this means for your practice

  • No NDA with us. Your client's drawings are never in our hands.
  • Your files, your machine. The model, the photographs, the record and the report are where you keep them.
  • Nothing to intercept. What travels is measurements, in pieces that mean nothing alone.
  • Nothing to hand over. A stateless engine holds nothing that could be demanded, leaked or lost.
  • A record that stands up. What you issued, verified and sent is on a chain that cannot be rewritten.

Questions from your client or your insurer?

We'll walk them through it. enterprise@kairoico.com · Privacy notice