Data ownership and independent use

Our accepted direction requires customer data to remain independently useful. That includes values, scientific meaning and permitted derivation history.

A practical exit test

1. Export permitted data with metadata, exact revision references and lineage.
2. Verify the package and its recorded hashes.
3. Read it with ordinary independent tooling.
4. Inspect units, nulls and coordinate claims.
5. Reproduce a selected transformation from its recorded inputs.

Local experiments establish part of this path. General customer-configured bucket export and its UI remain planned.

Revoking API access stops future authorized reads and publication. It cannot recall copies already downloaded.

AI training rights require explicit permission. Data access alone does not supply those rights.

Own the scientific history

Usable ownership includes permitted interpretations, labels and exact derivation records. Our own applications and domain APIs can capture operations explicitly so customers can inspect and reproduce how a result was made. An independent exit should retain that meaning and history alongside the values.

Data ownership overview · Lineage and AI · Customer telemetry controls.