Trust center
Private until you share it. Who sees what, where it lives, and who looked.
Each company's data sits in its own databases, on Microsoft Azure in the European Union. Everything you save stays private until you share it, and owners see every time someone opened something not shared with them.
Private until
you share it.
- 1Private until you share it
- 2Each person sees their team's rows
- 3It says plainly that it signs in as one account
Where your data lives.
- nexibi runs as a managed service on Microsoft Azure in the European Union (Frankfurt). Its AI runs in Microsoft's EU Data Zone.
- Backups are kept in Germany.
- Each company's data is kept in its own databases, apart from every other company's.
- Anything that belongs to another company answers "not found", and the attempt is recorded.
- It reads your systems when you ask. There is no data warehouse to build first, and nothing to move before the first question.
- A question reads only the lists it needs, when it is asked, and at most 20,000 rows of each. To a web system it sends a few reads at a time and queues the rest, so a busy system is not sent a burst.
- It keeps your chats (unless you choose not to save one), the files you attach, the dashboards and queries you save, and the copies of lists you choose to keep in the history engine. How long each is kept is on our privacy page.
- The outside services we use are listed on our subprocessors page.
Your systems
A database A web system Microsoft 365 filesWho sees what.
- Everything you save is private until you share it: connections, saved queries, dashboards, reports and workflows.
- Share with a person, a team, a role or everyone in your company, to view, edit or delete. Everyone in the company means view only.
- Only signed-in people of your company can open what you share.
- Share with a team once, and people who join the team later get it too.
- Sharing a dashboard also shares the queries and connections behind it, only what is yours to share, and it names what it cannot share before you save.
- Each person signs in as themselves and sees only what has been shared with them. Where a system allows it, each person connects with their own account, so that system's own rights apply.
- On a shared system, an owner can let each person see only their own rows, their team's, or their branch's. This works on web systems, not on a database connection.
- A result read with one person's own account is shown only to that person, even on a shared report.
- Share a read-only copy of a chat with a colleague: they see only the answers from systems they may open.
- For a group with branches in several countries, nexibi warns before data from one country is shown to people in another. It warns; it does not block.
- Owners run the company's settings and people; members use what is shared with them.
Departments can be sealed.
- An owner can seal a department, with a reason.
- Its dashboards, queries and connections are then not listed, counted or named to anyone outside it: other departments, owners outside it, and our staff.
- Anything made from a sealed thing is sealed too.
- To look inside, an owner asks with a reason and names a second person to approve. Once approved, the owner may read for 24 hours, and every read goes on that department's Activity.
A record of who looked.
- The Activity page shows owners every time someone opened something not shared with them: an owner looking across the company, a refused reach into another company, one of our staff naming your company, or a hand-over. An empty page is the good case.
- Our staff look inside your company only by naming it first, and that naming is written on your Activity page.
- Each connection keeps a record of every action proposed, approved, run, failed or declined, with who proposed it and who approved it. Nothing is removed from it.
- A sign-in log keeps every sign-in and every refusal, with its reason, for 90 days. Owners see the company's; everyone else sees their own.
An empty page
is the good case.
Sign-in that follows your company's rules.
- Everyone signs in as themselves, with a work Microsoft account or a username and password.
- If your company uses Microsoft 365, your owner connects it once, and your people sign in with their work accounts. Their nexibi account is made on their first sign-in. A Microsoft administrator approves the app once.
- Once Microsoft 365 sign-in is on, passwords stop working, so your own multi-factor and leaver rules apply.
- Switch a person off, and they are signed out of every session.
- See the sessions that are open, and sign out everywhere.
- Repeated wrong passwords are slowed down, then blocked for a time.
- Bring your departments in from your Microsoft directory's security groups, nested groups included, whenever you choose.
- When someone leaves, hand their work to a colleague in one step: connections, saved queries, dashboards, reports, workflows, history copies, and their chats with their files.
- 1Which Microsoft do you use?Donetarnwick.com
- 2Ask an administrator to approve nexibiDoneapproved
- 3What we can seeDoneapproval checked, a test mailbox read
- 4Turn on signing in with MicrosoftDoneon
It asks before it acts.
In the chat, the assistant asks before it acts. Anything it would send, share, write to one of your systems, or delete waits for a person's approval.
Writing to a system is off for every connection until a company owner, someone who runs your company's settings and people in nexibi, switches it on and approves each kind of change.
Each person chooses how much it asks: before every change, or only before it sends, shares, writes to one of your systems or deletes. A third way of working does not ask. It exists only where we have switched it on for your company and your owner allows it.
Changes it makes for you can be undone for 24 hours. That covers what it changed without asking, not a change you approved on a card.
A workflow does what its steps say. It waits for a person's yes where it has an "Ask someone first" step. Try a workflow first: nothing is sent and nothing is changed.
Anything an AI agent would change in your systems or send to someone waits for a person's yes. It can never approve its own work.
Your data stays yours.
- You own your data, and the answers nexibi gives you.
- We do not use your data, your prompts or the answers to train AI models, and under Microsoft's terms Microsoft does not either. We do not sell personal data.
- Export everything your company put in, whenever you like, as one file. Passwords and keys are left out.
- If you leave, your company turns read-only and your owners have 30 days to take everything out. Then it is deleted, on the timeline in our Terms. Owners are told by e-mail at each step.
- Your owner decides how long chats are kept. How long everything else is kept is on our privacy page.
The owner's switches.
- An owner can switch the assistant, or downloads, off for the whole company.
- Whole apps can be switched off too: Insights, Data, Flows or Agents. Their pages say so, and nothing is deleted.
- With downloads off, every way out closes for everyone, owners included: dashboard pictures, PDF and Excel, list downloads, chat exports and the company export.
What it does not do yet.
So you know before the demo.
- No sign-in with Google, Okta or other providersA Microsoft work account, or a username and password.
- No password reset by e-mailYour owner sets a new password.
- No two-step sign-in for password accountsWith Microsoft sign-in, your company's own rules apply.
- Inside another company's product, people sign in to the assistant once more, in a small window
- The Activity page is not a log of every changeChanges to settings and people are not listed there.
- An owner cannot delete the company's data on the spotDeletion follows the end of the subscription, on the timeline in our privacy page.
- No security certification yetHow your data is protected is on our Privacy page.
- No uptime promise yet
The documents.
- Our Terms, Privacy and Subprocessors pages are public and in force, last updated 22 October 2026.
- A data processing agreement is available on request from hello@nexibi.ai.
- We tell every company's owners by e-mail at least 30 days before a new subprocessor starts to process their data.
See who sees what, on your own system.
In the demo we connect one of your systems, and you ask the questions.