Zero Data Retention (ZDR) Inference Services
Schedule to the Doubleword Terms of Service
This Data Processing Agreement ("DPA") forms part of, and is entered into under, Doubleword's Terms of Service, and incorporates Doubleword's Data Usage Policy and Privacy Policy (together, the "Agreement"). It governs the Processing of Personal Data by Doubleword in connection with the ZDR-enabled Services. To the extent of any conflict regarding the Processing of Personal Data — including retention — this DPA prevails over the Agreement.
No training on your data. Doubleword does not use your Service Content to train or improve models unless you expressly opt in.
You control your data. Access, download or delete your data at any time through the Services.
Zero Data Retention on realtime and async endpoints. Request and response content is processed only to serve the request and is not retained as durable product data. Batch endpoints are not ZDR-eligible and are not covered by this DPA.
(1) TYTN Ltd, trading as "Doubleword", a company registered in England and Wales under company number 13353288 whose registered office is at 73 Cornhill, London EC3V 3QQ ("Doubleword", the "Processor"); and
(2) The customer identified in the Agreement, being the business that accepts the Terms of Service and enables ZDR (the "Customer", the "Controller"), each a "party" and together the "parties".
(a) This DPA is published at https://doubleword.ai/zdr-dpa/ and is incorporated by reference into Doubleword's Terms of Service. It applies to any Customer that enables Zero Data Retention in the Services, whether ZDR is enabled by the Customer or by Doubleword Support at the Customer's request. By enabling ZDR, or by continuing to use the Services while ZDR is enabled, the Customer agrees to this DPA. No signature is required.
(b) This DPA applies only to the Processing of Personal Data in connection with ZDR-enabled Services, and to Operational Metadata relating to them. It does not apply to Service Content submitted through batch endpoints, or through any other mode for which ZDR is not enabled. The Customer must not submit Personal Data through any such mode unless it has first entered into a separate data processing agreement with Doubleword (available by contacting [email protected]).
(c) Where the parties have signed a separate data processing agreement, that agreement prevails over this DPA to the extent of any conflict and only for its scope.
Capitalised terms not defined here have the meaning given in the Agreement or in Data Protection Law.
| Term | Meaning |
|---|---|
| Data Protection Law | The UK GDPR and the Data Protection Act 2018; the EU GDPR (Regulation (EU) 2016/679); and, where applicable, the California Consumer Privacy Act as amended by the California Privacy Rights Act (the "CCPA/CPRA"); in each case together with binding guidance and any successor legislation. |
| Personal Data, Processing, Controller, Processor, Data Subject, Personal Data Breach | As defined in the UK/EU GDPR; and, for CCPA/CPRA, "Personal Data" includes "personal information", "Controller" maps to "business" and "Processor" to "service provider". |
| Service Content | Prompts, inputs, files and other content submitted to the Services, and the outputs generated in response, including tool-call payloads and streamed response chunks. "Service Content" has the meaning given in Doubleword's Data Usage Policy. |
| Operational Metadata | Metadata generated in the course of providing the Services that does not comprise Service Content — for example account and API-key identifiers, timestamps, token counts, routing and model identifiers, latency and error metrics, and billing and abuse-prevention records. This is distinct from "Usage Data", which the Data Usage Policy defines as aggregated or de-identified data. |
| ZDR / Zero Data Retention | The mode of the Services in which Service Content is Processed only to serve the request and is not retained as durable product data after the Permitted Processing Window, as further described in Annex 4. |
| ZDR-Compatible Provider | A Sub-processor contractually bound to no-retention commitments equivalent to Clause 3 and Annex 4, with request logging disabled or suppressed for ZDR traffic. |
| Permitted Processing Window | The minimal period during which Service Content necessarily exists in transient processing state in order to dispatch the request and return the response, after which it is not persisted to any durable store. Transient in-memory caching (including prompt and key-value caching) that exists only in volatile memory falls within this window and does not constitute retention. The window is bounded as described in Annex 4 for each eligible mode. |
| Sub-processor | Any third party engaged by Doubleword to Process Personal Data on its behalf in connection with the Services. |
| SCCs | The Standard Contractual Clauses approved by the European Commission (Decision 2021/914). |
| UK Addendum | The International Data Transfer Addendum to the SCCs issued by the UK Information Commissioner under s.119A DPA 2018. |
1. The Customer is the Controller and Doubleword is the Processor in respect of the Personal Data described in Annex 1. Where the Customer is itself a processor acting for a third-party controller, Doubleword acts as a sub-processor and this DPA applies mutatis mutandis.
2. Doubleword shall Process Personal Data only: (a) to provide the Services in accordance with the Agreement; (b) on the documented instructions of the Customer, of which this DPA and the Customer's configuration of the Services (including ZDR settings) form part; and (c) as required by applicable law, in which case Doubleword shall, where lawful, inform the Customer of that requirement before Processing.
3. The subject-matter, duration, nature and purpose of the Processing, the types of Personal Data and the categories of Data Subjects are set out in Annex 1.
4. Doubleword shall immediately inform the Customer if, in its opinion, an instruction infringes Data Protection Law.
5. Doubleword shall not use Service Content to train, fine-tune or otherwise improve any model except to the extent the Customer expressly opts in.
6. ZDR is available for realtime and asynchronous ("async/flex") inference only. Batch inference is not ZDR-eligible, is not covered by this DPA and is Processed under Doubleword's standard retention terms; the Customer must not submit Personal Data through batch endpoints unless a separate data processing agreement is in place. The retention semantics and limitations for each mode are set out in Annex 4.
7. When ZDR is enabled for the applicable scope, Doubleword shall ensure that Service Content is not persisted to product data stores, request logs, debug logs, traces, error captures, or async state beyond the Permitted Processing Window, and that streamed response bodies are not buffered to durable storage.
8. In-memory caching is not retention. To reduce latency and cost, Doubleword and its ZDR-Compatible Providers may cache portions of Service Content (including prompt and key-value caches) solely in volatile memory for a short period. Such cached data is never written to durable storage, is confined to the Permitted Processing Window, and does not constitute retention of Service Content for the purposes of this DPA.
9. ZDR may be enabled: (a) by the Customer, by toggling ZDR for the applicable use case in the Services; (b) by Doubleword Support on behalf of the Customer, at the organisation level; or (c) as agreed in writing between the parties (including in an Order Form), for the scope so agreed. In each case, enabling ZDR constitutes the Customer's acceptance of this DPA. The current ZDR state is exposed to Customers via the UI and Doubleword support.
10. Operational Metadata is retained notwithstanding ZDR, solely for billing, routing, abuse prevention, reliability, latency and error metrics, and auditability. The specific metadata fields retained under ZDR are enumerated in Annex 4. Operational Metadata is minimised and does not include Service Content.
11. For Service Content Processed under ZDR, this DPA overrides the default retention described in Doubleword's Data Usage Policy. That default — including persistent storage of Service Content — applies only where ZDR is not enabled, subject to any separate data processing agreement between the parties.
12. Doubleword shall route ZDR traffic only to inference providers and models that honour equivalent no-retention guarantees. Doubleword shall not route ZDR traffic to any downstream provider whose retention behaviour would be inconsistent with this Clause 3.
13. Doubleword shall ensure that persons authorised to Process the Personal Data are bound by an appropriate duty of confidentiality and Process the Personal Data only on the Customer's instructions, save as required by law.
14. Taking into account the state of the art, the costs of implementation, and the nature, scope, context and purposes of Processing, Doubleword shall implement appropriate technical and organisational measures to ensure a level of security appropriate to the risk, including the measures described in Annex 2.
15. For ZDR-enabled Services, those measures include controls designed to prevent Service Content from being written to durable stores or exported telemetry, and testing designed to verify that prompts, completions, tool payloads, images and files, async payloads and streamed chunks do not land in persistent stores or exported telemetry.
16. Doubleword has completed a SOC 2 Type II examination covering the Security trust services criteria for the period 8 June 2026 to 8 September 2026, with an unqualified opinion issued by Prescient Assurance LLC on 23 October 2026. A copy of the report is available to the Customer on request, subject to confidentiality, in accordance with Clause 11.
17. The Customer grants Doubleword general written authorisation to engage Sub-processors. A current list of Sub-processors is set out at https://trust.doubleword.ai/?tab=subprocessors, as updated from time to time in accordance with Clause 18.
18. Doubleword shall give notice of any intended addition or replacement of a Sub-processor by updating the list at https://trust.doubleword.ai/?tab=subprocessors at least 7 days in advance. Doubleword has no obligation to notify the Customer individually. Where urgently required for service continuity, Doubleword may engage a ZDR-Compatible Provider immediately and give notice as soon as reasonably practicable afterwards. The Customer may object within the notice period on reasonable data-protection grounds; a Sub-processor that meets the ZDR-Compatible Provider criteria and Doubleword's published location and quality standards is presumed not to give rise to such grounds. If the parties cannot resolve a well-founded objection, the Customer may terminate the affected Services as its sole remedy.
19. Doubleword shall impose on each Sub-processor, by written contract, data-protection obligations no less protective than those in this DPA. Where a Sub-processor Processes ZDR traffic, those obligations shall include no-retention commitments equivalent to Clause 3 and Annex 4. Doubleword remains fully liable to the Customer for each Sub-processor's performance of its obligations.
20. Taking into account the nature of the Processing, Doubleword shall assist the Customer by appropriate technical and organisational measures, insofar as possible, in fulfilling the Customer's obligations to respond to requests to exercise Data Subject rights.
21. The parties acknowledge that, for ZDR-enabled Services, Service Content is not retained after the Permitted Processing Window. Accordingly, in respect of such Service Content, Doubleword's assistance consists principally in confirming that the content has not been retained, rather than in retrieving, exporting, rectifying or deleting stored copies, because no durable copy exists. Doubleword shall assist in relation to any Operational Metadata it does retain.
22. Doubleword shall notify the Customer without undue delay after becoming aware of a Personal Data Breach affecting the Customer's Personal Data, by email to the Customer's account administrator, and shall provide the Customer with information reasonably required to enable the Customer to meet its own notification obligations, which may be provided in phases as it becomes available. Unsuccessful attempts or activities that do not compromise the security of Personal Data, including pings, port scans, unsuccessful log-in attempts and other network attacks that do not result in unauthorised access to Customer Personal Data, are not Personal Data Breaches. Notification is not an acknowledgement of fault or liability.
23. Doubleword shall provide reasonable assistance to the Customer with any data protection impact assessment and prior consultation with a supervisory authority that the Customer is required to carry out, taking into account the nature of the Processing and the information available to Doubleword, and to the extent the Customer does not otherwise have access to the relevant information. Doubleword may satisfy this obligation primarily by making available this DPA, its trust centre materials and its then-current third-party audit reports. Any further assistance shall be at the Customer's cost at Doubleword's then-current rates.
24. On termination or expiry of the Services, Doubleword shall, at the Customer's choice, delete or return the Personal Data it Processes on the Customer's behalf under this DPA, and delete existing copies, unless retention is required by law.
25. The parties acknowledge that, for ZDR-enabled Services, Service Content is not retained beyond the Permitted Processing Window and therefore requires no separate return or deletion on termination. This Clause 10 applies to any Operational Metadata.
26. Doubleword shall make available to the Customer information reasonably necessary to demonstrate compliance with this DPA and, on reasonable prior notice and no more than once in any twelve-month period (save where required by a supervisory authority or following a Personal Data Breach), allow for and contribute to audits, including inspections, conducted by the Customer or an independent auditor mandated by it, subject to reasonable confidentiality and security conditions. Doubleword may satisfy audit requests by providing then-current third-party certifications or reports where these reasonably address the Customer's request.
27. The Customer authorises Doubleword to transfer Personal Data outside the UK and the EEA, provided an appropriate transfer mechanism is in place.
28. Where Personal Data originating in the EEA is transferred to a country without an adequacy decision, the SCCs are incorporated into this DPA and completed as set out in Annex 3 (Module Two: Controller-to-Processor, or Module Three: Processor-to-Processor, as applicable). Where Personal Data originating in the UK is so transferred, the UK Addendum applies to and amends the SCCs accordingly. Doubleword shall ensure that transfers of ZDR traffic are made only to recipients bound by no-retention commitments equivalent to Clause 3.
29. Data residency. Inference endpoints that are explicitly labelled as Europe-hosted are Processed entirely within Europe. Inference requests to endpoints that are not so labelled may be processed in any trusted region, and overflow routing via ZDR-Compatible Providers may reach providers in any region, in each case subject to the transfer mechanisms in this Clause 12.
This Clause 13 applies to the extent the Customer is a "business" and Doubleword a "service provider" under the CCPA/CPRA.
30. Doubleword shall Process personal information disclosed by the Customer solely to perform the Services (the "business purpose") specified in the Agreement, and shall not retain, use or disclose it for any other purpose, or outside the direct business relationship between the parties, except as permitted by the CCPA/CPRA.
31. Doubleword shall not "sell" or "share" the Customer's personal information as those terms are defined in the CCPA/CPRA, and shall not combine it with personal information received from other sources except as permitted by the CCPA/CPRA.
32. Doubleword certifies that it understands the restrictions in this Clause 13 and shall comply with them, and shall provide the same level of privacy protection required of a service provider under the CCPA/CPRA. The Customer may take reasonable and appropriate steps to remediate unauthorised use.
33. Each party's liability under or in connection with this DPA is subject to the limitations and exclusions of liability set out in the Agreement.
34. This DPA takes effect on the date the Customer first enables ZDR (or, if earlier, the date the parties agree to it in writing) and continues for so long as Doubleword Processes Personal Data on the Customer's behalf in connection with ZDR-enabled Services. Clauses that by their nature should survive termination shall do so.
35. This DPA is governed by the law and subject to the jurisdiction stated in the Agreement, save where Data Protection Law or an incorporated transfer mechanism requires otherwise.
36. Doubleword may update this DPA from time to time on at least 30 days' notice, provided that each update (a) is required by a change in Data Protection Law or binding guidance, or (b) does not materially reduce the protection of Personal Data. Notice may be given by email or by posting the updated DPA on Doubleword's website or trust centre. The Customer's continued use of the Services after the notice period constitutes acceptance of the updated DPA.
37. This DPA takes effect without signature. A countersigned copy is available on request from [email protected], but signature is not a condition of this DPA applying.
| Item | Detail |
|---|---|
| Subject-matter | Provision of ZDR-enabled hosted inference services (realtime and async) to the Customer under the Agreement. Batch inference is outside the scope of this DPA. |
| Duration | For the term of the Agreement and any ZDR-related processing window described in Annex 4. |
| Nature and purpose | Providing AI inference: processing requests and returning responses, plus billing, abuse prevention, and service reliability |
| Types of Personal Data | Any Personal Data the Customer chooses to include within Service Content submitted to ZDR-enabled Services, and Operational Metadata. |
| Categories of Data Subjects | Customer's end users, employees, and other individuals whose data appears in prompts / inputs |
| Special category data | The Customer must not submit highly sensitive personal data, including health data, financial account credentials, or government identification numbers, and must not submit personal data through any mode not covered by this DPA unless a separate data processing agreement is in place, consistent with the Terms of Service and Data Usage Policy. |
| Frequency | Continuous, on an on-demand basis, for the term of the Agreement. |
Doubleword maintains, at minimum, the following measures:
ZDR traffic is Processed only by ZDR-Compatible Providers. The current list of Sub-processors, including ZDR-Compatible Providers, is maintained at https://trust.doubleword.ai/?tab=subprocessors.
Transfer mechanism: for Sub-processors outside the UK/EEA without adequacy, the SCCs (with UK Addendum where relevant) apply as set out in Clause 12.
Compute location. Inference-compute providers (Prime Intellect, Lambda) and overflow routers may provision capacity in any trusted region; Prime Intellect in particular operates as a marketplace and the underlying datacenter varies per node. Only endpoints explicitly labelled as Europe-hosted are Processed entirely within Europe, as set out in Clause 12.
This Annex is the written statement of the exact retention semantics and limitations for each mode.
Across the ZDR-eligible modes above, Doubleword and its ZDR-Compatible Providers may cache portions of Service Content to reduce latency and cost. The following applies:
The following categories of Operational Metadata may be retained even in ZDR mode, and do not contain Service Content: