AI & data privacy
We're a data provider, not an AI.
Cloud Konnekt never sends your data to an AI service on its own. Your AI assistant asks; we return only what its connection allows. What happens to the answer after that is governed by your AI provider's terms and your settings — so here's how to get those right.
How a request travels.
Your assistant only reaches Cloud Konnekt because you connected it. Cloud Konnekt doesn't call AI models and doesn't push data anywhere — it answers requests.
Request
- Your AI assistant
- Cloud Konnekt
- Finance system API
Cloud Konnekt checks who is asking and whether their connection allows that action, then calls your finance system.
Response
- Finance system API
- Cloud Konnekt
- Your AI assistant
The result goes back to the assistant that asked. From there it is processed under your AI provider’s terms. Cloud Konnekt doesn’t store the result. Only the request is logged, for 90 days, for support.
Who's responsible for what.
Cloud Konnekt
- Answers requests from AI assistants you connect — never sends data to AI on its own
- Applies its own restrictions on top of your finance system’s permissions: each connection can call only the actions you allow
- Lets an admin revoke access instantly and block further calls
- Stores no ledger data — only a log of requests, kept 90 days for support
- Runs the gateway on AWS in London, with all traffic encrypted in transit
Your AI service
- Processes what it receives to answer your question
- Decides retention and whether content is used for training, under your plan and settings
- Keeps your chat history, including results already returned
Your organisation
- Chooses and approves the AI services people may connect
- Sets plans and privacy settings with each provider
- Decides who gets a connection and what it allows
- Sets user permissions in its finance system
Using, training and storing are different things.
"Is my data used for AI?" mixes three separate questions. Ask your provider about each one.
Using it to answer
Inference: the AI reads the result to answer your question. This always happens — it’s the point of connecting.
Training models
Whether content may be used to improve future models. This depends on the provider, your plan and your settings.
Storing it
Retention: how long the provider keeps chats and results. A separate setting from training — and disconnecting doesn’t delete it.
Provider guidance · checked 13 October 2026
Your plan matters more than your bot.
We recommend an organisation-managed business plan with model training switched off. Provider terms change — always confirm against the provider's current documentation. For Grok and other assistants, check directly with the provider; we don't assume their terms match these.
OpenAI
ChatGPT personal plans
Content may be used to train models when “Improve the model for everyone” is on. Check this setting before connecting.
How OpenAI uses data ↗OpenAI
ChatGPT Business, Enterprise and Edu
Not used for training by default. Workspace admins control which connected apps are allowed.
Connected apps in ChatGPT ↗Anthropic
Claude Free, Pro and Max
Raw content from connectors and MCP tools is excluded from training, but content copied into the conversation may be included if training is on.
Claude consumer training ↗Anthropic
Claude Team, Enterprise and API
Not used for training by default. Retention is set out separately.
Claude commercial training ↗Anthropic
Data retention
How long Claude keeps conversations depends on plan and settings.
Claude data retention ↗Others
Grok and other assistants
Any MCP-capable assistant can connect. Check its training, retention and connector terms with the provider before connecting.
Ask us if unsure ↗Before you connect.
Connecting an AI service allows it to request and receive business information within your configured access permissions. Confirm that your organisation has approved the service and its data-handling arrangements before connecting.
- Use an organisation-managed business or enterprise plan where you can.
- Check the provider's training, retention and connector settings.
- Give each connection only the actions its users need.
Questions customers ask.
- Does my data leave our finance system?
- Only the results your assistant asks for, within its connection’s permissions. They go to the AI service you connected, so it can answer.
- Is my data used to train AI?
- Cloud Konnekt doesn’t train or use AI models. Whether your AI provider can train on content depends on its terms, your plan and your settings.
- Is a paid personal account enough?
- Not necessarily. Some paid personal plans may still allow training unless you switch it off. We recommend an organisation-managed business plan.
- Who controls access?
- You do. Your finance system’s permissions apply, and Cloud Konnekt restricts each connection to the actions you allow. Each person signs in with their own login and MFA.
- Does disconnecting delete previous chats?
- No. Revoking access stops future requests immediately, but results already in your chat history stay with your AI provider under its retention rules.
- Can Cloud Konnekt check my AI privacy settings?
- No. We can’t see or verify your settings with an AI provider — that sits with your organisation.
- What does Cloud Konnekt store?
- Each user’s account details, and a log of the requests made — what was asked, not the data returned — kept for 90 days for support. We don’t store ledger data.
- Where is Cloud Konnekt hosted?
- Our gateway runs on Amazon Web Services in London, UK. Traffic between your assistant, Cloud Konnekt and your finance system is encrypted with SSL/TLS.
For your security review.
Ask for our security details →| Ledger data | Not stored — results pass straight back to the assistant |
|---|---|
| Logs | Requests only (not returned data), kept for 90 days for support, then deleted |
| User authentication | Individual Cloud Konnekt accounts with MFA |
| Access control | Finance-system permissions, plus Cloud Konnekt restrictions on the actions each connection can call |
| Revoking access | Admins can revoke instantly; further calls are blocked |
| Field-level filtering | [Planned] |
| Hosting location | Amazon Web Services (AWS), London region, UK |
| Encryption in transit | All traffic encrypted with SSL/TLS |
| Sub-processors | Amazon Web Services (hosting) only |
| ICO registration | Konnekt365 Limited, 00015759417 |
| Privacy Notice | Published — see Privacy Notice in the footer |
| Data processing agreement | Available on request from support@cloudkonnekt.com |