> ## Documentation index > Fetch the complete documentation index at: https://docs.odysseysignal.com/llms.txt > Use this file to discover all available pages before exploring further. # Platform and AI Services User Terms > These Services Terms form part of the Agreement between the Customer, Users and Odyssey. Version 2 ยท Effective 10 November 2026 All versions: version 2 (10 November 2026) https://docs.odysseysignal.com/legal/user-terms/v2.md; version 1 (15 September 2026) https://docs.odysseysignal.com/legal/user-terms/v1.md ## 1. Nature of the Services The Services include **Platform Services**, **AI Services**, and **Consulting Services**. Outputs may be generated through automated systems, human analysis, or a combination of both. ## 2. Informational Purpose Only All outputs, including Refined Data, AI Output, and Consulting Services, are provided for informational purposes only. They do not constitute legal, financial, or professional advice. ## 3. AI Services AI Services generate outputs automatically using statistical models and machine learning models like Large Language Models (LLM). Such outputs: - may be inaccurate, incomplete, or misleading, - may vary depending on inputs, - may change over time. ## 4. Consulting Services Consulting Services are based on available data and professional judgment. Odyssey does not guarantee that any conclusions or recommendations will achieve specific business outcomes. ## 5. Customer Responsibility The Customer is solely responsible for: - evaluating outputs, - verifying accuracy, - decisions made based on the Services. ## 6. Customer Input Responsibility The Customer is responsible for all data, content, documents, and files submitted or uploaded to the Services, including through AI Services. Any data shared with Odyssey Services is processed in accordance with the applicable [Data Processing Agreement](https://docs.odysseysignal.com/legal/data-processing-agreement) (DPA). The Customer shall ensure that: - it has all necessary rights and permissions to submit or upload such data, content, documents, and files; - no personal data, confidential information, sensitive information, or other protected data is submitted or uploaded unless legally permitted and appropriate safeguards are in place; and - all use of the Services, including the uploading of files to AI Services, complies with applicable laws, regulations, contractual obligations, and internal policies. Odyssey does not control or independently verify user inputs or files uploaded to the Services, and the Customer remains responsible for the content and legality of such inputs. ## 7. AI Data Handling Odyssey does not provide personal data to AI Services. AI Services are designed to operate without personal data. Odyssey cannot guarantee that users do not submit personal data and are not liable for any such activity. ## 8. Third-Party Technologies The Services may rely on third-party technologies, including AI providers. Odyssey is not responsible for errors or limitations caused by such providers. ## 9. Acceptable Use The Customer shall not: - use AI Services unlawfully, - generate harmful or misleading content, - rely on AI for fully automated decisions without human review, - attempt to reverse engineer AI systems. - attempt to force guardrails built into the AI Services. ## 10. Evolution of the Services AI Services and methodologies may evolve over time, which may affect outputs. ## 11. No Guarantee of Outcomes Odyssey does not guarantee any business, marketing, or strategic outcomes resulting from the use of the Services. ## 12. API and MCP Access 12.1 The Services may be accessed programmatically through Odyssey's application programming interface (the "API") and Odyssey's Model Context Protocol server (the "MCP Server"), together "Programmatic Access". This section applies in addition to the rest of the Agreement whenever the Services are accessed through Programmatic Access, including through software, scripts, AI assistants or other tools connected by a User. 12.2 Credentials. Access through the API requires an API key issued to the Customer's organisation. Access through the MCP Server is made with a User's own sign-in and is limited to that User's permissions in the Services. The Customer shall: - keep API keys confidential and store them securely; - not share API keys or sign-in credentials with any Third Party, or place them in public code, websites or applications; - revoke an API key without delay if it may have been exposed; - be responsible for all use made with its API keys and its Users' credentials. 12.3 Permitted use. Raw Data, Refined Data, Reports and AI Output obtained through Programmatic Access may only be used for the Customer's own internal business purposes and for the Brand(s) for which the Services have been purchased, as stated in the Statement of Work and in accordance with Section 10 of the Terms. 12.4 No AI training. The Customer shall not, and shall ensure that its Users do not: - use data obtained through Programmatic Access to train, fine-tune or otherwise improve any machine learning or AI model; - connect the MCP Server, or send data obtained through the API, to an AI application, assistant or account where the provider may use prompts, outputs or connected data to train or improve its models. The MCP Server may only be connected to AI applications used under a business or enterprise account in which the provider's use of customer data for model training is contractually excluded or turned off. The Customer is responsible for verifying this before connecting and for keeping it in place. 12.5 No redistribution. The Customer shall not: - resell, sublicense, publish or otherwise make data obtained through Programmatic Access available to any Third Party, except as permitted under Section 10 of the Terms; - use Programmatic Access to build or supply a product or service offered to Third Parties, or one that competes with the Services; - systematically extract or copy data beyond what its permitted use requires, or to create a copy or substitute of the Services or their data. 12.6 Limits and security. The Customer shall: - respect rate limits and other technical limits, and not attempt to circumvent them, for example by using several API keys or accounts; - not use Programmatic Access in a way that disrupts, overloads or impairs the Services; - not attempt to access data or organisations other than those it is authorised to access. Odyssey may set, change and enforce such limits, and may suspend or revoke Programmatic Access in accordance with Section 6 of the Terms if this section is breached or the Services are put at risk. 12.7 AI assistants and other third-party tools. When a User connects the MCP Server or the API to an AI assistant or another third-party tool, the data the User retrieves is passed to that tool and its provider. Such tools are chosen and controlled by the Customer, and their providers are not sub-processors of Odyssey. The Customer is responsible for ensuring that this use complies with the Agreement, its internal policies and the tool provider's terms. Section 3 applies to outputs generated by such tools, and Odyssey is not responsible for them. 12.8 Changes. Odyssey may develop, change or discontinue features of the API and the MCP Server. Odyssey will aim to give reasonable notice of changes that break existing integrations, as described in the API documentation.