Electronic Team uses cookies to personalize your experience on our website. By continuing to use this site, you agree to our cookie policy. Click here to learn more.

HelpWire Data Processing Agreement

Last updated: 15 October 2026

In short: If you use HelpWire to handle other people's personal data — your clients, employees, or customers — the law (notably the GDPR) requires a written contract about how we process that data for you. This is that contract. It applies automatically; you don't need to sign anything.

1. Parties and Incorporation

This Data Processing Agreement ("DPA") forms part of the HelpWire Terms of Service ("Terms") between Electronic Team, Inc. ("we," "us," the "Processor") and the customer accepting the Terms ("Customer," "you," the "Controller"). It applies automatically whenever you use the Service to process personal data of Clients or other individuals on whose behalf you act, and takes effect on your first such use. If you need a copy of this DPA for your records, contact dpo@electronic.us.

2. Definitions

Capitalized terms not defined here have the meanings in the Terms. "Personal data," "controller," "processor," "data subject," "processing," "personal data breach," and "supervisory authority" have the meanings in the GDPR. "Applicable Data Protection Law" means the GDPR, the UK GDPR, the Swiss Federal Act on Data Protection, the CCPA/CPRA, the Virginia CDPA, and other data-protection laws applicable to the processing under this DPA. "Customer Data" means personal data that you or your Operators submit to or generate in the Service and that we process on your behalf, as detailed in Annex 1 — including Client directory records, notes, and session metadata associated with your Clients.

3. Roles

You are the controller of Customer Data (or a processor acting for another controller, in which case we are your subprocessor and you warrant your instructions are consistent with the controller's). We are your processor. For CCPA/CPRA purposes, we act as your "service provider": we process Customer Data only to provide the Service, and we do not sell it, share it for cross-context behavioral advertising, retain it, use it, or disclose it for any purpose other than performing the Service or as permitted by the CCPA. We will not combine Customer Data with personal information we receive from other sources except as the CCPA permits, will comply with the CCPA and provide the level of privacy protection it requires, and will notify you if we determine that we can no longer meet our obligations under the CCPA. You may take the reasonable and appropriate steps described in Section 12 to ensure that we use Customer Data consistently with your obligations, and may direct us to stop and remediate any unauthorized use. For the Virginia CDPA and other U.S. state privacy laws, we act as your processor, and this DPA is the contract those laws require between a controller and its processor.


For clarity, we act as an independent controller — not your processor — for the data described in Section 2 of the Privacy Policy as controller data (your account, billing, support, and analytics data). We also act as an independent controller for the limited use of device identifiers and session metadata to enforce Plan limits and to detect and prevent abuse, as described in Sections 2 and 3 of the Privacy Policy. Section 9.2 of the Terms is your documented instruction to create aggregated or de-identified statistics from Customer Data on the conditions stated there; once aggregated or de-identified so that no individual, Organization, or Client can be identified, those statistics are not Customer Data and are not subject to this DPA.


Your obligations. You are responsible for the lawfulness of Customer Data and of your instructions, for giving Clients and other data subjects any notices and obtaining any consents that Applicable Data Protection Law requires, for not storing special categories of personal data or the regulated data described in Section 9.4 of the Terms in client records, notes, or chat except where Section 9.4 permits it and you have a lawful basis to do so, for the lawfulness of any personal data, including special categories, that appears in Session content transmitted through the Service, and for configuring the Service's security features (including access groups, and making sure your Operators enable MFA) appropriately for your use.

4. Details of Processing

The subject matter, duration, nature and purpose of processing, categories of data subjects, and categories of personal data are set out in Annex 1.

5. Our Obligations

We will: (a) process Customer Data only on your documented instructions (including with regard to transfers of Customer Data to a third country) — which are: the Terms, this DPA, and your and your Operators' use of the Service's features — unless law requires otherwise, in which case we will inform you unless the law prohibits it; (b) promptly inform you if, in our opinion, an instruction infringes Applicable Data Protection Law; (c) ensure persons authorized to process Customer Data are bound by confidentiality obligations; (d) not sell Customer Data or share it for advertising purposes; (e) maintain a record of the processing we carry out on your behalf as required by Article 30(2) GDPR; and (f) notify you without undue delay, unless legally prohibited, if we receive a legally binding request from a public authority for access to Customer Data, and disclose only the minimum required.

6. Security

We implement the technical and organizational measures ("TOMs") described in Annex 2, taking into account the state of the art and the risks of the processing. We may update the TOMs, provided updates do not materially reduce the level of protection.

7. Subprocessors

You generally authorize us to engage subprocessors to provide the Service. The subprocessors listed on the date you accept this DPA are approved. That list is also the agreed list of sub-processors for the purposes of Clause 9(a) of the Standard Contractual Clauses in Annex 3. The current list of subprocessors that process Customer Data is at https://www.helpwire.app/legal/subprocessors/, together with a dated record of changes. We will notify Organization owners by email at least 14 days before adding or replacing such a subprocessor. You may object on reasonable data-protection grounds within that window; if we cannot offer a workaround, you may cancel your subscription as described in the Terms, effective at the end of your current billing period. We remain responsible for our subprocessors' performance and will impose data-protection obligations on them no less protective than this DPA. On request, we will provide a summary of the data-protection terms in place with a subprocessor.

8. Assistance

Taking into account the nature of the processing, we will assist you with appropriate technical and organizational measures, insofar as possible, in fulfilling your obligations regarding: (a) data-subject requests — if a data subject contacts us directly about Customer Data, we will refer them to you and not respond on the merits except as required by law; (b) security, breach notification, data-protection impact assessments, and prior consultation with supervisory authorities. We may charge reasonable fees for assistance that exceeds the Service's built-in capabilities, and will tell you before costs arise.

9. Personal Data Breach

We will notify you without undue delay, and in any event within 72 hours, after becoming aware of a personal data breach affecting Customer Data. The notice will describe, to the extent known, the nature of the breach, categories and approximate numbers of data subjects and records affected, likely consequences, and measures taken or proposed. Our notification is not an acknowledgment of fault or liability. We will reasonably cooperate with your own notification obligations. We will not notify data subjects or authorities on your behalf unless you instruct us to or the law requires it.

10. International Transfers

Customer Data is processed on our production infrastructure in California, USA, and in the countries where our subprocessors operate (see the subprocessor list). Session relay servers operate in 12 AWS regions worldwide but carry only end-to-end-encrypted session content, which we do not decrypt. For transfers of EU/EEA, UK, or Swiss personal data to countries without an adequacy decision, the parties incorporate the European Commission's Standard Contractual Clauses (Module Two: controller-to-processor), completed as set out in Annex 3, which also completes the UK Addendum and the Swiss adaptations, as applicable. Electronic Team does not currently hold an EU-U.S. Data Privacy Framework certification; where a subprocessor holds one, it may rely on it for the relevant transfer. Each subprocessor that processes Customer Data in the United States is certified under the Data Privacy Framework or bound to us by the SCCs.

11. Deletion and Return

Customer Data is available to you in the Service during the subscription. Upon deletion of your account, Customer Data is deleted immediately and irreversibly from production systems, consistent with Section 13 of the Terms; encrypted backup snapshots containing deleted data expire within 7 days, and IP addresses in rotating server logs are overwritten within 30 days. At the end of the Service, at your choice, we will return Customer Data to you by providing an export in a common machine-readable format, or delete it. You may request an export at any time, at no charge, and we will provide it within 30 days of your request; Customer Data then remains available in the Service for at least 30 days after we provide the export, unless you delete your account earlier, and you may extend either period once by notice before it ends. During those periods we will provide reasonable assistance with the export and keep the Service available. If we terminate your account, Customer Data remains available for export for at least 30 days after termination before it is deleted, unless law prohibits the export, requires us to preserve the data for an investigation, or the account was used for unauthorized access or fraud. Section 13.4 of the Terms describes the categories of data included in an export and the deletion that follows a switching request. Where you delete your account yourself, you instruct us to delete Customer Data immediately without prior return. On written request, we will confirm deletion. We may retain Customer Data only where and as long as law requires, protected under this DPA.

12. Audits

We will make available information reasonably necessary to demonstrate compliance with this DPA — first through documentation and security summaries. We do not currently hold third-party security certifications or attestations (such as SOC 2 or ISO 27001). Where these are insufficient under Applicable Data Protection Law, you may conduct (directly or through a non-competitor auditor bound to confidentiality) an audit of relevant processing facilities and records: no more than once per calendar year, on at least 30 days' written notice, during business hours, minimizing disruption, and at your own cost unless the audit reveals a material breach of this DPA.

13. Liability, Precedence, Term

Each party's liability under this DPA is subject to the limitations and exclusions in Section 16 of the Terms, which apply in aggregate across the Terms and this DPA. If this DPA conflicts with the Terms on data-protection matters, this DPA prevails; the SCCs, where they apply, prevail over both. This DPA lasts as long as we process Customer Data and terminates automatically when processing ends.



Annex 1 — Details of Processing

Subject matter. Provision of the HelpWire remote support and remote desktop service.


Duration. The term of the Customer's use of the Service, until deletion under Section 11 of this DPA.


Nature and purpose. Hosting and transmission of data required to establish and manage remote support sessions between the Customer's Operators and its Clients; storage of the Customer's client directory, chat messages, session events, and session metadata; transmission (without content retention) of end-to-end-encrypted session content — screen data, input, clipboard, and files.



Categories of data subjects.


  • The Customer's Clients: individuals whose devices receive remote support (customers, employees, contractors, or other end users of the Customer).

  • The Customer's Operators, to the extent their data appears within Customer Data (e.g., in session metadata).


Categories of personal data.


  • Client identification data entered by the Customer: name, email address, phone number, company, country, order number, messenger contact details, social profile links, and any other information Operators choose to record in notes fields.

  • Session metadata and device records: session start/end times and duration, IP addresses, OS name and version, host name, CPU architecture, BIOS UUID, router MAC address, hashed hardware characteristics, and connection events.

  • Chat messages and session events: stored for the Customer's Organization until deletion of the related record or account.

  • Session content transmitted during Sessions (screen content, input, clipboard, transferred files) — end-to-end encrypted between the Operator and Client applications and transmitted only; never stored by us. The content of this data is determined solely by the Customer and its Clients and may include any category of personal data, including special categories; the Customer is responsible for the lawfulness of transmitting it.


Special categories. Not requested or required by the Service, and not to be stored in client records, notes, or chat (Terms Section 9.4). Special categories may be present in Session content that the Customer transmits and that we do not store, and may appear incidentally in Customer-entered fields despite Section 9.4; in both cases the Customer is responsible for the lawfulness of the processing.


Frequency. Continuous, as driven by the Customer's use.

Annex 2 — Technical and Organizational Measures (TOMs)

This annex describes the technical and organisational measures ("TOMs") we implement under Article 32 GDPR. It mirrors Section 11 of our Privacy Policy.


Encryption and transmission. Session content (screen, input, clipboard, file transfer) is end-to-end encrypted between the Operator and Client applications using TLS 1.3 with cipher suite TLS_AES_256_GCM_SHA384 (AES-256-GCM); it is not decrypted at relay servers or any intermediate node. Application-to-server traffic (chat, service commands) is encrypted in transit with the same protocols and decrypted only on the central server. QUIC+TLS is used where UDP transport is required; web traffic runs over HTTPS/WSS. Database connections are encrypted in transit.


Data minimization by architecture. No recording or storage of session audiovisual content; transferred files and clipboard content are never stored server-side. Chat messages and session events are stored for the Customer's Organization until deletion of the related record or account.


Data portability and erasure. Self-service account deletion removes Customer Data from production systems immediately, and exports of Organization data in a common machine-readable format are available on request (Terms Section 13.4).


Access control. Personal data accessible only to personnel who need it for their duties. Internal services reachable only via corporate VPN behind an additional authentication layer, with individual per-service credentials. Customer-side access control: Organization owners control Operator membership and group-level client access; MFA available for all user accounts via Clerk.


Infrastructure. Production servers located in California, USA (AWS us-west-1); session relay servers on AWS across 12 regions worldwide; a separate server distributes application builds. Applications code-signed (DigiCert). Authentication and credential management via Clerk.


Availability and resilience. Backups of file directories and database dumps are taken every 2 days; volume snapshots are encrypted and retained for a maximum of 7 days. Key infrastructure parameters are continuously monitored with automated alerting, and an on-call administrator team responds to incidents. Recovery procedures are executed manually and verified as needed.


Personnel. Confidentiality obligations for staff with data access; privacy and security policies binding on employees.


Incident response. Infrastructure monitoring with automated alerting and an on-call administrator team, supporting the breach-notification commitment in Section 9.


Subprocessor management. Subprocessors engaged under Section 7; list maintained at https://www.helpwire.app/legal/subprocessors/.


Review. These measures are reviewed and updated from time to time, and whenever we make a significant change to the Service or our infrastructure.

Annex 3 — Standard Contractual Clauses, UK Addendum, and Swiss Adaptations

This Annex 3 forms part of the HelpWire Data Processing Agreement (the "DPA") between Electronic Team, Inc. ("Electronic Team") and the customer accepting the HelpWire Terms of Service (the "Customer"). Capitalized terms not defined here have the meanings given in the DPA and the Terms. Part A incorporates and completes the EU Standard Contractual Clauses for transfers of personal data from the European Economic Area. Parts B to D set out the Annexes the Clauses require. Part E completes the UK International Data Transfer Addendum for transfers from the United Kingdom. Part F contains the adaptations that apply to transfers from Switzerland. Part G contains operational terms that apply to all three.


Part A. Incorporation and completion of the EU Standard Contractual Clauses


1. Incorporation. The standard contractual clauses for the transfer of personal data to third countries annexed to Commission Implementing Decision (EU) 2021/914 of 4 June 2021 (the "Clauses") are incorporated into the DPA by reference under Section 10 of the DPA and apply to every transfer of personal data that is subject to Regulation (EU) 2016/679 (the "GDPR") from the Customer to Electronic Team. Module Two (transfer controller to processor) applies. The Customer is the data exporter and Electronic Team is the data importer.


2. Execution. By accepting the Terms and using the Service to process personal data of Clients or other individuals on whose behalf it acts, the Customer is deemed to have signed the Clauses, including the Annexes completed in Parts B to D, with effect from the first such use. Electronic Team is deemed to have signed the Clauses on the same date by making the Service available under the DPA. A copy of the Clauses is available on request from the contact in Part B.


3. Selections. The Clauses are completed as follows.


  • Clause 7 (docking clause) is included.

  • Clause 9(a): Option 2 (general written authorisation) applies. The agreed list of sub-processors is the list in Part D, as maintained at the address stated there. The period for prior notice of any intended addition or replacement is 14 days, as provided in Section 7 of the DPA.

  • Clause 11(a): the optional language on an independent dispute resolution body is not included.

  • Clause 13(a): the paragraph that applies is determined by the position of the data exporter. Where the data exporter is established in an EU Member State, the supervisory authority of that Member State is competent. Where the data exporter is not established in an EU Member State but falls within Article 3(2) of the GDPR and has appointed a representative under Article 27, the supervisory authority of the Member State in which the representative is established is competent. Where the data exporter is not established in an EU Member State and falls within Article 3(2) without being required to appoint a representative, the supervisory authority of one of the Member States in which the data subjects whose personal data is transferred are located is competent.

  • Clause 17: Option 1 applies. The Clauses are governed by the law of Ireland.

  • Clause 18(b): the courts of Ireland are the courts chosen for the resolution of disputes.


4. Customers acting as processors. Where the Customer uses the Service as a processor on behalf of another controller (Section 3 of the DPA), Module Three (transfer processor to processor) applies in place of Module Two, with the same selections and the same Annexes, notwithstanding the reference to Module Two in Section 10 of the DPA. In that case the Customer warrants that it holds the controller's authorisation for the transfer and for the engagement of Electronic Team as a sub-processor, and the Customer is responsible for passing on to its controller the information that the Clauses require the data importer to provide to the controller, including notice of changes to the list of sub-processors under Clause 9(a).


5. Precedence. In accordance with Clause 5, the Clauses prevail over the DPA and the Terms in the event of a conflict, and the DPA and the Terms do not limit the rights of data subjects under the Clauses.

Part B. Annex I to the Clauses

A. List of parties



Data exporter Name: the Customer, being the legal entity or individual identified in the HelpWire account and Organization details.
Address: as recorded in the HelpWire account.
Contact person's name, position and contact details: the Organization owner, at the email address recorded in the HelpWire account.
Activities relevant to the data transferred under the Clauses: use of the HelpWire remote support and remote desktop service to provide support to the Customer's Clients.
Signature and date: deemed given by acceptance of the Terms (Part A.2).
Role: controller (or processor, where Part A.4 applies).
Data importer Name: Electronic Team, Inc.
Address: 11890 Sunrise Valley Dr, Ste 111, Reston, VA 20191, United States.
Contact person's name, position and contact details: Privacy contact, dpo@electronic.us, +1 202 335 8465.
Activities relevant to the data transferred under the Clauses: provision of the HelpWire remote support and remote desktop service, including hosting of the Customer's client directory, chat messages, session events and session metadata, and transmission of end-to-end-encrypted session content.
Signature and date: deemed given under Part A.2.
Role: processor.


B. Description of transfer



Categories of data subjects whose personal data is transferred The Customer's Clients: individuals whose devices receive remote support through the Service, including the Customer's customers, employees, contractors and other end users.
The Customer's Operators, to the extent their personal data appears within Customer Data, for example in session metadata and session events.
Categories of personal data transferred Client identification data entered by the Customer: name, email address, phone number, company, country, order number, messenger contact details, social profile links, and any other information Operators record in notes fields.
Session metadata and device records: session start and end times and duration, IP addresses, operating system name and version, host name, CPU architecture, BIOS UUID, router MAC address, hashed hardware characteristics, and connection events.
Chat messages between Operators and Clients and session events shown in the session timeline.
Session content transmitted during Sessions (screen output, keyboard and mouse input, clipboard content, and transferred files), which is end-to-end encrypted between the Operator and Client applications, is not decrypted by the data importer, and is not stored by it.
Sensitive data transferred and applied restrictions or safeguards No special categories of personal data are requested or required by the Service. Special categories may be present in session content that the Customer transmits, which the data importer does not store, and may appear incidentally in Customer-entered fields despite Section 9.4 of the Terms and Section 3 of the DPA, which restrict what may be stored. The safeguards are the technical and organisational measures in Annex II, including end-to-end encryption of session content and its non-retention, access limited to personnel who need it, and confidentiality obligations on those personnel.
Frequency of the transfer Continuous, as driven by the Customer's use of the Service.
Nature of the processing Hosting, storage, retrieval and display of the Customer's client directory, chat messages, session events and session metadata; establishment and management of remote support sessions between the Customer's Operators and its Clients; transmission of end-to-end-encrypted session content without retention of its contents.
Purpose of the data transfer and further processing Provision of the HelpWire service to the Customer in accordance with the Terms and the DPA. No further processing takes place, other than the creation of aggregated or de-identified statistics on the instruction recorded in Section 3 of the DPA and the limited controller uses described there.
Period for which the personal data will be retained For the term of the Customer's use of the Service and until deletion under Section 11 of the DPA. Self-service deletion removes Customer Data from production systems immediately; encrypted backup snapshots expire within 7 days; IP addresses in rotating server logs are overwritten within 30 days. Where the Customer requests an export or Electronic Team terminates the account, Customer Data remains available for at least the retrieval periods stated in Section 11 of the DPA before deletion.
Transfers to sub-processors: subject matter, nature and duration Hosting of production infrastructure and operation of session relay servers by Amazon Web Services, and engineering, operations and support by individual contractors of Electronic Team, as listed in Part D, for the duration of the Service. Relay servers forward end-to-end-encrypted session traffic only.


C. Competent supervisory authority


The competent supervisory authority is determined in accordance with Clause 13 as completed in Part A.3. For transfers subject to the Swiss Federal Act on Data Protection, the Federal Data Protection and Information Commissioner is competent (Part F).

Part C. Annex II to the Clauses: technical and organisational measures

The data importer implements the technical and organisational measures described in Annex 2 of the DPA, which is incorporated here, together with the related facts stated in the Terms and the Privacy Policy. Organised under the headings in the Clauses list, those measures are as follows.



Pseudonymisation and encryption Session content (screen, input, clipboard, transferred files) is end-to-end encrypted between the Operator and Client applications using TLS 1.3 with cipher suite TLS_AES_256_GCM_SHA384 and is not decrypted at relay servers or any other data importer infrastructure. Application-to-server traffic (chat, service commands) is encrypted in transit and decrypted only on the central server. QUIC with TLS is used where UDP transport is required; web traffic runs over HTTPS and WSS. Database connections are encrypted in transit. Certain hardware characteristics in device records are stored as one-way hashes. Volume snapshots are encrypted.
Ongoing confidentiality, integrity, availability and resilience Personal data is accessible only to personnel who need it for their duties. Internal services are reachable only over the corporate VPN behind an additional authentication layer, with individual per-service credentials. Key infrastructure parameters are continuously monitored with automated alerting, and an on-call administrator team responds to incidents.
Ability to restore availability and access in a timely manner Backups of file directories and database dumps are taken every two days. Volume snapshots are encrypted and retained for a maximum of 7 days. Recovery procedures are executed manually and verified as needed.
Regular testing, assessment and evaluation of the measures The measures are reviewed and updated from time to time and whenever a significant change is made to the Service or its infrastructure.
User identification and authorisation Authentication and credential management through Clerk, with multi-factor authentication available to all user accounts. Organization owners control Operator membership and group-level client access. Clients approve attended sessions at connection time; unattended access requires permission granted in advance.
Protection of data during transmission As under pseudonymisation and encryption above. Connections are peer-to-peer by default; relay servers, used only as fallback, forward encrypted traffic without storing or decrypting it.
Protection of data during storage Encrypted backup snapshots retained for a maximum of 7 days. Production data is held on AWS infrastructure in California (us-west-1) with access restricted as described above.
Physical security of processing locations Production and relay infrastructure is hosted in Amazon Web Services data centres, which maintain physical access controls under AWS's own certifications.
Events logging Server logs (IP address, request time and URL, browser) are kept on a rotating basis of up to approximately 15 days for portal and chat services and 30 days for connection and build services. Session events are recorded in the Customer's session timeline.
System configuration, including default configuration Applications are code-signed with DigiCert certificates. A separate server distributes application builds. Service accounts are credential-protected.
Internal IT and IT security governance and management Privacy and security policies binding on employees; confidentiality obligations for staff with data access.
Certification or assurance of processes and products No third-party security certifications or attestations (such as SOC 2 or ISO 27001) are currently held. Information reasonably necessary to demonstrate compliance is made available under Section 12 of the DPA.
Data minimisation No recording or storage of session audiovisual content; transferred files and clipboard content are never stored server-side. Session metadata is limited to the items listed in Annex I.B.
Data quality Customers maintain their own client directory records and can correct them at any time in the web portal.
Limited data retention Chat messages and session events are stored for the Customer's Organization until deletion of the related record or account. Retention periods are as stated in Annex I.B and Section 11 of the DPA.
Accountability Records of processing carried out on behalf of the Customer are maintained under Article 30(2) of the GDPR (Section 5(e) of the DPA). Sub-processors are engaged under Section 7 of the DPA.
Data portability and erasure Self-service account deletion removes Customer Data from production systems immediately. Exports of Organization data in a common machine-readable format are available on request within the periods stated in Section 11 of the DPA and Section 13.4 of the Terms.
Assistance to the controller Data subject requests received directly are referred to the Customer (Section 8 of the DPA). Personal data breaches affecting Customer Data are notified without undue delay and in any event within 72 hours of the data importer becoming aware (Section 9 of the DPA).
Measures to be taken by sub-processors Amazon Web Services applies its own technical and organisational measures for the hosting services it provides, under its GDPR Data Processing Addendum. Individual contractors of Electronic Team work under the access controls described above, including the corporate VPN, the additional authentication layer and individual per-service credentials.

Part D. Annex III to the Clauses: list of sub-processors

The data exporter has authorised the use of the following sub-processors under Clause 9(a), Option 2. This list is the agreed list for the purposes of that Clause. The current list, together with a dated record of changes, is maintained at https://www.helpwire.app/legal/subprocessors/; the entries on that page identified as processing Customer Data constitute the agreed list, and changes to them are notified 14 days in advance as provided in Section 7 of the DPA.



Name Address and contact Description of processing and transfer safeguard
Amazon Web Services, Inc. 410 Terry Avenue North, Seattle, WA 98109, United States. Contact: as published at aws.amazon.com/privacy. Hosting of production infrastructure (us-west-1, California) and operation of session relay servers in 12 AWS regions worldwide. Relay servers forward end-to-end-encrypted session traffic only. Safeguard for the onward transfer: participation in the EU-U.S. Data Privacy Framework, its UK Extension and the Swiss-U.S. Data Privacy Framework, and the AWS GDPR Data Processing Addendum incorporating the Clauses.

Part E. UK International Data Transfer Addendum

For transfers of personal data that are subject to the UK GDPR from the Customer to Electronic Team, the parties enter into the International Data Transfer Addendum to the EU Commission Standard Contractual Clauses issued by the Information Commissioner under section 119A of the Data Protection Act 2018 (version B1.0, in force from 21 March 2022) (the "Addendum"). The Addendum is completed as follows.

Part 1: Tables

Table 1: Parties



Start date The date on which the Customer first uses the Service to process personal data subject to the UK GDPR (Part A.2).
The Parties Exporter (who sends the Restricted Transfer) Importer (who receives the Restricted Transfer)
Parties' details Full legal name: the Customer, as identified in the HelpWire account. Trading name (if different): as recorded in the account. Main address: as recorded in the account. Official registration number: as recorded in the account, where applicable. Full legal name: Electronic Team, Inc. Main address: 11890 Sunrise Valley Dr, Ste 111, Reston, VA 20191, United States. Official registration number: Virginia State Corporation Commission entity ID 08345597.
Key contact The Organization owner, at the email address recorded in the HelpWire account. Privacy contact, dpo@electronic.us.
Signature (if required for the purposes of Section 2) Deemed given by acceptance of the Terms (Part A.2). Deemed given under Part A.2.


Table 2: Selected SCCs, Modules and Selected Clauses



Addendum EU SCCs The version of the Approved EU SCCs to which this Addendum is appended, detailed below, including the Appendix Information: the Clauses as completed in Part A of this Annex 3, dated as of the Start date.
Module Module Two (transfer controller to processor), or Module Three (transfer processor to processor) where Part A.4 applies.
Clause 7 (docking clause) Included.
Clause 11 (option) Not included.
Clause 9(a) (prior authorisation or general authorisation) General authorisation.
Clause 9(a) (time period) 14 days.
Is personal data received from the Importer combined with personal data collected by the Exporter? Not applicable to Modules Two and Three.


Table 3: Appendix Information


"Appendix Information" means the information which must be provided for the selected modules as set out in the Appendix of the Approved EU SCCs (other than the Parties), and which for this Addendum is set out in: Annex 1A (List of Parties): Part B.A of this Annex 3. Annex 1B (Description of Transfer): Part B.B of this Annex 3. Annex II (Technical and organisational measures): Part C of this Annex 3. Annex III (List of Subprocessors): Part D of this Annex 3.


Table 4: Ending this Addendum when the Approved Addendum changes


Which Parties may end this Addendum as set out in Section 19: the Importer.

Part 2: Mandatory Clauses

The Mandatory Clauses of the Approved Addendum, being the template Addendum B.1.0 issued by the Information Commissioner and laid before Parliament in accordance with section 119A of the Data Protection Act 2018 on 2 February 2022, as it is revised under Section 18 of those Mandatory Clauses, are incorporated into this Annex 3 by reference and apply to the transfers described in this Part E.


Part F. Swiss adaptations


For transfers of personal data that are subject to the Swiss Federal Act on Data Protection of 25 September 2020 (the "FADP") from the Customer to Electronic Team, the Clauses apply as completed in Parts A to D with the following adaptations, in accordance with the guidance of the Federal Data Protection and Information Commissioner (the "FDPIC").


  • References in the Clauses to the GDPR are to be read as references to the FADP insofar as the transfer is subject to the FADP.

  • The FDPIC is the competent supervisory authority under Clause 13 and Annex I.C insofar as the transfer is subject to the FADP.

  • The term "Member State" in the Clauses is not to be interpreted so as to exclude data subjects in Switzerland from the possibility of enforcing their rights in their place of habitual residence in Switzerland under Clause 18(c).

  • References to the "European Union", the "Union" and "EU Member State" in the Clauses are to be read as including Switzerland insofar as the transfer is subject to the FADP.

  • Clause 17 (governing law) and Clause 18(b) (choice of forum) remain as completed in Part A.3, the law of Ireland being a law that allows for and grants third-party beneficiary rights, without prejudice to the rights of data subjects under Clause 18(c) as adapted above.

  • Where a transfer is subject to both the GDPR and the FADP, the Clauses apply in their EU form, and the adaptations above apply in parallel to the extent the FADP governs the transfer.

Part G. Operational terms


  1. Notices and information. Information that the data importer must provide to the data exporter under the Clauses, including under Clauses 8.6, 9(a), 9(c), 14(e), 15 and 16, is given by email to the Organization owner at the address recorded in the HelpWire account. Requests by the data exporter under the Clauses are made to the contact in Part B.A.

  2. Access requests by public authorities. The data importer's commitments under Clause 15 are performed in accordance with Section 5(f) of the DPA. The data importer will review the legality of any request under the laws of the country of destination, challenge it where there are reasonable grounds to do so, and disclose only the minimum information required.

  3. Transfer impact documentation. To support the assessment the parties are required to make under Clause 14, the data importer makes available to the data exporter, on request to the contact in Part B.A, a transfer impact support statement describing the laws and practices of the United States relevant to the transfer, the data importer's policy on government access requests, and the supplementary measures in place. The data importer will update that statement if it becomes aware of a change that affects it.

  4. Audits. The data exporter's rights under Clauses 8.9(c) and 8.9(d) are exercised in accordance with Section 12 of the DPA, provided that nothing in Section 12 limits those rights beyond what Clause 8.9 permits.

  5. Liability between the parties. Section 13 of the DPA applies to liability between the parties under the Clauses to the extent permitted by Clause 12 and does not limit the rights of data subjects under the Clauses.

  6. Termination of transfers. Where the data exporter suspends or terminates transfers under Clause 16, the DPA and the Terms continue to apply to any Customer Data already held, which will be returned or deleted in accordance with Clause 16(d) and Section 11 of the DPA.

  7. Language. This Annex 3 is drafted in English. Where the Clauses or the Addendum are required to be provided in another language, the English text prevails as between the parties to the extent permitted by law.