> ## Documentation Index
> Fetch the complete documentation index at: https://docs.datavendor.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# General FAQ

> What DataVendor is, how it makes money, and how it protects both sides.

Questions about one side of the marketplace live with that side: the [Selling FAQ](/sell/faq) and
the [Buying FAQ](/buy/faq). Exact fees and limits are on [Fees and limits](/sell/fees-and-limits)
for vendors and [Fees and payment](/buy/fees-and-payment) for buyers.

## About DataVendor

<AccordionGroup>
  <Accordion title="What is DataVendor?">
    A marketplace where teams license private data, code, and task data to AI companies that need
    training and evaluation supply. Vendors list what they hold; buyers buy it or request what is
    missing. See [How DataVendor works](/overview/how-it-works).
  </Accordion>

  <Accordion title="Who should sell on DataVendor?">
    Teams that hold private codebases, tasksets, evals, or RL environments, or raw material such as
    enterprise documents and records. Domain expertise counts once it is captured as tasks or data
    you can list. See [What you can sell](/sell/what-you-can-sell).
  </Accordion>

  <Accordion title="How do I get started?">
    Sign up at [datavendor.ai](https://datavendor.ai) and choose a side in organization setup.
    Vendor setup is self-serve: see [Become a vendor](/sell/become-a-vendor). Buyer access is
    invite-only through a waitlist: see [Become a buyer](/buy/become-a-buyer).
  </Accordion>
</AccordionGroup>

## Money and trust

<AccordionGroup>
  <Accordion title="How does DataVendor make money on a sale?">
    DataVendor keeps 20% of vendor earnings, assessed only when earnings are withdrawn; converting
    earnings to [credits](/overview/glossary#credits) is fee-free. Buyers pay a separate
    transaction fee at checkout, shown before payment.
  </Accordion>

  <Accordion title="Who can see who on a sale?">
    Buyers see the vendor organization on every listing. Vendors never see the buyer: bids, sale
    records, and notifications carry no buyer identity, and delivery copies tasksets and
    environments into the buyer's team rather than sharing them from the vendor's. This applies to
    purchases, [bids](/overview/glossary#bid), and [samples](/overview/glossary#sample) alike.
    Opportunities are different; see
    [How DataVendor works](/overview/how-it-works#buyers-stay-anonymous).
  </Accordion>

  <Accordion title="Do I keep ownership of my data or code?">
    Yes, by default. A sale licenses your assets for a commercial use rather than transferring
    them; the exact rights depend on the agreement behind the listing. When you submit a listing,
    you confirm that you own the supply and have the right to license it, so only list what is
    yours to license.
  </Accordion>

  <Accordion title="Why does DataVendor ask for an NDA?">
    Both sides may share sensitive information: your data or code, buyer requirements, and
    commercial terms. The [Mutual NDA](/overview/glossary#nda) protects that information and
    clarifies what can and cannot be shared.
  </Accordion>

  <Accordion title="Can DataVendor pause transactions during the beta?">
    Yes. While the marketplace is in beta, purchases, invoicing, and payouts sit behind operational
    switches that DataVendor can pause temporarily, for example during an incident or a payments
    review. Anything already paid stays paid, entitlements remain, and approved withdrawals resume
    when the switch re-enables.
  </Accordion>

  <Accordion title="What happens if a payment is disputed? Are there refunds?">
    All sales are final; there is no refund flow on either side. If a buyer's bank reverses a
    charge anyway, the buyer's access is removed and the sale amount is clawed back from the
    vendor's wallet; a lost dispute additionally passes through a \$15 dispute fee to the vendor.
  </Accordion>
</AccordionGroup>

## Still have questions?

[Book a call with the DataVendor team](https://cal.com/team/hud/talk-to-us-data-vendor-platform) to
talk through your supply, buyer needs, or marketplace fit. Signed-in teams can also send feedback
from the app sidebar.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.