Security and privacy

Technical details for security officers and IT. ancoreMind works in the user's own Qlik session with the user's own rights. The ancoreMind service never connects to Qlik, and the AI receives calculated results and app structure – not raw data. For an overview for users, see How ancoreMind works.

On this page you find:

• the architecture and what is sent to the AI service,
• sign-in, storage, encryption and retention,
• how Workspaces are kept apart, and what happens when an account is deleted.

Architecture

Part	Where it runs
Extension	In the user's browser, inside the Qlik Sense session. It is loaded from the ancoreSoft CDN as an immutable, versioned build.
ancoreMind service – sign-in, Workspaces, Library, AI gateway	Microsoft Azure, region Germany West Central
AI	Azure OpenAI, deployment type Data Zone Standard EU, fixed model version

How ancoreMind works with Qlik

ancoreMind runs in the browser, inside the user's Qlik Sense session. It works with the Qlik user who is signed in – it sees what that user sees, and section access and permissions apply. ancoreMind needs no Qlik API key, no OAuth client and no other Qlik credentials, and it stores none.

The ancoreMind service never connects to Qlik. When the AI needs figures, the service sends the request to the user's browser, and the extension runs it in the Qlik session. ancoreMind does not load the data model, does not read raw tables and does not copy QVD files or the app.

What is sent to the AI service

To answer, ancoreMind sends the AI service what it needs for the question at hand:

• the question and the conversation so far,
• the structure of the app that matters for the question – sheet and object definitions, names of fields and master items, expressions,
• the rules of the Workspace and, if Knowledge is used, the matching excerpts from the documents.

The browser never calls the AI service directly; every request goes through the ancoreMind service. Per Microsoft's Azure OpenAI terms, Microsoft does not use customer data to train its models. The model version is fixed – there are no automatic model upgrades. ancoreMind stores the answer and the token usage with the conversation.

Sign-in and credentials

• Users sign in with an ancoreCloud account (Microsoft Entra External ID, with PKCE).
• The extension holds a short-lived bearer token in the session storage of the browser tab only – not in local storage, no cookies. It ends when the tab is closed.
• A session ends after 30 minutes without activity. While the user works in Qlik it is renewed automatically, but never for longer than 7 days after sign-in.

What ancoreMind keeps

ancoreMind does not copy your Qlik app: no data model, no tables, no app copy. What it keeps is the conversation – your questions and its answers, which can contain figures from your app – and files you choose to create or save, for example a report in the Library. Results from Qlik that the AI worked with are deleted after 7 days.

Storage, encryption and retention

Content	Service	Region
Conversations, rules, Knowledge	Azure SQL Database	Germany
Library files	Azure Blob Storage	Germany
Knowledge search index	Azure AI Search	Germany

• Storage is redundant across two Azure regions in Germany (Germany West Central and Germany North). Technical service logs are kept in the EU (Azure West Europe).
• Encryption at rest (Microsoft-managed keys) and in transit – HTTPS only, TLS 1.2 or higher.
• Uploaded documents are checked for malware (Microsoft Defender) before they are processed.
• Retention: results from Qlik are deleted after 7 days, the full responses recorded by the AI service after 30 days – cost and usage figures are kept; the answer in the conversation itself stays –, problem reports after 180 days, backups after 7 days.

Who can see what

• Every request is authorized per user and Workspace: ancoreMind checks the membership of the Workspace and the access to the conversation.
• A Personal Workspace is visible only to its owner.
• In a Shared Workspace, members see the Conversations open to all members, the Library and the Knowledge base. Conversations with selected members are visible only to their participants. See Workspaces and Conversations.
• Reports that ancoreMind generates are at first only in the user's browser, until they are saved to the Library.
• ancoreMind sends a mail only after the user selects Send, and only to ancoreMind users. See Changes and confirmations.

Further protection

• The services reach each other without stored keys (Azure managed identities). The database accepts only Microsoft Entra sign-in. The platform's storage accepts no account keys; services reach it through their Azure identity.
• The production endpoints of the ancoreMind service and its AI gateway accept traffic only through Azure Front Door.
• Access to the AI service works only with Azure identities, not with shared keys.
• ancorecloud.com uses HSTS and a strict content security policy and cannot be embedded in other pages.
• Database access is recorded in audit logs.

When a user reports a problem

Only when a user selects Report under an answer and then Send, ancoreSoft receives that answer, the steps ancoreMind took for it, the version numbers and the user's note, if any. No data from the app is attached. See Report a problem with an answer.

With Help › Report an issue…, ancoreSoft receives the chosen area, the text and pictures, the version numbers and where the user was in ancoreMind – again no data from the app. See Report an issue.

Deactivating and deleting an account

• Deactivate account signs the user out on all devices. The data is kept, and the account can be restored by signing in again.
• Delete account removes the profile, the sign-in methods, the Personal Workspace with its files and its search index. Content shared with others stays and shows Deleted user as author. Audit, security, backup and billing records are retained as required.

Details: Settings and account.