Connect an AI to chat with your shop data directly here.
Choose how you want to connect your AI.
A new tab will open for OpenRouter authorisation.
Return here once you've approved.
After approving, .
Requesty runs its gateway in the EU (Frankfurt), is GDPR compliant and offers a data processing agreement. Choose an EU-hosted model to keep your data in the EU.
Requesty: glm-5.3-flash@eu · OpenAI: gpt-4o · OpenRouter: openai/gpt-4o
Your MCP server URL:
Configure this URL in your MCP client. See the Help page for detailed setup instructions.
To continue using Shop Conductor, read and accept the Terms of Service. Your connected shops and AI clients keep working in the meantime.
1.1 These supplementary terms apply to the Shop Conductor service (the "Service") provided by Vilkas Group Oy (Business ID 1033996-4), Näsilinnankatu 27 B 9, 33200 Tampere, Finland ("Vilkas"), through which the Merchant can use an AI assistant to read and change the data of its online shop. The assistant's answers are produced by a language model, not by a person.
1.2 The Service is an additional service within the meaning of clause 1.1 of the Vilkas Service Agreement. The Service Agreement applies to the Service except where these terms provide otherwise. In case of conflict, these terms apply first, then the Data Processing Addendum (Annex 1), then the Service Agreement.
1.3 The Merchant accepts these terms when connecting a shop or a Client Application to the Service, or when the Service asks it to accept them. The person accepting confirms that they are authorised to bind the Merchant. The terms bind the Merchant also when the Service is used by one of the Merchant's Back Office Users under clause 4.
2.1 "Merchant" is the company or person that has an online shop agreement with Vilkas and takes the Service into use.
2.2 "Back Office User" is a person to whom the Merchant has given credentials to the administration of its shop.
2.3 "Shop Data" is the product, order, customer, subscriber and settings data of the Merchant's shop and any other content read from or written to the shop's API.
2.4 "Vilkas AI Model" (usage model A) is the language model selected and paid for by Vilkas and used by the Service's chat page and the assistant panel in the shop back office unless the Merchant has chosen its own AI provider.
2.5 "Own AI Provider" (usage model B) is a language model provider or AI client application that the Merchant selects and contracts with itself and connects to the Service by an MCP connection or, where Vilkas has enabled the function, by its own API key or its own OpenRouter account.
2.6 "Client Application" is an application the Merchant connects to the Service over MCP, for example Claude, ChatGPT, Gemini or opencode.
2.7 "Pseudonymous Mode" is a mode of the Service in which customer and subscriber identities are replaced with codes and address and free-text fields are removed before data is passed to the language model.
3.1 The Service relays the language model's requests to the Merchant's shop API within the permissions the Merchant has granted. The current content of the Service, the available functions ("tools") and usage limits are described on the Service's help page.
3.2 The Service is in development (beta). Vilkas may change, limit or discontinue functions without separate notice, and no specific availability is promised. Clause 10 of the Service Agreement applies only to the extent the Service is priced.
3.3 Use of the Vilkas AI Model is free of charge within the allowance in clause 7. Additional usage beyond the allowance can be bought as token bundles, to which the Shop Conductor purchase terms apply. Vilkas announces any other pricing under clause 5 of the Service Agreement, and once priced, use requires an order from the Merchant.
4.1 The Merchant is responsible for its Shop Conductor account and everything done with it, as set out in clauses 6.5 and 6.8 of the Service Agreement.
4.2 The assistant panel in the shop back office is available to every Back Office User of the Merchant, and every Back Office User acts in the panel with the permissions and access level of the Merchant's account. The shop's own user permissions are not applied in the panel. The Merchant's main administrator can switch the panel off for an individual Back Office User in the shop's user management, and the Merchant is responsible for doing so where use is not intended.
4.3 When connecting a shop or a Client Application, the Merchant chooses what the assistant may do from four options: full access (preselected: reads everything and makes changes, customers by name), product editing, reading with customers by name, or reading with customers as codes (Pseudonymous Mode). The choice is recorded as per-shop tool settings, which the Merchant can change tool by tool on the dashboard. The Merchant is responsible for its choice and for checking the preselected option before accepting. Vilkas may limit the access level of an account.
4.4 The Merchant is responsible for the access granted to Client Applications, chooses how long it lasts and can revoke it at any time from the dashboard. A lifetime longer than one year is the Merchant's own choice, of which the Service warns.
4.5 The Merchant may allow Vilkas's designers to work on a shop's page content through the Service, either reading it only or also editing it, until a date the Merchant chooses. A Vilkas designer may also activate such access on the Merchant's behalf when the Merchant has agreed to it in another way, for example by phone or email. The designer then records where the consent came from, and the Merchant sees that record with the designer's name on the dashboard and, where the account has an email address, by email. The access never covers orders, customers or newsletter subscribers, and it is not available in the shop back office panel. The Merchant sees who uses the access and can end it at any time from the dashboard. Vilkas's designers act in the shop on the Merchant's instructions, and what they change is recorded in the log.
5.1 Vilkas AI Model (A). Vilkas selects the language model and its host. Vilkas may change the model without notice; a change of host is a change of sub-processor, notified under section 5 of the Data Processing Addendum. Vilkas undertakes that the model is run within the European Economic Area, that the model gateway and hosts are companies under European ownership and control, established in the European Economic Area or the United Kingdom, and not subsidiaries of groups from outside Europe, that the Merchant's questions and Shop Data are not used to train models, and that the model provider does not retain them after producing the answer. Use is limited by the allowance in clause 7.
5.2 Own AI Provider (B). When the Merchant connects a Client Application or, where the function is enabled, enters its own API key or links its own OpenRouter account, the Merchant selects its AI provider itself and contracts with it directly. Vilkas discloses Shop Data to that provider on the Merchant's instruction and is not responsible for the provider's processing, location, retention, training use or pricing. The Merchant is responsible for having a data processing agreement with its provider and a transfer mechanism where data is processed outside the European Economic Area.
5.3 Where the Merchant has entered its own API key, it is stored encrypted and used only for the Merchant's own requests. The Merchant bears the costs the key incurs with its provider.
5.4 The Service's chat page and the assistant panel in the shop back office use the Vilkas AI Model. Using an own API key or OpenRouter account in them is possible only where Vilkas has enabled the function; the Merchant may then switch usage model in the Service's settings, and the switch applies to the Merchant's whole account, not to a single shop. A Client Application can always be connected.
6.1 The language model may produce incorrect, incomplete or invented answers and may interpret a request differently from what the Merchant meant. The Merchant verifies answers before acting on them.
6.2 Write tools change the shop immediately and there is no undo. The Merchant is responsible for every change the language model makes at the request of the Merchant or a Back Office User as if the Merchant had made it, including changes to and deletions of products, categories, orders, customer records and legal pages.
6.3 The language model is instructed to ask the Merchant for confirmation before deletions and bulk changes. This is an instruction to the model, not a check made by Vilkas, and the model may fail to follow it. A confirmation prompt is not a review by Vilkas and does not shift responsibility to Vilkas.
6.4 The Merchant is responsible for the lawfulness and accuracy of content the language model produces or changes (for example product descriptions, legal pages, customer messages), as for Material under clause 6.2 of the Service Agreement.
6.5 The Merchant must not use the Service to attempt access to another merchant's data, to circumvent tool restrictions, to direct the language model to act contrary to these terms, or to load the Service in an automated way that departs from ordinary use. Clause 6.9 of the Service Agreement applies.
7.1 Use of the Vilkas AI Model is limited by a per-account allowance counted in processed tokens over five-hour periods and per calendar week. The Service shows the Merchant the share used and the reset time, not the amount. Once the allowance is spent, the Vilkas AI Model does not answer until the reset, unless the account holds purchased additional usage (clause 3.3). The Merchant may then also use its Own AI Provider.
7.2 Vilkas may change allowances and other usage limits by notice in the Service. An allowance is sizing, not a service commitment.
8.1 The Merchant is the controller of the personal data contained in Shop Data and Vilkas is its processor under clause 8 of the Service Agreement. The supplementary terms for the Service are in the Data Processing Addendum (Annex 1), which forms part of this agreement.
8.2 The Merchant decides under clause 4.3 whether identifiable customer data is passed to the language model or whether Pseudonymous Mode is used. When connecting, full mode is preselected, and Pseudonymous Mode is chosen by the Merchant. The Merchant is responsible for its choice being consistent with its own privacy notice and legal basis.
8.3 Vilkas is the controller of personal data relating to the Shop Conductor accounts, logins, usage log and support requests of the Merchant and its Back Office Users. These are described in the Service's privacy notice.
9.1 The credential of a connected Client Application is a secret equivalent to login credentials. The Merchant must not disclose it to a third party and revokes the connection at once if it suspects misuse.
9.2 The Merchant is responsible for removing a Back Office User's access in the shop's user management when that person's role ends. Once a Back Office User's access is removed, no new assistant sessions are opened for them, and a session already open ends within 30 minutes.
9.3 Vilkas keeps a 90-day log of tool calls (timestamp, tool, shop, request parameters, Client Application) and of requests sent to the online shop (address, content sent, error response) for security, abuse investigation and support. In write operations the content sent may include customer data. Vilkas also keeps an event log of sign-ins, connections, settings changes, acceptances of these terms and assistant sessions opened, which records the Back Office User identifier when a session is opened for them; no fixed retention period currently applies to the event log. The Merchant can obtain its own log data by asking Vilkas.
10.1 Shop Data, the Merchant's questions and the answers the language model produces for the Merchant belong to the Merchant. Vilkas does not use them to train language models or for any purpose other than providing the Service, security and the anonymous usage analysis permitted by clause 7.15 of the Service Agreement.
10.2 The Service, its software, prompts and support article index belong to Vilkas or its licensors.
11.1 Support requests about using the Service are made through the Service's support form or through the assistant. Questions about using the shop fall under Vilkas shop support in accordance with the Service Agreement.
11.2 Instructions the assistant gives from support articles are compiled from Vilkas's public documentation and do not replace support.
12.1 Vilkas may change these supplementary terms. The changed terms are published in the Service, and the Service asks the Merchant to accept them before continuing to use the dashboard and the chat page. For the Merchant, the change takes effect on acceptance. Shops and Client Applications already connected keep working under the previous terms until then. A Merchant that does not accept a change may stop using the Service under clause 14. Updating the sub-processor list (Annex 2) under section 5 of the Data Processing Addendum is not a change of terms within the meaning of this clause.
12.2 Changes to sub-processors are notified under the Data Processing Addendum.
13.1 Clauses 7.14 and 10.5 of the Service Agreement apply. Vilkas is not liable for loss resulting from an incorrect answer of the language model, a change made to the shop at the request of the Merchant or a Back Office User, the conduct of the Merchant's Own AI Provider, or the Merchant's choice of tools and access level.
13.2 The limitation does not apply to loss caused intentionally or by gross negligence, nor to processor liability that cannot be limited by law.
14.1 The agreement is in force until further notice. The Merchant may stop using the Service at any time by removing the app from its shop, revoking connected Client Applications or deleting its account.
14.2 The Service ends when the Merchant's online shop agreement with Vilkas ends. Vilkas then removes the shop's connection from the Service.
14.3 Vilkas may suspend or terminate the Service under clauses 9 and 12 of the Service Agreement, and immediately if use endangers the Service, other merchants' data or Vilkas's agreements with its sub-processors.
14.4 After termination Vilkas deletes the Merchant's account, connections, stored keys and pseudonym codes within 30 days. Tool call and shop request logs are deleted at the end of their 90-day retention period. The event log and daily usage totals are kept. They hold an account identifier that no longer refers to any account and, for panel sessions, the Back Office User identifier, but no email addresses or other contact details. Purchase records for additional usage are kept for the period required by accounting law.
15.1 Clause 13 of the Service Agreement applies.
This addendum supplements clause 8 of the Service Agreement and its annexes (Customer Register Description and Conditions for Processing Personal Data of 7 May 2018).
1.1 This addendum sets out, in accordance with Article 28 of Regulation (EU) 2016/679 (the "GDPR"), how Vilkas Group Oy (the "Processor") processes personal data on behalf of the Merchant (the "Controller") in the Shop Conductor service.
1.2 The addendum supplements clause 8 of the Service Agreement and its annexes, which continue to apply to all processing in the hosting of the online shop. In case of conflict, this addendum applies to processing in the Shop Conductor service.
3.1 The Processor processes personal data only on the Controller's documented instructions. The instructions are the Service Agreement, the Shop Conductor supplementary terms, this addendum, and the choices the Merchant makes in the Service: the permissions chosen when connecting (clause 4.3 of the supplementary terms), tools enabled per shop and per connection, the choice of pseudonymous or full mode, the choice of AI provider, the connection of a Client Application and the access granted to Vilkas's designers (clause 4.5). An individual request given to the assistant is the Controller's instruction for the processing of that request.
3.2 The Processor informs the Controller if, in its opinion, an instruction infringes data protection law.
3.3 The Processor ensures that persons processing personal data are bound by confidentiality.
3.4 The Processor implements the measures under Article 32, the main ones being described in section 7.
3.5 The Processor assists the Controller in responding to data subject requests insofar as the request concerns data processed in Shop Conductor. The Service retains customer data only in the log and as pseudonym code mappings, so a request concerns the shop's data, the log and the pseudonym codes.
3.6 The Processor notifies the Controller of a personal data breach without undue delay and at the latest within 48 hours of becoming aware of it, and provides the information under Article 33(3) as it becomes available.
3.7 The Processor assists with the obligations under Articles 35 and 36 by providing this addendum, the sub-processor list and the technical description of the Service.
3.8 The Processor makes available the information necessary to demonstrate compliance with Article 28 and allows audits by the Controller or an independent auditor mandated by it at reasonable intervals, at most once a year and with 30 days' notice. An audit must not endanger other merchants' data.
4.1 Vilkas AI Model (usage model A). The Processor engages as sub-processors the language model gateway and hosts named in the sub-processor list. The Processor remains liable for them under Article 28(4) and undertakes that (a) the language model is run in a data centre within the European Economic Area, (b) the sub-processor does not retain questions, Shop Data or answers after producing the answer, (c) the data is not used to train models, (d) an Article 28 agreement is in place with the sub-processor, and (e) every language model gateway and host is a company under European ownership and control, established in the European Economic Area or the United Kingdom. Subsidiaries of groups from outside Europe, including their data centres located in Europe, are not used to run the language model. Switching language model within a host named in the sub-processor list is not a change of sub-processor; switching host is.
4.2 Own AI Provider (usage model B). When the Controller connects a Client Application, its own API key or its own OpenRouter account to the Service, it gives the Processor a documented instruction to disclose Shop Data to the AI provider it has named. That provider is the Controller's own processor or an independent controller, not a sub-processor of the Processor. The Controller is responsible for having an Article 28 agreement with the provider, a Chapter V transfer mechanism where data is processed outside the European Economic Area, and for its own privacy notice covering the disclosure. The Processor's obligations under this addendum are limited to the Shop Conductor server.
4.3 In both models the Controller may limit the data passed to the language model by choosing Pseudonymous Mode, in which customer and subscriber identities are replaced with HMAC codes, addresses are reduced to country and the first two characters of the postcode, and free text is removed. Only the Controller can resolve a code, through the Service's lookup page, and every lookup is logged. When connecting, full mode is preselected, and Pseudonymous Mode is chosen by the Controller under clause 4.3 of the supplementary terms.
5.1 The Controller gives the general authorisation referred to in Article 28(2) GDPR for sub-processors that meet the conditions of clause 4.1 and are named in the sub-processor list (Annex 2) as it stands from time to time. The list is published on the Service's terms page. Updating the list under clause 5.2 is not a change of the supplementary terms or of this addendum and does not require a new acceptance.
5.2 The Processor notifies a new or replaced sub-processor at least 30 days before it is taken into use by adding it to the sub-processor list with the date of use, and by notice in the Service and by email where the account has an email address. The Controller may object in writing on reasonable data protection grounds before that date. If no solution is found, the Controller may stop using the Shop Conductor service without penalty. The online shop agreement is unaffected. Removing a sub-processor from the list needs no notice period.
5.3 The Processor imposes on each sub-processor by contract obligations equivalent to this addendum and is liable for the sub-processor's performance as for its own.
6.1 In usage model A personal data is processed in data centres within the European Economic Area. Two sub-processors, Requesty Ltd and Neural Compute Ltd, are established in the United Kingdom. Disclosure to them is a transfer outside the European Economic Area, and it relies on the European Commission's decision on the adequacy of data protection in the United Kingdom (renewed 19 December 2025, valid until 27 December 2031). The sub-processor list names the domicile and the processing country of each sub-processor.
6.2 In usage model B any transfer is made by the Controller to its own provider under clause 4.2.
8.1 When the Shop Conductor service ends, the Processor deletes the Merchant's account, connections, stored keys and pseudonym codes within 30 days. Tool call and shop request logs are deleted at the end of their 90-day retention period unless law requires longer retention. The event log is kept as set out in clause 14.4 of the supplementary terms. Clause 8.5 of the Service Agreement applies to the shop's data.
9.1 The parties' liability is governed by the limitations in the Service Agreement and the Shop Conductor supplementary terms to the extent Article 82 GDPR permits. The parties are liable to each other under Article 82 for the part of any damage caused by their own breach.
10.1 Processor's data protection contact: privacy@vilkas.fi. The Controller's contact details are those on its Shop Conductor account.
Sub-processors of personal data used by Vilkas Group Oy in the Shop Conductor service. This is the living list referred to in section 5 of the Data Processing Addendum: a new sub-processor is added here with its date of use at least 30 days before it is taken into use, and the language model gateway and hosts must always meet the conditions of Annex 1 clause 4.1 (European Economic Area, no retention, no training use, an Article 28 agreement, European ownership and control). Entity details, processing countries and data processing agreements were checked against public company registers and the vendors' own contracts on 6 November 2026.
Not sub-processors: emails are sent from Vilkas's own relay, support article search and its embedding model run on the Shop Conductor server and the search text is sent nowhere, and software distribution (GitHub) handles no personal data.
Alternative route: if Vilkas switches the gateway to OpenRouter, the list gains OpenRouter, Inc. (United States, gateway), Inceptron (Finland) and NextBit (Spain). A gateway domiciled in the United States then requires a transfer assessment even though the models run in the EU.
In usage model B the providers the Merchant selects itself (for example Anthropic, OpenAI, Google, OpenRouter, Requesty with the Merchant's own key) are not sub-processors of Vilkas and are not on this list.
Version 2026-11-06