PRIVACY
Account and venue records are available only inside authenticated, owner-scoped routes. This page lists what is stored, where a credential is permitted to exist, and what the product refuses to collect at all.
STORED
Four record types. Nothing else is required to run the product.
An email address, a password hash and, when you enrol a second factor, a TOTP secret and single-use recovery codes. There is no funding flow, so no card, bank or payout detail is collected.
Reachable only inside your own session.A broker or exchange token is stored per connection and encrypted at rest with a separately managed key. Disconnecting revokes it with the provider and overwrites the stored value.
Per connection, never one shared credential.When a connection is authorized and synchronized, the venue balances, positions, orders and fills are imported and attributed to the account that owns them.
Requires a connected account.A single marketing-consent flag is kept in your browser local storage so the site can remember your choice between visits. It carries no account or trading information.
Browser-only, not an account record.CREDENTIALS
Each row is a boundary the implementation enforces, not an intention.
NOT COLLECTED
These are absent from the product rather than hidden behind a setting.
Recovery phrases and withdrawal permissions are never requested, because this product does not run a wallet and does not hold funds.
There is no on-site funding flow, so no payment instrument, bank account or payout detail is collected anywhere in the product.
Statements, balances and credentials are never requested through email or social media, and the product publishes no inbox to send them to.
Balances, holdings, profit, loss, strategy allocation, risk appetite, order sizes, wallet addresses and individual trades are never sent to Meta.
The pixel is mounted on the landing page only, so every other route is an uninstrumented document and nothing follows you into the account area.
Public market data is read from provider endpoints that receive no account information, and no customer record is used to request a price.
MEASUREMENT
The landing page may carry anonymous marketing measurement, and only after you consent. Every other page is uninstrumented, including the whole account area.
The Meta pixel is not loaded until you grant marketing consent. A declined or unanswered choice loads no pixel and sends no event.
Events are sent only when a pixel ID is configured for the deployment. With no ID, the public site works normally and sends nothing.
Two event names, and only from the landing page: PageView when the pixel loads, and Stay10Seconds after ten seconds of visible consented time on that page. No other event exists in the implementation.
No balance, holding, profit, loss, strategy allocation, risk appetite, order size, wallet address, API secret or individual trade event.
Stay10Seconds counts only visible, consented time on the landing page, once per page view. Time with the tab hidden does not count.
There is no reviewer-only content and no hidden real-money redirect. Every visitor sees the same product for the same eligibility state.
CONTROLS
Implemented controls, so nothing here depends on an operator’s manual action.
Connection settings list each connected venue. Disconnecting revokes the stored token with the provider and stops further imports.
An account can export its own fills, including fee and fee currency, as CSV. The export is scoped to the authenticated owner.
Completing a password reset signs out all existing sessions, not only the current one.
TOTP enrolment and single-use recovery codes are available today, and a confirmed code cannot be replayed inside its window.
SCOPEThis page describes the records the running release actually handles. A capability that is not enabled is stated as unavailable instead of being described as a plan.
SECRETSNever send a password, API key, recovery phrase or account token to any channel. No operator in this product will ask for one.