Risk Disclosure
Using AI-assisted automation in trading and related operational settings involves substantial risk. This Risk Disclosure is intended to highlight major categories of risk that may arise when using View Market, but it is not exhaustive and should not be treated as a substitute for your own testing, supervision, legal review, or professional risk assessment.
Last updated March 27, 2026
General Trading and Loss-of-Capital Risk
Trading and investment activity can result in significant losses, including the loss of all or substantially all capital committed to a strategy or account. Market prices can move rapidly because of volatility, illiquidity, gaps, news events, macroeconomic shifts, exchange outages, and other factors that may not be foreseeable or controllable. Slippage, widening spreads, limited liquidity, partial fills, and market closures can materially affect actual outcomes even where a strategy appeared sound in prior conditions. The existence of automation, alerting, or structured workflow logic does not eliminate core market risk, and no aspect of View Market should be understood as reducing, insuring, or capping the financial consequences of adverse market movement.
Strategy, Model, and Automation Failure Risk
Automations may fail because of prompt design flaws, rule conflicts, logic errors, stale assumptions, overfitting, weak exception handling, model drift, incomplete training context, or changing market regimes that invalidate prior behavior. A workflow that appears to operate correctly in a test or staging environment may behave differently when exposed to real-time data, live broker constraints, or unanticipated edge cases. Small configuration changes, model updates, or changes in external dependencies may produce effects that are not obvious until the workflow is under real operational pressure. AI-assisted systems can also misclassify inputs, generate misleading summaries, or produce outputs that appear reasonable while remaining materially wrong, which makes independent validation and ongoing supervision essential.
Data Quality, Latency, and Infrastructure Risk
Any workflow that relies on data feeds, webhook events, exchange messages, system clocks, network transport, or cloud-based infrastructure is exposed to latency, sequencing, completeness, and accuracy risk. Delayed, duplicated, stale, corrupted, or missing data may cause triggers to fire at the wrong time, produce inaccurate conclusions, or fail to respond when action is expected. Timestamp inconsistencies, queue delays, retry behavior, and background processing gaps can also distort how a workflow interprets incoming events. Infrastructure dependencies such as internet access, hosted services, background jobs, and notification channels may degrade or fail without warning, and even brief interruptions can be material in fast-moving environments.
Broker, Exchange, and Third-Party Integration Risk
View Market relies on external systems selected by the user, and those systems may impose their own rate limits, authentication requirements, maintenance windows, jurisdictional restrictions, commercial policies, and technical limitations. Brokers or exchanges may reject instructions, cancel sessions, delay acknowledgements, disable APIs, alter feature sets, or interpret account permissions differently than expected. Market data and AI model providers may also change contracts, pricing, output behavior, or service availability. Differences between sandbox and production environments, account tiers, or regional service configurations may further affect whether an integration behaves as expected. These external dependencies can materially affect your workflows even where the View Market interface itself appears to function normally.
Cybersecurity, Credential, and Access-Control Risk
Any platform that stores account access, integration credentials, operational settings, or sensitive workflow context may be exposed to unauthorized access, credential theft, phishing, malware, insider misuse, or accidental disclosure. If your broker keys, API tokens, support data, or workspace permissions are compromised, the resulting harm may include financial loss, data exposure, service misuse, reputational damage, and regulatory consequences. Shared devices, weak password hygiene, excessive permission grants, and delayed removal of former team members can materially increase that risk. You are responsible for using appropriate access controls, secret-management practices, permission boundaries, device security, user offboarding, and internal review processes suitable for the sensitivity of your activities.
Regulatory, Tax, and Compliance Risk
Automated trading, AI-assisted decision support, electronic communications, market-data use, and outsourced technical operations may all be subject to legal, tax, licensing, recordkeeping, privacy, and regulatory obligations that differ across jurisdictions and can change over time. A workflow that is permissible in one market, entity structure, or customer segment may be restricted or prohibited in another. Internal compliance policies, customer agreements, exchange rules, and supervisory expectations may impose standards that are stricter than baseline law. View Market does not determine whether your use of the service is lawful or compliant for your circumstances, and you remain solely responsible for assessing and satisfying all legal, tax, contractual, and regulatory requirements connected to your use of the platform.
User Obligation to Test, Monitor, and Apply Safeguards
Because the risks described in this disclosure can interact in unpredictable ways, you should use robust pre-deployment testing, paper or sandbox environments where available, approval workflows, alerting thresholds, exception handling, position or exposure limits, and clear human escalation paths before relying on any automation in production. Ongoing monitoring is equally important, as systems that once performed acceptably may become unreliable when markets, providers, models, or business requirements change. Periodic review of assumptions, permissions, incident logs, and fallback procedures is also important to ensure safeguards remain effective over time. You should also maintain contingency plans, including the ability to pause workflows, revoke credentials, switch providers, or intervene manually when risk conditions change.
Non-Exhaustive Nature of This Disclosure
This Risk Disclosure summarizes important categories of risk but cannot identify every scenario, dependency, failure mode, or legal consequence that may arise from your use of View Market. New risks may emerge from product updates, changing market conditions, evolving laws, internal process changes, or interactions among systems that were not previously material. The relative importance of particular risks will differ depending on your strategy, integrations, counterparties, jurisdiction, and internal controls. You should therefore treat this disclosure as one part of a broader diligence process and not as a complete statement of every risk relevant to your operations, personnel, counterparties, or customers.