Security and data
How Qited handles your documents and the questions people ask, in a production deployment and in the live demo.
1Where it runs
A production deployment runs in your own cloud tenant, in the region you choose. Your documents, the index built from them, and your records stay there.
Qited uses the AI model your organization approves, under your organization's own agreement with that provider.
2What's stored
| Data | Why | How long |
|---|---|---|
| Your documents | The source of every answer and every quote | Until you remove them |
| The index: passages with their section and page, and search vectors | Finding the right passages for a question | Rebuilt when a document changes, removed with it |
| Questions and answers | Usage reports and accuracy reviews | As long as you choose |
| Feedback: ratings, reasons and comments | Finding and fixing misses | As long as you choose |
| Admin changes | The audit log | As long as you choose |
3Personal details
- Email addresses and phone numbers are removed in the visitor's browser, before a question or comment is sent. The chat tells the visitor when it removed something.
- The public never signs in, so Qited doesn't need names or accounts for the people asking.
- The chat asks people not to enter personal information.
4Who can see what
The public chat can only ask questions. Documents, feedback, reports and settings live in the admin console, which your staff reach through your single sign-on.
Every admin change is recorded in the audit log: who made it, what changed, and when.
5Answers you can check
Answers come only from your documents. Each quote is checked word for word against its page before the answer is shown, and every answer cites its section and page, so anyone can open the page and check it.
When the documents don't cover a question, Qited says so and gives your team's contact instead of guessing.
6Limits and cost
Per-visitor and daily limits stop runaway use. Past a limit, people get your team's contact instead of a model call.
A call to the model that stalls is cancelled and tried once more. If it still fails, the visitor sees your contact, not an endless wait.
7In transit and at rest
Traffic uses HTTPS. Stored data sits in your tenant's storage, under your encryption, backup and retention settings.
8The live demo
The demo is hosted by us, by invitation, and answers from published engineering standards. It works differently from a production deployment:
- To answer a question, the demo sends it, with the passages found for it, to the AI services that search the documents and write the answer.
- The demo server doesn't save questions. The demo's history of questions, ratings and feedback is kept in the visitor's own browser.
- Documents uploaded in the demo's admin console are stored on the demo server.
- Please don't use the demo for confidential documents or questions.
For how this website itself handles data, see the privacy notice.