Outway · Policies
Data Processing Agreement — Draft
A business processing framework for review, with deployment and contracting details to be completed before agreement.
Last updated: 10 October 2026
Status of this document
This is a draft for business review, not an executed Data Processing Agreement. Outway’s contracting identity, address, applicable jurisdiction, deployment details and provider schedule must be completed before this document can serve as a binding agreement. Contact [email protected] to arrange this. Do not treat publication as a signed agreement or a certification of compliance.
Proposed processing scope
The customer would act as controller, or as a processor authorized by its controller; Outway would act as processor or subprocessor for personal data processed on the customer’s instructions. Account administration and our own legal obligations are addressed separately in the Privacy Policy.
The proposed subject matter is collection, storage, extraction, reporting, monitoring and deletion of customer-requested web and connected-source data. Duration would follow the service agreement and the agreed return/deletion period. Data can include contact details and other personal information present in submitted or collected content; data subjects can include customer personnel and people identified in that content. Special-category data is outside the proposed ordinary service scope unless separately assessed and agreed.
Instructions, confidentiality and security
The agreement should bind processing to documented lawful instructions, including authorized service settings and API requests. Outway would notify the customer if an instruction appears to breach applicable data-protection law. People with authorized access would be subject to confidentiality obligations.
A completed security schedule should identify access controls, credential protection, encrypted transport, segregation, logging, backup arrangements, incident response and deletion procedures actually in place. Testing individual controls does not establish that every production control has been audited.
Assistance and incidents
The proposed agreement would require assistance, taking account of the processing and information available, with data-subject requests, security obligations, impact assessments and regulatory consultation. Outway would notify the customer without undue delay after becoming aware of a personal-data breach affecting customer data, provide available relevant information and cooperate with containment and remediation. Contact and escalation procedures must be agreed.
Subprocessors and transfers
The final schedule must name authorized subprocessors, functions and processing locations, provide an agreed process for notice and objection to changes, and require equivalent data-protection obligations. Outway would remain responsible for its subprocessors’ performance of those obligations. Any required international-transfer mechanism must be agreed and documented; none is created simply by this webpage.
Return, deletion and accountability
On termination, the customer would choose return or deletion of covered personal data, subject to applicable retention law. The final agreement must specify the operational period, backup lifecycle, exceptions and deletion evidence. It should provide information reasonably necessary to demonstrate compliance and an appropriate audit process without exposing other customers’ data or compromising security.
Details still to agree
Before execution, complete the parties and authorized signatories, processing instructions and data categories, applicable law, security and provider schedules, transfer terms, retention/deletion periods, audit arrangements and notification contacts. The providers page is a starting inventory, not a substitute for those agreed schedules.