Security posture
Public pages are designed to avoid collecting broker credentials, payment methods, raw account identifiers, balances, positions, or orders.
OmniMint should be useful to browse while keeping research, account, broker, payment, and creator boundaries obvious.
Public pages are designed to avoid collecting broker credentials, payment methods, raw account identifiers, balances, positions, or orders.
Browsing, onboarding, subscriptions, and creator follows do not grant read, paper-trading, or live-trading broker authority.
Paper, live, and research-only states must remain visibly separate so users understand when an action is educational versus executable.
Strategies, creators, rankings, and backtests are historical research context only and are not individualized investment advice.
Backtests can be incomplete, stale, or overfit. AI optimization ideas must stay proposed experiments until separately reviewed.
Creator content can be followed, compared, and subscribed to for research, but content access never authorizes broker deployment.
Plain-language data boundaries, future export/delete rights, and never-store fields.
Research-only product terms, creator-content boundaries, and prohibited advice claims.
What users can safely share and what OmniMint will never ask for.
Support routing that avoids passwords, keys, broker credentials, and payment data.
Read-only, paper, and live permission concepts before any future connection flow.
How creator evidence, disclosure, and review states should be evaluated.
Subscription-plan education with provider checkout disabled.