Trust & Compliance

MoTA supports brokerage account connection through third-party connectivity infrastructure, including SnapTrade where available.

Connected account data may be used to help users view portfolios, analyze holdings, review risks, prepare trading decisions, and understand account-related context.

The availability, accuracy, completeness, and freshness of brokerage data may depend on the connected brokerage, third-party infrastructure, account permissions, market data conditions, and product availability.

MoTA’s use of third-party infrastructure does not imply that such third parties endorse MoTA, guarantee MoTA’s outputs, or are responsible for MoTA’s AI analysis or product experience.

MoTA’s AI agents may analyze market information, portfolio data, risk factors, holdings, candidate actions, and related context.

AI-generated outputs are intended for information organization, analysis support, workflow preparation, and user review.

They are not investment advice, performance guarantees, suitability determinations, legal advice, tax advice, or licensed professional opinions.

AI outputs may be incomplete, inaccurate, delayed, based on limited data, or affected by model limitations. Users should independently review relevant information, account status, market conditions, risk exposure, and personal circumstances before making investment or trading decisions.

Investing involves risk, including potential loss of principal. MoTA does not guarantee returns, risk reduction, execution quality, or investment outcomes.

Some MoTA demos, onboarding flows, examples, testing environments, or Alpha experiences may use simulated data.

Simulated data is used to demonstrate product workflows, explain how AI agents may operate, and help users explore MoTA’s investment decision process.

Simulated data should not be treated as live account data, personalized investment advice, or a basis for real trading decisions.

When data is simulated, delayed, stale, restricted, or otherwise limited, MoTA aims to make that status clear in the user experience.

MoTA treats account data, holdings, transactions, portfolio metrics, strategy preferences, agent interactions, trading previews, confirmation records, and operational logs as sensitive information.

Our product governance approach is based on controlled access, permission-based use, and minimum necessary data exposure.

MoTA prioritizes structured summaries, permissioned outputs, and clear status indicators instead of default access to raw data, restricted data, exports, or third-party access.

Third-party agents and creator-built agents do not currently receive access to users’ sensitive brokerage or portfolio data.

If MoTA introduces expanded third-party or creator agent access in the future, such access should require explicit user permission, clear data scope, additional product controls, and user-facing disclosure before sensitive information is made available.

MoTA is designed to help users understand the source and status of information used in portfolio views, AI analysis, risk review, and trading workflows.

Where applicable, MoTA may distinguish between:

• Connected account data
• Simulated data
• Delayed data
• Stale or outdated data
• Restricted data
• Unverified or incomplete data

When data source, freshness, completeness, or evidence is limited, MoTA aims to present those limitations clearly rather than pushing users toward false certainty or unsupported trading actions.

MoTA is designed with clear product boundaries. By default:

• MoTA does not let AI agents independently place real trades without user confirmation.
• MoTA does not treat AI outputs as guaranteed investment outcomes.
• MoTA does not currently allow third-party or creator-built agents to access sensitive brokerage or portfolio data.
• MoTA does not treat simulated data as live account data.
• MoTA does not guarantee execution, market availability, brokerage acceptance, or third-party system uptime.
• MoTA does not broadly expose raw sensitive data by default.
• MoTA does not replace the user’s responsibility for final investment and trading decisions.

MoTA’s governance design supports reviewability for important actions across the product experience.

This may include records related to authorization, revoked access, account connection, agent activity, signal generation, trading previews, user confirmations, blocked actions, sensitive data access, and downstream workflow events.

These records are intended to support user review, operational troubleshooting, product governance, and permission-aware explanations.

They are not a substitute for regulatory reports, external audit reports, third-party certifications, or formal compliance filings.

Review the key privacy, risk, and product boundary disclosures that apply to MoTA’s AI-powered investment workflows.

MoTA may use authorized account data, portfolio information, holdings, transactions, strategy preferences, agent interactions, trading previews, confirmation records, and operational logs to support product functionality.

This may include portfolio views, risk review, AI agent analysis, decision preparation, trading workflow support, user-facing explanations, troubleshooting, and product governance.

MoTA’s data governance approach is based on permissioned access, controlled visibility, and minimum necessary data use.

Sensitive information is not intended to be broadly exposed by default through raw exports, unrestricted third-party access, or uncontrolled agent access.

Users may affect the scope of data use by connecting accounts, granting permissions, revoking authorization, or removing account connections where supported.

MoTA supports brokerage account connection through third-party connectivity infrastructure, including SnapTrade where available.

Brokerage connection may allow MoTA to display account-related information, analyze portfolios, review risks, and support trading workflows based on authorized user permissions.

The availability, accuracy, completeness, and freshness of brokerage data may depend on the connected brokerage, third-party infrastructure, account permissions, market data conditions, and product availability.

MoTA’s use of third-party infrastructure does not imply that such third parties endorse MoTA, guarantee MoTA’s outputs, or are responsible for MoTA’s AI analysis or product experience.

MoTA’s AI agents may analyze market information, portfolio data, risk factors, holdings, candidate actions, and related context.

AI-generated outputs are intended for information organization, analysis support, workflow preparation, and user review.

They are not investment advice, performance guarantees, suitability determinations, legal advice, tax advice, or licensed professional opinions.

AI outputs may be incomplete, inaccurate, delayed, based on limited data, or affected by model limitations.

Users should independently review relevant information, account status, market conditions, risk exposure, and personal circumstances before making investment or trading decisions.

Investing involves risk, including potential loss of principal. MoTA does not guarantee returns, risk reduction, execution quality, or investment outcomes.

MoTA may support real trading workflows through connected brokerage accounts and third-party infrastructure.

Before a real trading action is submitted, users are expected to review the trading preview, order details, account context, data status, and relevant risk information.

AI agents do not independently place real trades without explicit user confirmation.

User confirmation does not guarantee execution.

Trading availability and execution may depend on brokerage account status, user permissions, market conditions, order type, liquidity, third-party platform availability, product controls, and applicable agreements.

Third-party agents and creator-built agents do not currently receive access to users’ sensitive brokerage or portfolio data.

Sensitive data may include connected account data, holdings, transactions, portfolio metrics, trading previews, confirmation records, agent interactions, and operational logs.

If MoTA introduces expanded third-party or creator agent access in the future, such access should require explicit user permission, clear data scope, additional controls, and user-facing disclosure before sensitive information is made available.