Skip to policy
TAPTrusted Agreement Platform
Back to TAP
  1. TAP home
  2. Great Britain Policies
  3. Great Britain Data Processing Addendum

Great Britain · English

Great Britain Data Processing Addendum

Prelaunch preview · Published 13 November 2026

In this policy
  1. Scope, definitions and roles
  2. Customer instructions and responsibilities
  3. Restricted use and confidentiality
  4. Security
  5. Subprocessors
  6. Requests from individuals and complaints
  7. Personal data breaches
  8. Assistance and compliance information
  9. Processing locations and international transfers
  10. Retention, return and deletion
  11. Continuing obligations, priority and contact

This is a prelaunch preview. The effective date of the completed addendum will be the recorded date on which TAP and the Customer accept it with the applicable completed schedules.

This Data Processing Addendum (“DPA”) is between Ardor Service LLC, doing business as TAP Agreements (“TAP”) and the business customer identified in the accepted order or account record (“Customer”). It forms part of their TAP service agreement when accepted by both parties, including through a recorded electronic acceptance that identifies this version and its completed schedules. It applies to personal data TAP processes on the Customer’s behalf in providing the Services (“Customer Personal Data”).

The completed annexes form part of this DPA. TAP will make them available before the Customer accepts the applicable order. Covered processing begins only after the applicable annexes are complete and any required transfer arrangements are binding. A publicly available preview does not itself put an international transfer mechanism in place.

1 Scope, definitions and roles

“Data Protection Law” means the UK GDPR, the Data Protection Act 2018 and other applicable UK data protection and privacy law, as amended. Controller, processor, personal data, data subject, personal data breach and processing have their meanings under that law. “Subprocessor” means another processor engaged by TAP to process Customer Personal Data.

The Customer is ordinarily the controller and TAP its processor. Where the Customer acts as a processor for another controller, TAP acts as its subprocessor; the Customer confirms it has the controller’s authority to appoint TAP, accept these terms and relay lawful instructions. References to the Customer’s controller responsibilities apply according to its actual role and do not transfer TAP’s own legal obligations to the Customer.

TAP’s separately determined uses of limited account, billing, website, business administration and independent security information are described in the Great Britain Privacy Statement. Merely possessing Customer Personal Data does not authorise TAP to repurpose it as controller data. This DPA does not permit a use prohibited by the service agreement or Privacy Statement.

2 Customer instructions and responsibilities

The Customer instructs TAP to carry out the processing in Annex 1, provide the functions selected in the service, follow authorised workspace instructions and implement other lawful written instructions agreed by the parties. Instructions include agreed storage, export, deletion, recipient and transfer arrangements. Email and other retainable electronic records may document instructions.

The Customer is responsible for determining the purposes and lawful grounds of its agreements, providing required notices, securing any necessary permissions, selecting information reasonably necessary for its transactions and checking the suitability of the service. The standard Great Britain service is limited to ordinary nonsensitive business agreements. Preparation sources must be blank or reliably anonymised. Special-category personal data, criminal-offence information and biometric-recognition processing are prohibited, including sensitive-purpose forms and questions, edits, signer free text, attachments and support submissions. These duties do not excuse defective performance or a breach by TAP.

TAP will process Customer Personal Data only on documented instructions, including for international transfers, unless UK law requires otherwise. Where UK law requires additional processing, TAP will tell the Customer before it occurs unless that law prohibits notice on important public-interest grounds. TAP will immediately inform the Customer if, in its opinion, an instruction infringes Data Protection Law and may pause the affected instruction while the parties resolve the issue. A foreign legal demand is not automatically treated as overriding UK restrictions; TAP will assess applicable law and transfer protections and notify the Customer to the extent legally permitted.

Unexpected prohibited content. If prohibited information is received, TAP will restrict access, stop further preparation/publication and onward AI disclosure, notify the Customer using minimal information, assess existing exposure and arrange controlled deletion subject to specific binding preservation requirements. Receipt and review are still processing; these safeguards do not make prohibited use supported or accidental receipt impossible.

3 Restricted use and confidentiality

TAP will use Customer Personal Data only to provide, support and secure the instructed Services and comply with obligations lawfully applicable to that processing. TAP will not sell it, use it for advertising, unrelated marketing or unrelated product development, or use it to train general-purpose models. TAP will not permit a Subprocessor to use it for those purposes. These restrictions include signer contact details and IP addresses collected for the signing record.

TAP will limit access to authorised people who need it for permitted functions. Those people must be subject to an appropriate contractual or statutory duty of confidentiality and receive instructions appropriate to their access and responsibilities. The confidentiality and use restrictions continue while TAP or its Subprocessors retain the information.

4 Security

TAP will implement and maintain technical and organisational measures meeting Article 32 of the UK GDPR, taking account of the state of the art, implementation costs, the nature, scope, context and purposes of processing, and the likelihood and seriousness of risks to people. Annex 2 records the agreed security measures and their scope.

TAP will protect the confidentiality, integrity, availability and resilience of the relevant systems and services, maintain appropriate recovery arrangements, and regularly assess the effectiveness of its safeguards. Changes to safeguards must not materially reduce the overall protection promised for the contracted processing. The Customer remains responsible for its own credentials, user permissions, devices, lawful recipient selections and downloaded copies.

5 Subprocessors

Under the completed DPA, the Customer gives general written authorisation to engage the Subprocessors identified in the register incorporated in Annex 3 at acceptance. The register identifies each provider’s legal entity, function, relevant processing locations and transfer arrangement. TAP will give advance written notice of an intended addition or replacement and allow the Customer to object on reasonable data-protection grounds before the change takes effect. The completed DPA will specify the notice period and procedure.

The parties will work in good faith to resolve a timely objection, including considering an available alternative. TAP will not introduce the disputed Subprocessor for that Customer’s information while the objection remains unresolved. If no reasonable solution is available, either party may end the affected service before the proposed use starts; TAP will refund unused prepaid charges for that affected service and honour agreed export, return, preservation and deletion arrangements. This does not authorise introducing a new Subprocessor without the required notice and opportunity to object.

Before a Subprocessor receives Customer Personal Data, TAP will bind it by a written contract imposing data-protection obligations offering an equivalent level of protection to this DPA, including appropriate security, confidentiality and use limits. TAP remains responsible to the Customer for the Subprocessor’s performance of those obligations.

6 Requests from individuals and complaints

Taking account of the nature of the processing, TAP will provide appropriate technical and organisational assistance so the Customer can respond to requests to exercise data-protection rights. TAP will promptly pass to the Customer a request or complaint concerning its Customer Personal Data, unless prohibited by law, and will not decide it on the Customer’s behalf except on instructions or where law requires TAP to do so.

TAP may provide necessary routing information and will deal directly with matters for which it is independently responsible. Assistance includes locating and exporting relevant information, supporting correction, restriction or erasure, and providing information about recipients and safeguards where required. Corrections to an executed agreement must preserve an accurate record of what was signed while enabling lawful correction or an explanatory record; they must not conceal a material alteration.

7 Personal data breaches

TAP will notify the Customer without undue delay after becoming aware of a personal data breach affecting Customer Personal Data. It will not wait for a complete investigation before providing an initial notice. The notice will include information then available about the nature of the breach, affected information and individuals, likely consequences, measures taken or proposed and a contact for further information. TAP will provide material updates as the investigation proceeds.

TAP will take appropriate steps to contain, investigate and remedy the breach, preserve relevant evidence and assist the Customer with its notification and response duties. The Customer determines notifications for processing under its control, without limiting any notification duty directly imposed on TAP. A notice is not an admission of liability. The Customer must keep an effective incident contact current in Annex 1 or its account record.

8 Assistance and compliance information

Taking account of the nature of processing and information available to it, TAP will assist the Customer with security obligations, breach notifications, data protection impact assessments and prior consultation with the competent regulator under Articles 32–36. TAP will provide relevant information about the instructed processing and safeguards.

TAP will make available information needed to demonstrate compliance with Article 28 and permit and contribute to audits and inspections by the Customer or its independent auditor. The parties may use proportionate documentary review first and agree reasonable confidentiality, scheduling and security arrangements. Those arrangements must not prevent an effective audit, necessary investigation, urgent incident response or regulatory access. TAP is not required to disclose another customer’s personal data, but will offer an appropriate method of demonstrating compliance.

Any reasonable charges for substantial additional assistance must be agreed in advance, must not delay a legally required response, and will not be imposed for work necessary to remedy TAP’s breach. No fee provision limits a data subject’s or regulator’s rights.

9 Processing locations and international transfers

The service is provided by a US company. Selecting the Great Britain offering does not establish a UK-only storage or access arrangement. Annexes 3 and 4 identify permitted processing locations and the protections for relevant transfers.

TAP will not make or enable a restricted transfer contrary to the Customer’s instructions or Data Protection Law. Before a transfer requiring safeguards begins, the responsible parties must establish the applicable lawful mechanism and any required assessment or supplementary measures. A transfer to TAP and a transfer by TAP to a Subprocessor must each be assessed on their own facts.

Where UK adequacy regulations are relied on, the actual recipient and processing must fall within them. The UK Extension to the EU-US Data Privacy Framework may be used only while the relevant recipient has an active, applicable certification covering that transfer. Where contractual safeguards are used, the completed ICO International Data Transfer Agreement, or the relevant EU standard contractual clauses with the completed UK Addendum, forms part of the parties’ agreement as identified in Annex 4. Stating that such clauses may be used does not execute them.

TAP will provide reasonable information and assistance needed for the transfer assessment. If a safeguard ceases to provide a lawful basis for a transfer, TAP will notify the Customer and put a lawful replacement in place or suspend the affected transfer. The parties will arrange continued protection, return or deletion as required. Mandatory transfer provisions prevail over conflicting commercial terms and may not be weakened by this DPA.

10 Retention, return and deletion

The Customer’s documented instructions and accepted Plan Details identify any agreed archive. The archive remains part of the processing service for the agreed period after paid service ends. Turning off renewal or ending billing alone is not an instruction to erase it. The archive does not override an authorised earlier deletion instruction, applicable individual rights or a legal requirement for different treatment.

At the Customer’s choice, TAP will return or delete Customer Personal Data when the relevant processing service ends, including the instructed archive period, and delete existing copies unless UK law requires storage. TAP will support earlier lawful instructions consistently with the agreed service. Any particular retention required by law must be restricted to that purpose and duration, protected and explained to the Customer to the extent permitted. A possible future dispute does not justify indefinite retention of all agreements.

TAP will delete live copies and instruct relevant Subprocessors to do the same. Where immediate removal from protected backups is not practicable, TAP will put the information beyond ordinary use and remove it through the documented deletion cycle in Annex 2, with any applicable earlier legal deadline taking priority. It will not restore deleted information into ordinary use. On reasonable request, TAP will confirm completion, identifying any lawful retention or backup period still outstanding.

Return will use the agreed usable export formats and a secure verified method. Deleting TAP’s copy does not delete copies the Customer or authorised recipients already hold. Those recipients remain responsible for their copies.

11 Continuing obligations, priority and contact

This DPA continues for as long as TAP or its Subprocessors process Customer Personal Data. The service agreement’s governing law and commercial liability provisions apply only to the extent consistent with this DPA, mandatory law and controlling transfer terms. No commercial limit restricts a data subject’s statutory rights, a regulator’s powers or mandatory transfer rights. This DPA prevails for its subject matter as provided in the service agreement.

TAP’s data-protection contact is dpo@tapagreements.com. General support: support@tapagreements.com. Postal address: Ardor Service LLC, DBA TAP Agreements, 1034 N. Madison Ave, Pasadena, CA 91104, United States. Telephone: +1 626-630-0096.

Annex 1 Processing details and instructions

Item Planned scope
Customer and contact The legal entity, business address, authorised contact and incident email in the accepted order/account record. If the Customer is a processor, record the relevant controller and authority to appoint TAP.
TAP Ardor Service LLC, DBA TAP Agreements, at the postal address and data-protection email above.
Subject matter Customer-directed preparation, presentation, completion, signing, distribution, storage, retrieval, export and deletion of business agreements and associated records.
Nature of processing Collection and receipt; document conversion and field preparation; organisation and storage; controlled access and display; collection of completed fields and signatures; generation of completed PDFs and evidence records; delivery to authorised recipients; backup/recovery; support; correction, export, restriction and deletion.
Purposes Providing the Customer’s selected agreement workflow and associated support, security and record services under its documented instructions. No advertising, unrelated marketing or general-purpose model training.
Data subjects Customer staff and representatives; signers and other agreement participants; customers, suppliers, contractors and other people identified in submitted agreements; children whose information is lawfully supplied in a supported transaction by an authorised adult or business.
Ordinary data Names, roles, business and contact details; uploaded and approved documents and images; form responses and attachments; signatures/initials; transaction and agreement details; participant assignments; completion/consent events, status, IP addresses, timestamps and associated technical evidence; related support information.
Excluded information Article 9 special-category data, Article 10 criminal-offence information and biometric-recognition processing are outside the standard GB service. Sources must be blank or reliably anonymised, with no real people’s prefilled records. Sensitive-purpose forms/questions remain unsupported even when blank. Ordinary names, contacts and typed/drawn signatures are not automatically special-category data.
Frequency As initiated by the Customer and authorised participants; storage and protection continue for the instructed retention period.
Duration and archive The accepted Plan Details and documented instructions identify the processing duration, which completed agreements, signing evidence and approved originals are covered, when the archive starts, and applicable retrieval arrangements. They specify whether approved originals are covered before a completed agreement is produced.
Shorter-lived materials Unaccepted or unusable uploads, temporary copies, drafts and unused templates follow the preparation, review, export and deletion periods in the accepted Plan Details and service schedules.
Access and disclosure Authorised users share workspace records under configured permissions. The workflow may provide completed agreements to authorised participants. Assigned fields do not make the remainder private. Original uploads are nonpublic and not automatically shared with outside signers.
End of processing Customer’s return/deletion choice under section 10, with export methods, deletion timings and backup cycle completed in the service schedules.

Annex 2 Security measures and deletion schedule

The measures below describe proposed contractual commitments for the operational service. The completed schedule will identify their implemented scope, storage and access locations, and agreed time limits.

TAP will maintain the following measures for the processing covered by this DPA, proportionate to the nature of the data and identified risks:

Area Contractual commitment
Access and authorisation Limit access to approved users and personnel with a service-related need. Apply role-based permissions and appropriate authentication; protect privileged access; review and remove access when it is no longer required.
Customer separation Use controls that prevent one customer’s users from accessing another customer’s records. Apply the agreed workspace permissions and controls for signing links, public reusable links, private originals and completed copies.
Transmission and storage Use encrypted connections for transmission of Customer Personal Data over public networks and protective measures appropriate to stored information, including appropriate control of encryption keys and credentials. Record the actual storage and encryption arrangements in the completed security particulars.
Personnel and access to documents Bind authorised people to confidentiality; provide appropriate security and data-handling instructions; restrict support access to permitted functions and retain appropriate records of privileged activity.
System and software security Maintain a documented process for secure changes, vulnerability identification, risk-based patching, protection against malicious software and secure management of secrets and configuration.
Monitoring and incidents Maintain relevant security and access logs, assess suspicious activity and follow a documented incident-response process supporting the notification and assistance obligations in this DPA. Do not use security logging as a basis for unrelated tracking of signers.
Continuity and recovery Maintain protected backups and recovery arrangements appropriate to service risks; regularly assess recovery capability and keep backup access restricted.
Return, deletion and restoration Provide secure verified exports; implement authorised restriction and deletion; document the removal of live copies and Subprocessor copies; prevent restored backups from returning previously deleted data to ordinary use.
Providers and facilities Assess providers’ ability to protect the relevant data, put required contracts in place and obtain reasonable evidence of appropriate physical, access and environmental protections for hosting facilities.
Review and effectiveness Regularly assess the effectiveness of the measures, address identified deficiencies and document relevant changes without materially reducing contracted protection.

The completed schedule will identify the systems and records covered, implemented access and encryption controls, storage and remote-access locations, incident contacts and available evidence of safeguards. It will specify time limits for temporary materials, security logs, live-system deletion and the finite backup deletion cycle. Customer instructions and applicable legal deadlines remain controlling as set out in section 10.

Annex 3 Subprocessor register and notices

Planned service schedule GB-PROVIDERS-2026-11-12-04. The following facts describe the selected providers; this preview does not authorise document processing. Before acceptance, the completed register will identify effective account arrangements, applicable remote-access countries, transfer safeguards and change-notice procedure.

Provider / legal entity Function and Customer Personal Data Established or configured location
OVH US LLC, trading as OVHcloud Application, database, preparation workers and related infrastructure support; permitted agreement content, workspace records and signing/service evidence. Virginia primary and Oregon standby, United States. Relevant support/onward routes are qualified below.
Amazon Web Services, Inc. — US account route Document storage, including preparation sources, completed PDFs and signing evidence; encrypted database backups. Documents: us-east-1, Northern Virginia, United States. Effective backup destination and account-specific support/replica arrangements must be confirmed in the completed schedule.
OpenAI OpCo, LLC Automated preparation using required document text/images/instructions and generated output. No additional AI provider is authorised by this schedule. International processing under the applicable project and service arrangements. No US-only or UK-only boundary is established by the approved Zero Data Retention arrangement.
Twilio Inc. / SendGrid Email API Recipient details, transactional message text, business/agreement titles, retrieval links and delivery records. The standard completed-copy message links to the document rather than attaching its PDF. Global email endpoint; provider-listed US and other regional arrangements described below. Recipient mailbox delivery follows the customer’s instructions.

Stripe billing, identity and website providers are mapped separately according to their actual roles. A provider receiving agreement information through support or another enabled function must also be assessed for that function. Local OCR/parsing/scanning software is not a separate cloud recipient merely because TAP uses it.

Provider processing locations

TAP operates from the United States. Its application infrastructure and document storage are in the US locations above. AI preparation, email delivery and provider support can involve additional countries. The information below distinguishes established TAP hosting from provider-published possible processing arrangements, reviewed on 12 November 2026. It does not mean that every agreement is processed in every listed country.

OVHcloud. In addition to TAP’s US hosting, the OVH US data-processing agreement lists potential affiliate processing in Australia, Canada, France, Germany, India, Ireland, Italy, the Netherlands, Poland, Portugal, Singapore, Spain and the United Kingdom, and third-party processing in Finland, France and the United States. These are provider-listed possibilities; they do not establish that each location receives TAP agreement contents. Applicable support and onward access will be identified in the completed service schedule.

AWS. TAP document storage uses the Northern Virginia region. The AWS subprocessor list explains that relevant infrastructure depends on the selected service and region. It separately lists customer-requested support in Australia, Canada, Costa Rica, Egypt, France, Germany, Hong Kong, India, Ireland, Italy, Japan, South Africa, South Korea, Taiwan and the United States. AWS says customer data is shared with support subprocessors only with the customer’s agreement during support. Those support locations are not additional confirmed TAP storage locations.

OpenAI. Its API subprocessor list identifies cloud infrastructure in Australia, Belgium, Brazil, Canada, Denmark, Finland, France, Germany, India, Indonesia, Ireland, Italy, Japan, Malaysia, Mexico, the Netherlands, New Zealand, Norway, Poland, Singapore, South Africa, South Korea, Spain, Sweden, Switzerland, the United Arab Emirates, the United Kingdom and the United States. The Philippines is an additional listed location for conditional moderation and support. Customer-support processing depends on information explicitly shared in a support case. API network delivery can also follow Cloudflare’s global network routing. These are provider-published possibilities, not observed destinations for every TAP request; account settings and the features used affect applicable processing.

Twilio SendGrid. TAP uses SendGrid’s global email endpoint. The SendGrid-specific entries in Twilio’s subprocessor list describe infrastructure in the United States, North America and the European Union. That list does not identify every country applicable to TAP’s route. We are completing that service-specific mapping before Great Britain agreement processing opens. The regional descriptions are not a promise of US-only delivery or access.

Provider lists can change. We keep this schedule under review and will give appropriate notice of relevant changes. Before covered processing begins, the completed addendum will identify the applicable providers and countries and set out notice and a reasonable objection process for changes. Links to a provider’s wider list do not by themselves authorise unrestricted processing or a new purpose.

Official provider disclosures: OVH US DPA and schedules, AWS subprocessors, OpenAI subprocessors, Twilio subprocessors. This factual location disclosure is reused from TAP’s Australian schedule reviewed on 12 November 2026; it does not import Australian legal terms.

Annex 4 Transfer implementation schedule

The intended initial transfer is from the Customer’s Great Britain establishment to Ardor Service LLC, United States, normally as Customer-controller to Ardor-processor. The Customer’s identity, role, authorised instructions and any upstream-controller authority are completed for that actual Customer. The processing purposes, ordinary data categories, participants and frequency are in Annex 1; final duration and safeguards must match Annex 2.

The prepared route is a standalone UK International Data Transfer Agreement identifying the final DPA and schedules. The parties must complete and accept that instrument, and record the applicable transfer assessment, before the restricted transfer starts. Ardor is not represented as certified under the UK Extension to the EU-US Data Privacy Framework.

Onward provider Contractual route identified for completion
OVH US LLC Applicable US service agreement/DPA and its UK Addendum; retain the accepted account/order terms.
Amazon Web Services, Inc. Applicable AWS customer agreement, DPA and UK GDPR Addendum; confirm the account/service mapping.
OpenAI OpCo, LLC Applicable Services Agreement and DPA with UK transfer provisions. The BAA and Zero Data Retention controls supplement, and do not replace, these safeguards.
Twilio Inc. / SendGrid Applicable Terms and DPA UK transfer provisions for SendGrid; verify the governing route rather than assuming every Twilio group mechanism covers this service.

The completed schedule must map each applicable destination/access country and relevant onward safeguards. An assessment of the United States is not by itself an assessment of all possible global provider destinations. A provider’s broader list neither proves actual TAP routing to every location nor creates unrestricted authorisation. TAP will complete the applicable provider arrangements, safeguards and notice procedure before covered processing; customer and provider acceptance records remain distinct.

Back to top ↑

Trusted Agreement Platform (TAP)
About TAPPricing
Great Britain Privacy StatementGreat Britain Terms of Service (preview)Great Britain Policies
Operated by Ardor Service LLCTAP homePrivacy questions

Help us improve TAP

With your permission, we use Google Analytics through Cloudflare Zaraz to measure page visits and navigation clicks. You can decline or change your choice here at any time.

Great Britain Privacy Statement

Cookie and Analytics Notice