Answered plainly, before you have to ask them. Where the data sits, who owns it, what touches a model, how errors get caught, and how continuity is assured.
Your kete is yours. The infrastructure runs on it, but the contents, the sources, and every output belong to your organisation.
You do. Every source we agree, every insight we generate, and every output we produce belongs to your organisation. We hold and maintain the infrastructure on your behalf, but the kete is yours.
You own itIn a hosted environment operated by the platform that runs the engine. Access is limited to named members of your team and the ThoughtSeed practitioners on your engagement. Nothing is shared between clients.
Yes. Your data is exportable at any point, in full. Your sources, your approved insights, and your outputs travel with you, not with us.
Only the people you name. There is no shared pool, no cross-client dataset, and no benchmarking against other organisations. Your kete never feeds anyone else's.
The boundary is public. Machine synthesis and tagging sit on one side of it. Source selection, review, and the decision sit firmly on the other.
Two things only. It helps gather and cluster large volumes of source material, and it drafts summaries and themes for a person to review. The model proposes. A person decides.
The choice of sources, the review of every item, the judgement about what an insight means for your organisation, and the decision you make on the back of it. Those are human work, and they stay human.
Human in the loopA model can produce text that looks plausible without being true. That is exactly why a person checks each item against an openable source before it enters your pool. Fabrication is caught at the review step, not after the fact.
No. Your data is never used to train a shared model. What one engagement teaches the engine is generalised learning about method and review, never your content.
Data about Māori carries obligations that predate this platform. We treat it as the responsibility it is, not as a category of input.
With care and in line with the principles set out by Te Mana Raraunga, the Māori Data Sovereignty Network. Māori data is treated as a taonga, and decisions about its collection, storage, and use are made with the iwi, hapū, or organisation it belongs to, not over them.
The community it describes. Where data is gathered about Māori, the source community is named in the review trail and retains authority over how that data is held and used within the kete. We will flag, not quietly absorb, anything that needs a different standard.
It is developed and kept current with cultural advice, and the wording of any protocol that applies to a specific engagement is confirmed with the iwi, hapū or organisation concerned before data is collected.
Held under cultural adviceA specialist practice has to address key-person risk directly. Here is the position, in full.
Your kete, your sources, and your outputs are yours and exportable in full. The engine itself is proprietary, so the codebase is not handed over, but you are never locked out of the intelligence you paid to build.
Every agreement past the Design gate names a second practitioner who can step in. This is arranged before it is needed, not after.
Named in every agreementThe engine is proprietary, and we will not pretend otherwise. The honesty is the point. What you are never locked into is your own data: it is portable, documented, and yours to take at any gate.
A technical annex is handed over at the Design gate. It records the architecture, the component set, the sources, the access plan, and the review standard, so the work is legible to someone other than us.
Design is the gate where the work becomes legible. You leave it holding the same picture we hold.
The intelligence architecture, the agreed component set, the source and access plan, the review standard, and a definition of what good looks like at three months. Enough for your own people or another supplier to understand what is being built and why.
Handed over at the gateYou do. Nothing proceeds past the Design gate without your decision, and the annex is the document that decision is made against.