Skip to main content
Læs siden på dansk Consile is built to process as little data as possible. Here is what that means for your rights, in plain words. The technical foundation is described in Security & data.

​
Who is the data controller?

  • For the data that passes through Consile from your systems, and for your access credentials, your company is the data controller, and Consile is the data processor. This is governed by the data processing agreement, which is an appendix to the terms of service and is accepted together with them in the portal.
  • For information about your users and the customer relationship (account, login, payment and support), Consile is an independent data controller. This is described in the privacy policy.
  • The AI service you connect (for example Claude from Anthropic or ChatGPT from OpenAI) is your own choice. It is not Consile’s sub-processor, and what your AI receives is covered by your own agreement with the AI provider.

​
What does Consile store?

  • Account and users: the organization’s name, the users’ emails and roles, who has access to which connectors or the membership’s licence (including the access level), and which tools are switched on for the organization.
  • Which connectors you subscribe to, whether you have the Consile Studio membership or the free edition, whether the connections are connected, and a reference to your customer profile at the payment provider.
  • One encrypted access credential per connected account (token, API key or login).
  • The name of the connected account, where the connector supports it (for example the company name and agreement number in e-conomic).
  • Company locks: for each connection an administrator has locked to one company, the company’s ID at the provider, its name, the chosen values (for example environment and company in Business Central) and the time. The lock is deleted when it is unlocked, when the connection is disconnected or the agreement is removed, and when the subscription ends. See Company lock.
  • The AI clients your users have approved, and each user’s acceptance of the terms (time, version, IP address and browser).
  • Usage statistics: the number of calls per tool per day, without content.
  • The activity log: for every tool call, who made it (a person or an AI bot), the system and agreement, tool, time, outcome and duration. An agreement is one connection to a system. Each call is kept for 90 days. See Activity log.
  • Approvals: which tools require approval, who set the rule, and when. For every call that has waited for approval: who asked for it, the system, tool, status, times, who answered, how many times a window has been used, and the administrator’s optional message. Also a fingerprint that can recognize exactly the same call again, but cannot recreate the content. The information about a call is deleted 90 days after the request or the approval has expired. See Approvals.
  • Studio: your customers (typically the name of a client’s company), which agreements belong to which customer, and your own connectors with name, tools, instructions and shares. For each own connector also whether it is active or deactivated, and for a deactivated one when, by whom and why. See Studio.
  • AI bots: the bot’s name, platform, status and limits, the last four characters of the key, who confirmed that the bot went live or paused it, and the addresses the bot has most recently called from. The key itself is not stored, only a fingerprint. The bot’s call log is kept for 30 days with time, tool, result and the address the call came from, never data from your systems. See AI bots.
  • Messages and requests you send through Consile Concierge.
  • The result of our ongoing checks of whether your connections work.
  • Whether you came to Consile through a partner, and the commission the partner earns on your subscriptions.
  • An audit log of actions on the account, for example when a connector is connected or disconnected, when subscriptions, roles or access change, when a connection is locked to a company, and when approval rules are set, or calls are approved or refused. It contains internal IDs, the action and the time, not names, emails, company names, the administrator’s message, tokens or data from your systems.

​
What do we not store?

The content from your systems, for example accounting data, orders and search figures, is not stored. When your AI asks a question, the tool reads directly from the provider, and the answer is passed on to your AI. The content of the calls and answers is not logged either, not in the activity log, not with approvals and not in the AI bots’ log. If a call fails, we log the error type and any status code, but not the provider’s error text. If a person wants access to or deletion of information that is in your own systems (for example a customer in your accounting system), this therefore happens in those systems. The CVR connector looks things up in the CVR register of the Danish Business Authority (Erhvervsstyrelsen) with Consile’s own access. The search (for example a CVR number, a company name or a person’s name) is therefore sent to the Danish Business Authority.
Consile regularly checks with a light call to the provider that your connections still work. We store only the result of the check, for example whether the connection works, and when it last worked, not the provider’s answer. Consile employees can see your usage statistics for operations and support, and each lookup is recorded in the audit log.

​
Access: export your data

Under Account & data, on the Your data card, you download the file consile-data-export.json with Download data export. All users in the organization can download it. It contains:
  • the account’s creation date and a reference to your customer profile at the payment provider
  • your subscriptions and connection status
  • the AI clients you have approved, and your acceptances of the terms (time, version, IP address and browser)
  • company locks: which company each locked connection is locked to, with the ID at the provider, name, the chosen values and time
  • the activity log for the whole organization, with the newest calls first and at most 100,000 calls
  • approval rules and the calls that have waited for approval, including the administrator’s message. The fingerprint of the call is not included
  • Studio: your customers, which agreements belong to which customer, your own connectors with tools, instructions, shares and whether they are active, and your AI bots with status, limits, the last four characters of the key and the bot’s calls from the last 30 days.
Colleagues appear in the file with an ID, not with their name or email. The file never contains access credentials, AI bots’ keys or data from your systems. If you want full access to your data, for example users, usage statistics or support requests, write to support@consile.dk.

​
Deletion: withdraw access and delete the account

1

Disconnect a connection

An administrator clicks the three dots next to the agreement on the Connections card on the connector’s page, chooses Disconnect and confirms with Disconnect. The encrypted access (token, API key or login) is deleted immediately, and the agreement stops working for all users in the organization within a minute. If the agreement is locked to one company, the lock is deleted too. The subscription continues until an administrator cancels it. If the connector has several agreements, you disconnect each one separately. An administrator removes an extra agreement with Remove the agreement in the same menu, and then its access and any lock are deleted too.The disconnection deletes only the access Consile has stored. The access at the provider (app authorization, API key or login) remains until you remove it yourself. See the last step below.
2

Cancel a subscription

When a subscription ends, Consile automatically deletes the stored access to that connector and any company lock. If you buy the connector again, it must be connected again. If a payment merely fails, the connector is paused, but the stored access is kept, so you do not have to connect again when the payment goes through. See Subscription.
3

Remove a member of the team

An administrator can remove a member under Team. The member’s role and access to connectors are deleted immediately, and the person can no longer log in to the organization. The member’s own connectors in Studio are deactivated, and the member’s AI bots are deactivated and paused. The member’s calls in the activity log remain as Former user until they expire after 90 days.
4

Delete the whole account

Only an administrator can delete the account, and the deletion applies to the whole organization. Click Delete account on Account & data, type SLET in the field, and click Delete account again. The following happens immediately:
  • All access to connectors is removed, and no AI can use them any longer.
  • All encrypted access credentials (tokens, API keys and logins) are deleted permanently.
  • Company locks are deleted, and the agreements no longer belong to customers in Studio.
  • You are logged out, and it is not possible to buy or connect connectors while the deletion is scheduled.
The deletion does not cancel your subscriptions automatically. Cancel them under Subscription before you delete the account, so you are not charged for a renewal during the grace period.For the following 14 days, the other account data is kept (for example users, approved AI clients, acceptance of terms, usage statistics, the activity log, approvals, your customers and own connectors in Studio, and support requests), but no access credentials and no data from your systems. If you want to undo it, contact support before the deadline. Your connectors must then be connected again.After the deadline, the account is deleted permanently: all account data at Consile is deleted, the organization and all its users are deleted at the login service (Stytch), subscriptions that are still running are cancelled, and the customer profile at Stripe is anonymized. See below for what is kept.
5

Remove the access at the provider (recommended)

Consile does not revoke the access at the provider itself: not when a connection is disconnected, not when a subscription ends, and not when the account is deleted. If you want to be completely sure, also remove Consile’s access at the provider. For connectors you have connected with a login or app authorization (for example Google, Meta, LinkedIn, HubSpot, Shopify, Dinero, Business Central and e-conomic), you remove Consile in the provider’s settings. In Billy, you delete the access token, and in Uniconta, you delete the user you created for Consile or change its password. An Ordrestyring key can only be invalidated by Ordrestyring’s support. See the overview per connector in Troubleshooting.

​
What is kept after deletion?

  • Invoices and payment history at Stripe, because the Danish Bookkeeping Act requires it. The customer profile is anonymized (name, email, phone and address are removed), but invoices already issued are not changed.
  • The audit log for up to 400 days from each event. It contains internal IDs, the action and the time.
  • A receipt confirming that the deletion has been completed.
  • If you came through a partner, Consile’s bookkeeping of the partner’s commission (amount and an internal ID) is kept, because the Danish Bookkeeping Act requires it.
  • The contact and the associated information in Consile’s CRM system (HubSpot) are not deleted automatically. Write to support@consile.dk if they should be deleted too.

​
Suppliers and other recipients

​
Sub-processors

Consile uses two sub-processors to deliver the service. They process information on your behalf under the data processing agreement (Appendix B). We give at least 30 days’ notice before we add or change a sub-processor.

​
Recipients for which Consile is an independent data controller

These suppliers are not sub-processors. They receive only information about your users and the customer relationship, for which Consile itself is the data controller, and never data from your systems. The processing is described in the privacy policy. Ad measurement happens only for organizations where a user has accepted marketing cookies on consile.ai and then gone on to the portal through a link from consile.ai. An event is sent the first time the user logs in that way, and when a purchase is completed. Meta is also sent an event when a purchase is started. Without consent, nothing is sent. Consile records only that consent has been given, and which events have been sent, and it does so with internal IDs. If your organization came to Consile through a partner, for example through the partner’s referral link, the partner can see in Consile’s partner overview your name as a customer, which connectors you subscribe to, and how much commission the partner has earned on you. This applies once Consile has approved the attribution. The partner does not see your users or data from your systems.
Consile processes your data and access credentials in the EU (Frankfurt). The sub-processor Stytch processes identity data (for example your email) in the US under EU-approved transfer mechanisms (DPF/SCC).
Questions about data processing? Write to support@consile.dk, or read the data processing agreement, the terms of service and the privacy policy.