Security overview
A short guide to what Gurusup processes, where it runs, and who can reach your data.
Start here if you are reviewing Gurusup for your organization. This section lists what we can back with our code and internal records. Where we have not confirmed something, the page says so or leaves it out. We would rather give you fewer claims you can rely on.
At a glance
| Topic | What we can state | Details |
|---|---|---|
| Hosting and region | Gurusup is hosted on Google Cloud in Europe. | Where your data lives |
| AI providers | Learning uses Anthropic (Claude) or OpenAI, chosen by configuration. The numeric representations used for search come from OpenAI, per our deployment template. | AI providers |
| Access model | The role decides screens and actions. Categories, granted by an admin, decide which knowledge a member reads. A restricted source is read only by the people picked for it, admins included only if picked. | Permissions model |
| Assistants | An assistant connected through MCP sees what the signed-in account sees. | Access to your data |
| Retention | No legal retention periods are stated, because we have not confirmed any. | Retention and deletion |
| Disconnect | Stops new content and deletes the credential Gurusup stored. It does not remove what Gurusup already learned. | Retention and deletion |
Find an answer
| Question | Page |
|---|---|
| What does Gurusup keep, and what does an assistant receive? | Data we process |
| Where does Gurusup run? | Where your data lives |
| Who can see my organization's data? | Access to your data |
| What do roles, categories and restricted sources protect, and what do they not? | Permissions model |
| Which AI providers process my content? | AI providers |
| What permissions do connectors ask for? | Connectors and scopes |
| What can be removed, and what cannot? | Retention and deletion |
Was this page helpful?