Privacy Policy

Data We Process

Account state

Authentication state, account identifiers, entitlement signals, and token balance data are read from the MarketSchema platform when you use the research app.

Research activity

Exact Hub instrument and issuer identity, Basket ID and membership, PRIMARY or CONTEXT role, effective and known-at clocks, revision identity, typed availability, cited source receipts, saved historical packets, downloads, and API reads can be processed so the product can preserve governed context and auditability.

Telemetry

The app can collect technical logs, request metadata, device/browser information, performance data, errors, and security events needed to operate and protect the service.

What We Do Not Need

MarketSchema Research does not ask for brokerage credentials, trading authority, order instructions, portfolio allocations, or personalized suitability details. The product is not a broker, investment adviser, exchange, or execution venue.

This privacy boundary supports the same product boundary repeated throughout the app: MarketSchema Research is informational research, not investment advice or trading authority.

How We Use Data

Data is used to operate account access, bind public evidence and prospective observations to the exact Hub Asset and point-in-time Basket contract, preserve typed unavailable states, show account and historical activity, debug failures, enforce limits, protect against abuse, improve lawful source coverage, and maintain auditability.

Saved historical research and point-in-time records may be retained so the Vault, history views, API reads, exports, and evidence-change context remain useful and reproducible. Current fresh Research mutations do not create or refresh a packet.

Service Providers

MarketSchema Research may use infrastructure, authentication, analytics, storage, payment-platform, and lawful public-source providers to serve and protect the current read plane. Those providers receive only the data needed for their role. The current Research path does not initiate fresh provider or model compute or spend.

We do not sell personal information. Data may be disclosed when required for security, legal compliance, service protection, or a business transfer involving the product.

Controls

Account, billing, and identity controls live on the MarketSchema platform. Product support or privacy requests should be routed through the main MarketSchema account channel.

Fresh Research mutation paths are currently typed unavailable: they do not spend tokens or call a provider or model. Browser privacy controls, ad-blockers, and analytics opt-outs may affect some telemetry, but core security, entitlement, Hub identity, and saved historical records can still be needed to provide the read service.