Being able to read a record does not settle what you may do with it. Your organizationThe Developer-side unit that holds Campaigns, data access, and funds's grant or subscription for that data does, so check it before each use: looking at it, testing it, reading it through the API, exporting, publishing, sharing, and transferring are separate permissions.
Check what you may do
- Name the organization, the data (its listing or dataset, and the version if one is shown), and what you want to do: look at it, read it through the API, export it, publish it, or give it to someone.
- Ask your organization's administrator for the grant or subscription record and the terms for that data and purpose.
- Compare the permitted uses, recipients, and restrictions with what you want to do.
An API Key lets a program read within its scope; it is not a license. A successful API response means that request was allowed, not that you may republish the data or pass it on.
If you cannot find the grant or its terms, send support the organization, the listing or asset title or ID (and version, if shown), what you want to do and for whom, and any subscription or agreement reference. Ask which terms and delivery method apply before you export or share anything. Do not send raw data or a complete API Key.
Licenses, exports, and ownership
The Marketplace does not offer snapshot licenses or ownership deals: the portal has no Snapshot & license or Ownership & royalty option, so you cannot export a copy, sign a license, or make an ownership offer there. Metered access and Subscription are not affected. For an export or a license, ask hello@humanbased.ai about the specific data, the agreement that applies, and the delivery method. Existing subscriptions can still be checked against their API responses and receipts.
Your contributions and shares
Acceptance, delivery, and dataset membership are recorded separately for each contribution, so check each in its own record. Joining a teamA relationship among Contributors that leaves each member's Submissions and Earnings their own does not automatically change who is credited or paid for your own work; if your team has its own cooperation or settlement arrangement, check that agreement for the named payee.
A dataset share is your portion of one version of a dataset, and it is distinct from the Contribution Fingerprint that identifies your source work. It is not your taskA specific item a contributor claims or enters reward, and you cannot work it out by counting your contributions: check that version's allocation record. A share does not let you download the raw data or sublicense it. The XnY protocol explanation describes how shares work; it does not mean Humanbased offers self-service claims or transfers. For what you have been paid, see Earnings.
Provenance does not grant use
Anchoring and lineage let you trace a record back to its source. They do not change what you may do with the data; its terms decide that. A task passing review does not promise continuing royalties: subsequent-use revenue and task rewards have separate grounds.