Read-only connection
The application reads balances, positions and activity. It cannot place orders or move money.
Security model
Read access is not trade access.
TrustPortfolio reads the minimum portfolio data needed for its calculations. It cannot place orders, move money or expose raw account data publicly.
The control model
Explicit account choice
When multiple accounts are discovered, the user selects one. No synthetic combined account is created silently.
Owner isolation
Authenticated portfolio records are owner-scoped. Public pages receive no private account payload.
Server-held secrets
Provider credentials and tokens stay outside browser bundles and public analytics payloads.
Minimum derived output
Internal operations return bounded calculated facts, not raw account history or identifiers by default.
Fail closed
Missing quotes, identities, rights or holdings remain unavailable or unknown instead of being guessed.
Broker connection
What the permission boundary means
TrustPortfolio uses SnapTrade’s connection flow to receive the account data required for portfolio calculations, not the ability to execute a transaction. Review the provider consent before continuing. If it requests trading or money-movement access, stop and contact support.
Disconnecting must revoke the product connection and begin the documented deletion path. A disconnected state is not evidence that every processor copy has already been deleted; deletion evidence must be tracked separately.
Data and calculations
Security includes number integrity.
Portfolio value, holdings snapshots and exposure results carry source and quality states. An incomplete or stale input is labelled; unknown exposure is not spread across known companies. This prevents a data gap from becoming a falsely precise financial result.
Private analytics rules prohibit portfolio values, weights, returns, identifiers, broker names, securities and free text. Shareable output is explicit, privacy-bounded and separate from a private portfolio page.
Security limits
This page describes product controls, not a certification, penetration-test result or guarantee of zero risk. External services and threats change, so security controls require ongoing review.
Protect your sign-in method and device. Never place passwords, provider tokens or raw portfolio files in a support message. Review the privacy boundary and the calculation methodology.