# Data processing agreement document profile

The **Data processing agreement** profile helps you track stated processing roles and scope. It belongs to the contracts family.

## Recognize the source

Processing obligations and roles; do not infer compliance from the document or require jurisdiction-specific clauses globally.

Review the document itself before applying the profile. Similar labels, dates, parties, or amounts can appear in another document type with a different meaning. Use the source context to distinguish them.

## Expected fields

Core fields form the profile’s main structure. Recommended and optional fields add supported detail. None of these designations permits guessing a value that is absent or ambiguous.

| Field | Type | Inclusion | Meaning and extraction rule |
| --- | --- | --- | --- |
| Controller | text | Core | The source-stated controller for this document and its identified subject. Copy exact source spans for this one scalar field, preserving their order, ownership and qualifications. Ordered spans may continue across segments. Do not synthesize a summary or combine unrelated fields or repeated records; return unresolved when the scalar meaning is ambiguous. |
| Processor | text | Core | The source-stated processor for this document and its identified subject. Copy exact source spans for this one scalar field, preserving their order, ownership and qualifications. Ordered spans may continue across segments. Do not synthesize a summary or combine unrelated fields or repeated records; return unresolved when the scalar meaning is ambiguous. |
| Processing purpose | text | Core | The source-stated processing purpose for this document and its identified subject. Copy exact source spans for this one scalar field, preserving their order, ownership and qualifications. Ordered spans may continue across segments. Do not synthesize a summary or combine unrelated fields or repeated records; return unresolved when the scalar meaning is ambiguous. |
| Data categories | text | Core | The source-stated data categories for this document and its identified subject. Copy exact source spans for this one scalar field, preserving their order, ownership and qualifications. Ordered spans may continue across segments. Do not synthesize a summary or combine unrelated fields or repeated records; return unresolved when the scalar meaning is ambiguous. |
| Processing duration | text | Core | The source-stated processing duration for this document and its identified subject. Copy exact source spans for this one scalar field, preserving their order, ownership and qualifications. Ordered spans may continue across segments. Do not synthesize a summary or combine unrelated fields or repeated records; return unresolved when the scalar meaning is ambiguous. |
| Subprocessor terms | text | Optional | The source-stated subprocessor terms for this document and its identified subject. Copy exact source spans for this one scalar field, preserving their order, ownership and qualifications. Ordered spans may continue across segments. Do not synthesize a summary or combine unrelated fields or repeated records; return unresolved when the scalar meaning is ambiguous. |
| Transfer terms | text | Optional | The source-stated transfer terms for this document and its identified subject. Copy exact source spans for this one scalar field, preserving their order, ownership and qualifications. Ordered spans may continue across segments. Do not synthesize a summary or combine unrelated fields or repeated records; return unresolved when the scalar meaning is ambiguous. |
| Deletion terms | text | Optional | The source-stated deletion terms for this document and its identified subject. Copy exact source spans for this one scalar field, preserving their order, ownership and qualifications. Ordered spans may continue across segments. Do not synthesize a summary or combine unrelated fields or repeated records; return unresolved when the scalar meaning is ambiguous. |

## Missing, ambiguous, and repeated values

Missing or ambiguous fields remain null with a reason. Null is not zero, false, an empty statement, or proof that a document-wide fact does not exist. Inspect unresolved states and their supporting passages before accepting the table.
This document type can contain repeated records such as **processing activities and subprocessors**. The profile uses one row per document; do not compress repeated records into a scalar field or confuse a line value with a document-level total.
Additional supported fields can be considered when the extraction experience allows them. Review their definitions and types explicitly; changing a field’s meaning requires a new extraction preview.

## Review the result

Select evidence-backed cells and read the retained source. Text should preserve the relevant source spans and qualifications. Numbers and dates must be stated unambiguously and normalized safely; do not calculate unstated values or infer missing units, currency, scale, date parts, or time zones.

Verify the result against the captured document before acceptance. Source support does not independently establish perfect OCR, exhaustive field discovery, or correct domain interpretation.

See [profile modes](/docs/documents/profiles), [table review](/docs/tables/review-and-accept), and [captured evidence](/docs/documents/citations-and-evidence).