Trust
Privacy notice
What happens to what you share with us today, and what we are still building. Written to be read — not buried in terms of service.
Last updated November 2026
Thrivant AI is being built for communities that have too often had their data taken without consent or benefit. We want to be a custodian of your data, never its owner. Most of that design is not built yet. This notice says plainly what happens today and what is only planned. The design we are working towards is written up on our Data sovereignty page.
What we collect
There are no accounts, and we do not ask for your name. This is what leaves your device today:
- What you type in the Hub. It is sent, as typed, to our AI platform provider (Anthropic) to route and answer your question, and the provider keeps a record of the conversation. Nothing is filtered out first, so leave out names, phone numbers and anything you would not want recorded.
- Places you ask about. Place names and coordinates you give are sent to public map and data services — OpenStreetMap’s search service (Nominatim), public Overpass servers that serve OpenStreetMap data, and the Water Point Data Exchange — to find health facilities and water points.
- What keeps the Hub running. One session cookie that lasts two hours; a count of requests kept against a shortened hash of your network address, to limit abuse; and a bot check on chat messages, run by our hosting provider.
- Forms on this website. If you sign up for the newsletter or send a partner enquiry, what you enter is passed to the service we use to receive it. If no such service is connected, the form tells you so and nothing is kept. To limit abuse, form attempts are counted against your network address for a few minutes, in memory only.
Settings such as theme, language and accessibility preferences are saved in your browser only.
How we protect it
- In transit. Messages travel over HTTPS to our host and to our AI platform provider.
- At rest. Thrivant AI runs no database of its own yet. The record of each conversation is held by our AI platform provider. Encryption with keys we manage is part of the planned backend, which is not deployed.
- Logs. Our own server logs record errors, not what you type. We run no analytics.
- Planned, not built. Pseudonymised identifiers and per-region keys are designed for the planned backend.
Consent is not built yet
There is no consent step yet: what you type is sent when you press send. That includes sensitive things. A disclosure about violence typed into the chat is recorded like any other message. Recorded consent in your language, and deletion when consent is withdrawn, are designed for the planned backend. They are not deployed.
Where your data lives
Today your messages are processed and recorded by our AI platform provider on its own systems. Nothing keeps them in the country where you are. In-region storage is the design for the planned backend. It is not deployed. We have not yet had the design reviewed against data-protection laws such as Kenya’s Data Protection Act, Nigeria’s NDPA, South Africa’s POPIA, the EU GDPR or the African Union’s Malabo Convention. That review comes before any deployment.
Your rights
What you can do today: choose what to share, and use the Hub without an account or a name. These are planned with the community-owned backend. They are not available yet:
- Access to everything held about you or your community.
- Correction of anything inaccurate.
- Export in open formats, to take elsewhere.
- Deletion on request.
Because there are no accounts, we have no way today to tell which conversations are yours, so we cannot yet show, correct or delete them for you.
What we never do
We never sell your data. We have no partners to share it with. To answer you, your message goes to our AI platform provider, and places you ask about go to public map services, as set out above. And we never make an automated life-or-death decision — our AI recommends, and a person decides. See our Safety framework for how that works today.
If something goes wrong
We do not have an incident-response process yet. We will write one before any deployment with a partner.
Questions about your data
There is no monitored contact address yet, so today there is nobody you can write to about your data. An address will be listed here once someone is reading it. You can also read the design on our Data sovereignty page.