InSearch
How it works
Enterprise search software AI work assistant Knowledge base search AI enterprise search Internal knowledge search Workplace search Search all company apps AI knowledge assistant Unified search Search Slack & Drive AI assistant for work Knowledge management RAG for enterprise Cited AI answers Confluence search Notion search AI for support agents Sales enablement search Engineering search HR knowledge assistant Permission-aware search Secure AI search Onboarding knowledge SharePoint search See all →
Glean alternative GoSearch alternative Dust alternative Guru alternative Coveo alternative Microsoft Copilot alternative Amazon Kendra alternative Lucidworks alternative Moveworks alternative Sinequa alternative Atlassian Rovo alternative Glean pricing Hebbia alternative Onyx alternative Bloomfire alternative
Security Pricing Blog

Permission-aware · encrypted · never trained on

Security and privacy built into every answer

For an assistant that searches your whole company, security cannot be an afterthought, it has to be the product. InSearch is permission-aware by design, encrypted in transit and at rest, built to SOC 2 practices, and never trained on your data.

Your rules, enforced on every question

Permission-aware Encrypted SOC 2 practices Never trains on your data

The rollout unlock

Permission-aware by design

This is the single thing that lets you roll InSearch out across the whole company. It respects the access rules you already have, on every question, for every person.

  • Item-level permissions are inherited from each connected source, Drive, Slack, Notion, Confluence, Gmail, Jira and Salesforce.
  • Those permissions are enforced at query time, per person, on every single question.
  • InSearch creates no new permissions and exposes nothing new. Your existing rules stay exactly as they are.
  • If a person cannot already open a document in its home app, it never appears in their answer or its citations.
SAME QUESTION Scoped per person

Finance lead asks

Q4 revenue is on track at 92% of target1, with the board deck attached.

[1] Board-Q4.pdf · Drive

New hire asks the same question

No documents you can access mention this. Ask your manager for the finance handbook.

Restricted file never surfaced

One question, two answers, your permissions decide

How your data is protected

Your data answers your team\'s questions, and nothing else

We never train on your data

Your content is used for one purpose, to answer your own team\'s questions, and nothing else. We never use it to train models, and your knowledge is never shared with other customers. Your data stays yours.

Encrypted and access-controlled

Data is encrypted in transit and at rest. Connections to your apps are read-only and scoped, so InSearch reads to find answers and never writes back. Access to your environment is limited to what is needed to run the service.

SOC 2 practices

We follow SOC 2 practices across security, availability and confidentiality. Encryption, access controls and permission enforcement are built into how the product works, not bolted on, so the standards you expect are part of every answer.

Our commitments

What we hold ourselves to

These are the standards we build and operate InSearch to. Security and IT teams can verify each one before they ever roll it out.

Your permissions, never overridden

Item-level access controls from every source are inherited and enforced at query time. We never override, widen or replace the rules you already set.

Read-only by default

Every connection reads to find answers and never writes back to your systems. InSearch cannot change, move or delete anything in your apps.

Grounded, cited answers

Answers are grounded in your own connected content with citations to the exact source docs, so people can verify what they read rather than trust a black box.

Data minimized and scoped

We access only what is needed to answer questions and operate the service, and we keep that access controlled and limited.

Security questions

The questions security teams ask first

InSearch is permission-aware. It inherits the item-level access controls from every connected source and enforces them at query time, for each person, on every question. It creates no new permissions and exposes nothing new. If you cannot already open a document in its home app, it never appears in your answer.
No. Your content is used only to answer your own team's questions and nothing else. We never use your data to train models, and your knowledge is never shared with other customers.
Data is encrypted in transit and at rest. Connections to your apps are read-only and scoped, so InSearch reads to find answers and never writes back to your systems. Access to your environment is controlled and limited to what is needed to operate the service.
Yes. We follow SOC 2 practices across security, availability and confidentiality, with encryption, access controls and permission enforcement built into how the product works rather than bolted on afterward.
See how InSearch works

Roll out company-wide search with confidence.

Permission-aware by design, encrypted in transit and at rest, built to SOC 2 practices, and never trained on your data. Security is part of every answer, not an afterthought.

See pricing

Permission-aware · encrypted in transit and at rest · SOC 2 practices · never trains on your data