Buyer standards
Questions we ask every buyer, in writing
Before we recommend a buyer, we ask for written answers to the questions below. If a buyer won't let the seller approve every sample before it is released, we recommend the seller doesn't proceed.
| Topic | What we ask | Reviewer |
|---|---|---|
| 1. Exact dataset | Which systems, data types, date range, volume, and what's included and excluded? Will a written manifest be the only scope? Who drafts it and who approves changes? | Legal + technical |
| 2. Ownership vs license | Who owns the original, the prepared copy and anything derived from it? Is the license perpetual or for a term? Can it be sublicensed, and how far? | Legal |
| 3. Exclusivity | Is any part exclusive? For how long, for which data and uses? What future licensing would it block? | Legal |
| 4. Payment | The exact trigger events and dates: delivery, review window, acceptance, invoice, payment. Instalments, holdbacks or refunds? Who is the contracting party, the end developer or an intermediary? Will the end buyer be named, or only its type? Every deduction listed in writing. | Legal |
| 5. Payment safety | Are new or changed bank details confirmed by a call-back to a number verified earlier, never by email alone? | Legal + seller |
| 6. Personal and sensitive data | What must be excluded? Who de-identifies, by what method, and who sees raw data? Who holds any re-link key? Who bears leftover risk? What are the retention and deletion terms? | Legal + technical |
| 7. Sample approval | Will the seller approve every sample in writing (contents, recipients, purpose) before it's released, with no onward sharing without new approval? | Legal |
| 8. Referral fees | Is any referral fee paid to Legacy Signal? Is it paid from the buyer's side, without reducing the seller's payment? Does it create any exclusivity for the seller? | Legal |
A "no" or "unknown" on sample approval, exclusivity, payment or personal data means hold: nothing is released until it's answered in writing.