# Market-data redistribution rights

> Govern display, derived use, storage, attribution, entitlements, audits, vendors, and exchange-specific restrictions for delayed market data.

MyStocks holds full market-data rights for every supported exchange. Technical access still does not
grant a partner unrestricted downstream redistribution: before exposing data to a new audience,
device, geography, latency class, storage workflow, or commercial use, confirm that the intended use
is covered by the executed Partner Agreement and data schedule.

## Classify the use before launch

| Use | Typical classification | Required decision |
| --- | --- | --- |
| Price shown to one authenticated investor | Display | Is end-user display permitted and attributable? |
| Public website, widget, or social post | Public redistribution | Is a public-display licence required? |
| Download, API, spreadsheet, or bulk export | Non-display / redistribution | Usually requires explicit rights |
| Portfolio valuation or P&L | Derived internal use | Define whether values can be stored or exposed |
| Index, signal, model, or AI training | Derived/computational use | Separate permission may apply |
| Data shared with affiliates or vendors | Third-party use | Sub-licence, processor, or vendor approval |

<Callout type="warn" title="No implied exchange licence">
  MyStocks API credentials do not grant a direct exchange licence or permission to resell a feed. Your
  executed data schedule controls. Where it conflicts with a general guide, the executed schedule wins.
</Callout>

## Entitlement record

Maintain a machine-readable register for every market:

| Field | Example |
| --- | --- |
| Exchange / dataset | NSE delayed top-of-book |
| Audience | authenticated retail customers |
| Geography | Kenya and approved diaspora markets |
| Use | in-app display and portfolio valuation |
| Delay | exchange-supplied 15-minute-delayed data |
| Attribution | required text and logo treatment |
| Storage | quote cache TTL and historical retention |
| Export | disabled unless separately approved |
| Effective / renewal date | contract-controlled |
| Evidence owner | data licensing lead |

Gate the product by this register. A commercial team should not be able to turn on a new public widget,
country, or download feature without a recorded rights decision.

## Display standard

- Show the exchange, instrument currency, and market status.
- Present `asOf`, `ageSeconds`, `stale`, and `delayMode` where relevant to the decision.
- Label African equity prices “15-minute delayed,” never “live” or “real time.”
- Apply required MyStocks and exchange attribution without obscuring it.
- Stop or degrade display when entitlement expires, data becomes stale, or the provider withdraws rights.
- Keep state-change webhooks/SSE distinct from price streaming; event delivery is not a tick feed.

## Storage and downstream controls

1. Limit cache and historical retention to the executed licence.
2. Prevent bulk extraction with authentication, rate limits, export limits, and anomaly detection.
3. Flow restrictions to analytics, observability, support tools, subprocessors, and backups.
4. Maintain lineage from provider and exchange through transformed fields to customer display.
5. Delete or quarantine data when rights end, subject to lawful record-retention requirements.
6. Preserve usage logs needed for exchange/vendor audits without collecting unnecessary personal data.

## Change workflow

<FlowDiagram
  nodes={[
    { label: 'Product request', sublabel: 'market · audience · use' },
    { label: 'Rights review', sublabel: 'contract + exchange policy' },
    { label: 'Technical controls', sublabel: 'entitlement · cache · attribution', tone: 'accent' },
    { label: 'Approval', sublabel: 'legal + data owner' },
    { label: 'Monitor', sublabel: 'usage + expiry + audit', tone: 'success' },
  ]}
/>

## Production evidence

- Executed market-data schedule and exchange/provider rights matrix.
- Screenshots or design evidence showing delay and attribution treatment.
- Cache, export, download, and API-access controls.
- Vendor/subprocessor list and contractual flow-downs.
- Usage reporting, audit response, expiry, and takedown procedure.

See [Data licensing](/partners/docs/data-licensing) and
[Market-data quotes](/partners/docs/market-data-quotes) for the current API behaviour.