Source material is used to compute market-state context, proof windows, normalized public rows, freshness, and replay references.
Data rights and source boundary
The packet is the product; raw feeds are not resold by default.
Etna Alpha publishes derived market-state packets, normalized customer-safe rows, replay handles, proof context, usage receipts, and status metadata. This policy describes the boundary reviewers should use when evaluating source rights, public API access, and Enterprise data delivery.
Customers receive market_state.v1 packets with state,
tags, reasons, confidence, evidence, replay context, routes, and
usage context.
API access does not by itself grant resale, republication, sublicensing, redistribution, or external exposure of raw datasets.
Private runtime outcomes, Decision V1 internals, selected-signal learning features, customer secrets, and raw keys stay outside the public product.
What customers may use
API plans are for organization-owned internal use of derived market-state packets, Workbench evidence, replay context, normalized public rows, workflow receipts, feedback routes, usage, and customer-safe status. Enterprise agreements may define broader data delivery rights in writing.
What requires written review
- Public redistribution of packet outputs or normalized public rows outside the customer organization.
- Bulk historical exports, external resale, sublicensing, or republication.
- Use cases that require raw source payloads, venue-feed equivalence, or source-specific onward distribution rights.
- Enterprise embedding where Etna Alpha output becomes part of another commercial data product.
Source-change and takedown handling
If a source, venue, partner, or customer flags a rights issue, Etna Alpha can narrow route exposure, remove affected public examples, disable export paths, or move an account to written Enterprise review while the issue is resolved. Reports should go to sales@etnaalpha.io.