Buyer request brief: describe the data without naming a buyer

Copy this template into an internal document. Replace the bracketed text. Do not put a private archive, customer record, secret, or health record into this template.

1. Data family

• [Describe the family in plain language. If the request concerns health data, stop at research and status. Do not use this template as health intake.]

2. Intended use and environment

• [Describe the product or research context at a high level.]
• [State whether the use is internal, customer-facing, evaluation, or another reviewed purpose.]

Intended use helps scope a review. It is not permission to use the data. The final license and applicable review decide what is allowed.

3. Specification

• Languages: [language or unknown]
• Domains or subjects: [scope or unknown]
• Formats: [format or unknown]
• History depth: [period or unknown]
• Labels or metadata: [description or none known]
• Filters and exclusions: [description]

4. Volume and unit

• Requested volume: [amount or unknown]
• Unit: [record, conversation, file, token, hour, or other]
• Minimum useful sample: [amount or unknown]

Use unknown rather than an unsupported estimate. A number is useful only when its unit and source are clear.

5. License and term

• License shape: [non-exclusive, exclusive, or needs review]
• Term: [requested term or needs review]
• Deletion or return requirement: [requested requirement or needs review]
• Delivery cadence: [one-time, batch, or needs review]

The current Rightmark buyer workflow treats scope, use, term, exclusivity, delivery, and deletion as written deal terms. This worksheet records a request for review. It is not an agreed license.

General information, not legal advice.

6. Evaluation and security

• Sample format: [redacted sample, schema, or no sample requested]
• Security requirements: [encryption, access, residency, retention, or needs review]
• DPA or deletion requirements: [description or needs review]
• Review contact role: [role, not a private person’s details]

After a request is received, a response can state what is known about source systems, scope, formats, timing, and evidence. It can propose a written scope by email. The current buyer process describes evaluation reports and scrubbed samples under a confidentiality agreement, followed by written use and delivery terms, owner-system batches, and deletion certification where agreed.

General information, not legal advice.

Do not turn this into a promise. The response should separate known, needs evidence, and not available for this request.

• A buyer name, private company detail, or unverified relationship.
• Customer records, employee records, direct messages, privileged material, credentials, or a private archive.
• A price, availability statement, demand statement, or claim that a source is exclusive.
• Health records or a health intake. Health-related requests remain research and status only.

Rightmark does not take health data yet (patient records, medical imaging or veterinary records), until a HIPAA program and vendor agreements are in place.