Orbital Wealth
Security principles
Orbital Wealth is being designed around read-only access, user authorization, data minimization, and separation between customer accounts.
Orbital Wealth is currently in development. Security controls, hosting architecture, and operational procedures remain subject to testing, review, and refinement before commercial release.
Read-only by design
Orbital Wealth is intended to provide portfolio visibility without offering order entry, trade execution, account transfers, or other transaction capabilities.
Users will continue to use their financial provider’s established mobile or desktop applications when they need to review and submit transactions.
Credential and token handling
The planned commercial architecture separates customer authorization information from application configuration and source code.
Provider authorization credentials are intended to be encrypted when stored. Access will be limited to the application services that require them to retrieve authorized portfolio information.
The system is also being designed to support provider token renewal and rotation requirements.
Data minimization
Orbital Wealth is intended to retrieve and process only the information needed to provide its portfolio-monitoring features.
The planned design avoids unnecessary permanent storage of detailed holdings and portfolio history. Information may be temporarily processed or cached as needed to provide reliable service and manage provider-request limits.
Customer isolation
Customer accounts, provider connections, account selections, device authorizations, and application preferences are intended to be associated with the correct Orbital Wealth user.
The application is being developed with explicit customer-scoping controls to prevent one customer’s authorized financial information from being returned to another customer.
Device access
Supported wearable devices are intended to use revocable device-specific authorization rather than permanently storing a customer’s primary account password on the watch.
Device access can be managed independently so that a lost, replaced, or retired device can be removed without requiring the user to recreate the entire account.
Revocation and disconnection
Users are intended to have controls for disconnecting a financial provider, reconnecting an expired authorization, and revoking access for a specific wearable device.
Disconnecting a provider is intended to remove the application’s ability to continue retrieving that user’s account information.
Development and review
Before commercial release, Orbital Wealth’s security controls and operational procedures will be tested and documented. The application may also be subject to review by supported financial providers and distribution platforms.
This page describes current design principles and planned controls. It does not represent a guarantee that every described feature or control has already been deployed.