IhsanRequest access

What your company knows stays yours

Ihsan is only useful if you can trust it with what your company has written down. This is how it is looked after.

Every company kept apart

Each workspace’s knowledge is stored separately. Ihsan answering for one company can never read another company’s documents, conversations or history.

Credentials locked before they are stored

When you connect a tool, the access credentials are encrypted before they reach the database. They are never kept in readable form.

Every Slack request verified

Slack signs each message it sends to Ihsan. Ihsan checks that signature before reading anything, so a forged request is turned away at the door.

The software gets only the access it needs

The running application uses a restricted database account. Changes to the database structure need a separate, more privileged account that the application does not hold.

Your content is not training data

Ihsan does not train AI models on your company’s content. It reads your knowledge to answer your people, and for nothing else.

You decide what it reads

Ihsan reads only the sources your admins connect. Remove a source and Ihsan stops using it. Ask us to delete your data and we delete it.

The providers behind Ihsan

Ihsan runs on established, enterprise-grade cloud, database and AI providers. Each one is bound by a written agreement to protect your data, to use it only to deliver its service, and not to train its own models on it.

Customer data is stored in the United States. A current list of providers is available to customers on request.

Questions about security? Write to security@ihsanone.com. The full detail is in the privacy policy.