trust, answered by architecture

"Does it train
on our data?"

Every cloud vendor answers this question with a policy: we promise not to. We answer it with architecture: the platform runs inside your walls, so there is no vendor-side model to train, no shared tenant to leak into, and no retention policy to read. Nothing leaves the room.

no vendor-side model · no other tenants · no policy required
policy vs. architecture

A promise you read, or a wall you can inspect.

The concern is well founded — RSM, J.P. Morgan and Citi have each warned family offices about what AI tools may quietly learn from the data placed in them, and in July 2026 Squire Patton Boggs named confidentiality the sector’s defining AI constraint. source: SPB White Paper, Jul 17 2026 → Most vendors respond with paperwork. We removed the surface the paperwork exists to cover.

  • iNo third-party transit. On-premise deployment means client documents and conversations never reach a third-party model provider. There is nothing upstream to retain them.
  • iiNo other tenants. There is no cross-tenant commingling because there are no other tenants. Your deployment serves one office: yours.
  • iiiThe contrast, plainly. A "zero-retention API" and a "private instance" are policies — your data still transits someone else’s infrastructure, and the guarantee is a clause you trust. Ours is a wall your own network team can verify.
// the claim, in two sentences
The platform runs inside your walls. There is nothing of ours for your data to train.
— the one answer a policy can never match.
no training on your datano telemetryno shared tenant
the concrete surface

What stays in the room — all of it.

"Nothing leaves" is easy to say and easy to blur. Here is the inventory, item by item, of what lives and remains inside your infrastructure.

01 · in the room
documents
every statement, deed and agreement — stored and read inside your network
02 · in the room
extractions
the structured data the platform reads out of them
03 · in the room
chat history
every question asked and every answer given
04 · in the room
embeddings
the vector index built from your documents
05 · in the room
audit logs
the record of who saw what, and when — yours to hold
your network→your keys→your logs→your record
asked, plainly answered

The questions every office asks.

Does Super Chain train on our data?

No. Super Chain is deployed inside your own infrastructure, so your documents and conversations never reach a vendor-side model. There is no shared model to improve and no cross-tenant pool for your data to join — nothing leaves the room. The guarantee is architectural, not a clause in a policy.

Where do our documents go?

Nowhere. Documents, extractions, chat history, embeddings and audit logs are all stored and processed inside your network — on the office’s own servers or a private tenancy your IT team controls. Super Chain keeps no copy, receives no telemetry, and has no vendor-side store for them to reach.

Can our IT team audit it?

Yes. The platform runs where your team can watch it: your network, your keys, your logs. Every access and action is kept in an audit record that belongs to the office, and the absence of egress can be verified at your own firewall rather than taken on trust.

What makes an AI architecture secure for a family office?

An architecture is secure for a family office when data never leaves the office’s control: the model runs on-premise, there are no other tenants to be commingled with, no vendor-side store to be breached, and the audit trail belongs to the office. Security by design, not by policy or perimeter add-ons.

further reading — the four tiers of "private AI" →✦on-premise AI for wealth management →
// next step

If your office is ready, we will come and meet it.

A first conversation, in person where we can. We listen to how the house works before we ever speak about the platform.

Request a demo
— a private conversation, on your terms —