PositionPilot
Privacy and data summary.
PositionPilot uses data to respond to requests, route users by language and region, connect supported exchange workflows, manage position plans and preserve audit-ready position history.
Exchange API secrets belong to a dedicated credential boundary and are not ordinary profile fields or partner dashboard content.
Requests stay simple, but routeable.
When a person submits a request, PositionPilot may process email, optional profile or community/company text, optional message, selected request type, package interest, exchange preferences, language, region, page context and attribution data. This helps route the conversation to demo, waitlist, affiliate, white-label or support follow-up.
Language is not the same as market availability.
PositionPilot can use language and region separately. Language controls the interface copy. Region can affect checkout, payment options, supported exchange presentation, disclosure placement, partner availability and lead routing.
Product workflows need account-connected context.
When a user connects a supported exchange account, PositionPilot workflows may process exchange account metadata, balances, orders, fills, fees, position records, strategy or plan references, market snapshots, audit events, connection status and credential status metadata where needed for position planning, execution workflow, ledger, audit and review.
API secrets are handled separately from product data.
Exchange API credentials belong in a dedicated credential boundary. Raw API secrets are not shown to referral partners, affiliate partners, ordinary support dashboards or white-label partner admins.
Partner or admin dashboards can use safe operational metadata where appropriate: exchange, connection status, capability status, last verification status, public key suffix or credential state.
Partner visibility depends on the partner path.
Referral and affiliate partners receive attribution and commission reporting only. They do not receive referred users' positions, trades, P&L, balances, exchange credentials, market snapshots or exports.
White-label or custom partner sites can have broader visibility only where the user, partner agreement and product scope allow it. The default is minimum necessary visibility.
Data lifecycle supports return without using access as pressure.
Subscription status can affect automated management coverage, read-only access, archive state and reactivation flow. PositionPilot keeps reasonable export and deletion paths separate from reactivation pressure.
Future archive features may add long-term convenience, reactivation and archive options, but they do not block basic user rights or safety-critical workflows.