Vordex converts the controller-processor record into a traceable first pass: defined intake fields, visible fallback tests, a fixed clause sequence and a returned package that keeps warnings beside the draft.
The page describes the supplied deterministic DPA implementation. It does not claim role classification, live legal checking, security assurance, transfer approval or guaranteed compliance.
Processing Flow Diagram
The generation path is shown as a six-node system rather than a generic three-step marketing workflow. Each node identifies what enters, what the supplied implementation does and what it emits next.
Controller, processor, service, processing schedule, controls, vendor-chain, transfer, incident, audit and special-term answers.
The entrypoint accepts the submitted answer payload together with jurisdiction, perspective and selected plan context.
Alternative labels such as customer, provider, data_categories, security and international_transfers.
The extractor chooses the first usable value for each of 13 canonical DPA fields and inserts a disclosed fallback where no usable value exists.
Controller, Processor or Neutral perspective plus England and Wales, Scotland, Northern Ireland or broad UK wording.
Perspective is stored in prompt context. Jurisdiction selects the final governing-law wording or remains explicitly unresolved.
The normalised values and the exact fallback strings used by the playbook.
Eleven top-level warning conditions are evaluated. Section-level fallback tests are then used to set draft or needs_input.
The normalised fields, standard playbook wording and selected legal system.
The current deterministic builder produces the same 15-section architecture on every run and inserts the supplied values into their defined destinations.
Sections, warnings, run context, original answers and generator metadata.
Vordex returns structured content and a plain-text rendering together, keeping the completion evidence beside the draft.
Controller vs Processor Builder
Choose a perspective to inspect the stored context and practical priorities. The component makes the implementation boundary explicit: perspective is recorded, while the deterministic clause bodies remain on the same 15-section track.
Use this context when the customer determines the purpose and essential means of the processing and is commissioning a processor.
The stored prompt note emphasises documented instructions, sub-processing control, security, transfers, incident support and end-of-processing control.
Data Mapping
Every row joins the accepted data labels to the exact fallback, the supported warning or state behaviour and the section that receives the value. This is the generator's real data boundary, not a broad UK GDPR checklist.
controllerNamecontroller_namecontrollercustomerthe ControllerWarning or state effectTop-level warning and Parties needs_input while the fallback label remains.
01 · Parties
processorNameprocessor_nameprocessorproviderthe ProcessorWarning or state effectTop-level warning and Parties needs_input while the fallback label remains.
01 · Parties
servicesserviceDescriptionservice_descriptionthe services described in the main agreementWarning or state effectNo separate top-level warning; Roles and Services becomes needs_input when the fallback remains.
02 · Roles and Services
processingSubjectMatterprocessing_subject_mattersubjectMattersubject_matterthe processing subject matter described in the service descriptionWarning or state effectNo separate top-level warning; Subject Matter becomes needs_input when the fallback remains.
03 · Subject Matter
personalDataCategoriespersonal_data_categoriesdataCategoriesdata_categoriespersonal data categories to be confirmedWarning or state effectTop-level warning and Data Categories and Data Subjects needs_input.
06 · Data Categories and Data Subjects
dataSubjectsdata_subjectsdata subjects to be confirmedWarning or state effectTop-level warning and Data Categories and Data Subjects needs_input.
06 · Data Categories and Data Subjects
durationtermprocessingDurationprocessing_durationthe duration of the processing stated in the main agreementWarning or state effectTop-level warning and Duration needs_input.
04 · Duration
securityMeasuressecurity_measuressecurityappropriate technical and organisational measures to be confirmedWarning or state effectTop-level warning and Security needs_input.
07 · Security
subProcessorssub_processorssubprocessorssub-processor arrangements to be confirmedWarning or state effectTop-level warning and Sub-processors needs_input.
08 · Sub-processors
transfersinternationalTransfersinternational_transfersinternational transfer arrangements to be confirmedWarning or state effectTop-level warning and International Transfers needs_input.
09 · International Transfers
breachNoticebreach_noticeincidentNoticeincident_noticebreach notification timing to be confirmedWarning or state effectTop-level warning and Breach Notice needs_input.
10 · Breach Notice
auditauditRightsaudit_rightsaudit assistance arrangements to be confirmedWarning or state effectTop-level warning and Audits needs_input.
12 · Audits
specialTermsspecial_termsadditionalTermsadditional_termsnone statedWarning or state effectNo top-level warning; Special Terms becomes needs_input while none stated remains.
14 · Special Terms
Clause Generation
The first half shows the exact section manifest. The legal trace registry then maps every authority mentioned on this page to the supported input, completion trigger, returned output and explicit non-check.
RELATIONSHIPThe opening lane links the commercial service to the controller-processor arrangement without deciding whether the labels are legally correct in practice.
Built from: Controller and processor names
Built from: Service description
Built from: Processing subject matter
Built from: Processing duration
INSTRUCTIONSThis lane combines standard playbook wording with the data schedule supplied through the intake.
Built from: Standard playbook wording
Built from: Categories and subject groups
Built from: Security measures
OPERATIONSOperational answers are preserved as drafting positions. The builder does not validate the underlying supplier list, transfer mechanism or incident process.
Built from: Sub-processor arrangements
Built from: Transfer arrangements
Built from: Incident notice timing
Built from: Standard playbook wording
Built from: Audit arrangements
EXITThe final lane covers return or deletion, exceptional instructions and the selected UK governing-law wording.
Built from: Standard playbook wording
Built from: Additional instructions
Built from: Normalised jurisdiction
Every legal reference used by the page is attached to a confirmed generator behaviour. A reference explains the drafting context; it does not imply that Vordex fetches the source or performs the excluded checks during generation.
Services, processing subject matter, duration, personal data categories and data subject groups supplied in the intake.
Duration, data categories and data subjects can create top-level warnings. Services and subject matter instead affect their section states.
Roles and Services, Subject Matter, Duration, and Data Categories and Data Subjects sections, with warning and needs_input evidence where defined.
No legal classification of the relationship, no verification of nature or purpose, and no confirmation that the schedule is complete for the real processing.
No dedicated instruction field. The builder uses disclosed standard wording for the instruction clause.
No top-level warning and no input-dependent fallback test for Controller Instructions.
Controller Instructions is always returned with draft state in the current section builder.
Vordex does not inspect operational instruction channels, decide whether an instruction is lawful or detect processing outside instructions.
The technical and organisational measures text entered as securityMeasures.
The unconfirmed security fallback creates a top-level warning and sets Security to needs_input.
Security section plus the matching completion signal in the warning list and section state.
No control test, certification check, security evidence review, risk assessment or conclusion that the measures are appropriate.
The supplied sub-processor arrangement or vendor-chain position.
An unconfirmed sub-processor position creates a top-level warning and a needs_input state.
Sub-processors section carrying the stated arrangement and the unresolved-input signal where applicable.
No vendor discovery, authorisation audit, list comparison or inspection of the processor-to-sub-processor contract.
No dedicated assistance field in the 13-field extractor; standard playbook wording supplies the clause.
No top-level warning and no needs_input fallback for the Assistance section.
Assistance is always returned as draft within the 15-section sequence.
No data-subject request workflow review, DPIA assessment, regulator-consultation check or proof that the processor can provide the promised help.
The breach or incident notification timing supplied through breachNotice.
The unconfirmed timing fallback creates a top-level warning and sets Breach Notice to needs_input.
Breach Notice section plus the related warning and state in the generation package.
No incident classification, no live breach assessment and no decision about the controller's separate 72-hour reporting obligation.
The audit assistance or audit-rights position entered in the intake.
The unconfirmed audit fallback creates a top-level warning and sets Audits to needs_input.
Audits section and its completion signal in the returned warnings and section state.
No inspection of certifications, reports, evidence rooms, audit frequency, cost allocation or practical access rights.
No dedicated deletion field. Standard playbook wording supplies the current clause.
No top-level warning and no input-dependent fallback for Deletion or Return.
Deletion or Return is always returned with draft state.
No retention schedule, backup-deletion analysis, legal-hold check, deletion certificate or confirmation that return is technically possible.
The international transfer arrangement described in the transfers field.
An unconfirmed transfer position creates a top-level warning and sets International Transfers to needs_input.
International Transfers section recording the stated position and indicating that an appropriate mechanism may be required.
No restricted-transfer identification, adequacy analysis, IDTA, UK Addendum, transfer risk assessment or supplementary-measures review is generated.
Compliance Limits
These limits are part of the product specification. They separate a supported drafting action from role analysis, operational verification, live regulatory checking and connected documents that the current generator does not produce.
A visible limit is more useful than a broad compliance promise the implementation cannot support.
The generator records a controller and processor name and can store Controller, Processor or Neutral drafting perspective.
It does not determine who decides the purposes and essential means for each activity, identify joint controllership or classify mixed roles.
Resolve the real data-role analysis before relying on the draft architecture.
The current playbook is built around a controller instructing a processor.
Independent controllers and joint controllers need different allocation, transparency and lawful-basis work.
Use the document type that matches the actual relationship.
The builder uses the disclosed field map, fallback tests and fixed section sequence.
It does not fetch legislation, ICO guidance or transfer updates during an individual run.
Treat official links as external verification points for current requirements.
The securityMeasures answer feeds section 07 and can produce a warning when unresolved.
The generator does not test controls, inspect certificates, compare the measures with the risk or validate supplier evidence.
Attach or review the real security schedule and evidence separately.
The transfers answer is preserved in the International Transfers section and unresolved wording is surfaced.
The playbook does not produce an IDTA, UK Addendum, TRA or a finding that a safeguard is valid.
Complete the separate transfer work where a restricted transfer exists.
Controller Instructions, Assistance and Deletion or Return are always returned as draft using standard playbook wording.
No workflow, staffing, tooling, retention or incident evidence is examined before those sections receive draft state.
Verify that the organisation can perform the obligations written into the agreement.
Additional instructions are carried into a dedicated Special Terms section and can be marked needs_input.
The deterministic builder does not convert every exceptional instruction into a bespoke set of linked clauses.
Review unusual liability, sector, public-sector, AI, biometric or children's-data requirements separately.
Fallbacks and warnings expose missing supported answers.
Vordex does not confirm that names, categories, security measures, vendor lists, transfer descriptions or timings are accurate.
Validate the processing record against the real service and data flows before signature.
Generation Output
The return package is designed to remain inspectable. Structured sections, warning metadata, context, original answers and plain text are kept together so the first pass can be traced back to the supplied processing record.
content.schemaVersionThe structured content identifies the generator contract schema used by the returned draft.
content.playbookThe response records that the dpa playbook produced the section set.
content.sections[]Each section carries its identifier, heading, body, category and draft or needs_input state.
metadata.warningsThe package preserves the supported missing-input messages calculated before section assembly.
jurisdiction + perspectiveThe selected legal system and drafting perspective remain visible beside the generated content.
promptContextPlan, contract type, perspective, jurisdiction and selected answers are retained as generation context.
answersThe raw answer object remains attached so the first pass can be traced back to the submitted inputs.
plainTextThe title, headings and section bodies are joined into a portable plain-text representation.
Pricing
Both actions preserve the DPA contract type, this source page and generation intent. The selected plan key is stored for the next step without inventing a different clause inventory or legal-check engine that the supplied implementation does not expose.
Open the lower-priced generation route for a new deterministic Data Processing Agreement first pass.
Use the page's primary route and carry the Full plan key into the same disclosed DPA generation journey.
FAQ
The answers describe the supported field model, warning behaviour, clause assembly, legal-reference mapping, output package and route wiring without claiming live compliance analysis or capabilities that are not confirmed.
Generate when the controller-processor model and core processing facts are understood. Review every warning and needs_input section, then verify the operational, transfer and role questions that sit outside the deterministic builder.