Security in coreAI rests on three pillars: where requests are processed, how users log in, and how your data is stored and scoped. On all three points the starting position is the same – you keep control, and coreAI layers on top of the security you already have instead of introducing a new one. The result is an AI solution that meets Norwegian privacy requirements without you having to compromise on what the assistant can actually do.
#Requests can run on European infrastructure
The AI request itself – the question and the content it should answer from – can be processed by providers within the EU/EEA instead of on servers in the US. Through an agreement with OpenRouter, the call is routed to the European endpoint, and the request is forwarded only to providers that offer the model on European hardware.
You choose this per knowledge base, where the option is available. That means you can run a knowledge base with sensitive content on European infrastructure and another on global – depending on how sensitive the content is. The choice is a simple setting, not a development project.
For the European providers, requests run under Zero Data Retention (ZDR): your content is not stored after the answer is delivered, and it is never used to train the models. A request is processed in memory to generate the answer and then discarded. There is no log of the content itself at the model provider, and nothing you send in ends up in a training dataset. See language models on European infrastructure for the full picture of how this is set up and what is guaranteed.
#Login is validated against your own system
If an assistant should only be available to logged-in users, coreAI validates them against your own login system – not against a parallel user registry you have to maintain. If you set a callbackUrl on the assistant, coreAI calls your endpoint with the user's token before the chat widget is initialised, and only users your endpoint approves with HTTP 200 get through.
The login, the session, and the user database stay with you. coreAI never owns the logic for who is who – it only reads the result of your own validation. The details, including how to scope each user to their own data sources, are in protect an assistant with your own login.
#The assistant only fetches within the user's permissions
The AI can't "stumble" over information a user shouldn't see. The access boundary is set not by the AI but by you – and enforced at the data level. Once the user is validated, your system decides which sources and documents that role should have access to, and coreAI limits all retrieval to exactly that set. The rest of the knowledge base is simply not visible to the search.
In other words, the knowledge base cannot leak internal documents to a customer, or one department's routines to another – because they are never part of the search basis for that user. The same role-based access (RBAC) that governs the rest of your systems also governs what the assistant can fetch and do. See even better answers behind login for how role-based, access-controlled knowledge bases are set up.
#Your data is stored securely and stays yours
Your knowledge base and search index sit on Norwegian infrastructure, and you are the data controller for the content all the way through. coreAI processes the data on your behalf to deliver the answers – it is you who owns it, decides what is imported, and can remove it again.
The combination is what makes the setup GDPR-friendly: data processing within the EU/EEA where you choose European infrastructure, no storage or training at the model provider, and a knowledge base you control yourself. If you also set the assistant to answer exclusively from your own sources, you avoid it falling back on general knowledge when the answer should be grounded in internal facts.
#Security without compromising functionality
What makes coreAI secure isn't that it does less – it's that it reuses the security you already have. You get European data processing where you need it, login against your own system, access control at the data level, and full control of where your data lives. At the same time, the assistant keeps the ability to answer personally and act on behalf of logged-in users, because access is always scoped to what each individual is actually allowed to do.
Want to walk through how the security fits your exact setup – login, data storage, and choice of infrastructure? Get in touch for a walkthrough.