Trust
Data sovereignty
Your data should belong to your community — not to us. That is the principle we are building towards. It is not yet how the Hub works, and this page says where the gaps are.
Last updated November 2026
Communities generate the data that would make these agents useful, and that data should belong to them. Below are the six principles of our design and, for each, what is true today. The design also covers regional storage, encryption and audit procedures. None of it is deployed.
Six principles, and where we are
- Data belongs to communities. The design makes us a custodian, not an owner. Today we run no database of our own: what you type in the Hub is recorded by our AI platform provider.
- Data stays where it is generated. Planned: storage in the region of origin. Today nothing keeps your messages in the country where you are.
- Minimum collection. There are no accounts and we do not ask for your name. But nothing is filtered out of what you type, so leave out anything you would not want recorded.
- Transparent purpose. Today there is one purpose: answering your question. Planned: purposes agreed with each community, and none changed without renewed consent. We have no community partner yet.
- Right to deletion. Planned with the community-owned backend. It is not available yet.
- Community benefit. A principle of the design: value derived from community data should flow back to those communities. We hold no community data yet, and nothing has been agreed or built to make that happen.
Where your data goes today
Today your messages are processed and recorded by our AI platform provider on its own systems, and places you ask about are sent to public map services. Nothing keeps any of it in the country where you are. The design for the planned backend is different: storage on in-region infrastructure, only anonymised aggregates leaving the region, and cross-border transfer only with explicit community consent and regulatory approval. It is not deployed.
Keeping the exit open
We do not want to lock anyone in. All our code is MIT-licensed, so a community is free to fork it. The agents run on a hosted AI platform, so your own copy needs your own account with that provider. Exporting your data in open formats is planned with the community-owned backend; it is not available yet. We want leaving to be a first-class feature, not a support ticket.
Rights, in your language
The design gives communities the right to know, access, correct, delete, export, refuse, benefit from, and have a say in how their data is governed. Planned: purposes agreed with each community, and rights explained in local languages rather than buried in fine print. We have no community partner yet, and this website is in English.
See also our Privacy notice and Safety framework.