Marketplace Data Processing Terms
Effective August 28, 2026 · Private beta draft — subject to counsel review before general availability.
1. Scope
These terms cover data transmitted between marketplace buyers and sellers: authorized input fields (buyer → seller) and delivered results (seller → buyer). They complement each service's machine-readable Data Use Contract, which is the operative declaration for retention, training, human review, sharing, and PII/confidential acceptance.
2. Only authorized fields travel
The gateway transmits only the fields the service contract declares. Credential and secret-classed content is never transmittable. Data classification caps configured in buyer policy are enforced deterministically before payment.
3. Seller processing obligations
Sellers must process buyer data strictly per their declared contract: honor retention windows and deletion behavior, never train on data when training is declared prohibited, never share with undeclared subprocessors, and report incidents promptly.
4. Telemetry and evidence
Security telemetry records pattern classes and counts only — never payload content, never secret values. Commerce session evidence preserves contract versions, schemas and decisions for dispute resolution without retaining sensitive content unnecessarily.
5. Jurisdiction
Actual data-protection obligations depend on the jurisdictions and business relationships involved. These terms will be finalized with qualified counsel; cross-border processing terms and formal DPAs are pending that review.
Questions? Reach the platform operator through your dashboard. See also: Terms of Service · Privacy Policy · Acceptable Use Policy · Marketplace & Seller Terms · API & Developer Terms · Marketplace Buyer Terms · Marketplace Seller Agreement · Marketplace Acceptable Use Policy
