This Data Processing Agreement (“Agreement”) forms part of the Contract for Services under the DocEvent.io Terms of Service (the “Principal Agreement”). This Agreement is an amendment to the Principal Agreement and is effective upon its incorporation to the Principal Agreement, which incorporation may be specified in the Principal Agreement or an executed amendment to the Principal Agreement. Upon its incorporation into the Principal Agreement, this Agreement will form a part of the Principal Agreement.
We periodically update this Agreement.
The term of this Agreement shall follow the term of the Principal Agreement. Terms not defined herein shall have the meaning as set forth in the Principal Agreement.
WHEREAS
- (A) You personally or your company act as a Data Controller, or as a Data Processor on behalf of your own customers (in either case, the “Controller”).
- (B) Your company wishes to subcontract certain Services (as defined below), which imply the processing of personal data, to DocEvent Pty Ltd (ABN 30 632 307 781), trading as DocEvent.io, acting as a Data Processor or, where the Controller is itself a processor, as a sub-processor (in either case, the “Processor”).
- (C) The Parties seek to implement a data processing agreement that complies with the requirements of the current legal framework in relation to data processing and with the Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data, and repealing Directive 95/46/EC (General Data Protection Regulation).
- (D) The Parties wish to lay down their rights and obligations.
IT IS AGREED AS FOLLOWS:
1. Definitions and Interpretation
1.1 Unless otherwise defined herein, capitalized terms and expressions used in this DPA shall have the following meaning:
- 1.1.1 “Company Personal Data” means any Personal Data Processed by a Contracted Processor on Controller’s behalf pursuant to or in connection with the Principal Agreement;
- 1.1.2 “Contracted Processor” means Processor or a Subprocessor;
- 1.1.3 “Data Protection Laws” means EU Data Protection Laws, UK Data Protection Laws and, to the extent applicable, the data protection or privacy laws of any other country;
- 1.1.4 “EEA” means the European Economic Area;
- 1.1.5 “EU Data Protection Laws” means the GDPR and the laws of the Member States implementing or supplementing the GDPR, as amended, replaced or superseded from time to time;
- 1.1.5A “UK Data Protection Laws” means the UK GDPR (as defined in section 3(10) of the Data Protection Act 2018) and the Data Protection Act 2018;
- 1.1.5B “SCCs” means the standard contractual clauses for the transfer of personal data to third countries set out in the Annex to Commission Implementing Decision (EU) 2021/914 of 4 June 2021, as amended or replaced from time to time;
- 1.1.5C “UK Addendum” means the International Data Transfer Addendum to the EU Commission Standard Contractual Clauses (version B1.0) issued by the UK Information Commissioner under section 119A of the Data Protection Act 2018, as amended or replaced from time to time;
- 1.1.5D “Restricted Transfer” means a transfer of Company Personal Data to Processor that is subject to EU Data Protection Laws or UK Data Protection Laws and is made to a country that is not recognised by those laws as providing an adequate level of protection;
- 1.1.6 “GDPR” means EU General Data Protection Regulation 2016/679;
- 1.1.7 “Data Transfer” means:
- 1.1.7.1 a transfer of Company Personal Data from Controller to a Contracted Processor; or
- 1.1.7.2 an onward transfer of Company Personal Data from a Contracted Processor to a Subcontracted Processor, or between two establishments of a Contracted Processor, in each case, where such transfer would be prohibited by Data Protection Laws (or by the terms of data transfer agreements put in place to address the data transfer restrictions of Data Protection Laws);
- 1.1.8 “Services” means end-to-end encrypted data transfer services. The Service is described more in detail in Schedule 1.
- 1.1.9 “Subprocessor” means any person appointed by or on behalf of Processor to process Personal Data on behalf of Controller in connection with the Agreement.
1.2 The terms, “Commission”, “Controller”, “Data Subject”, “Member State”, “Personal Data”, “Personal Data Breach”, “Processing” and “Supervisory Authority” shall have the same meaning as in the GDPR, and their cognate terms shall be construed accordingly.
2. Processing of Company Personal Data
2.1 Processor shall:
- 2.1.1 comply with all applicable Data Protection Laws in the Processing of Company Personal Data; and
- 2.1.2 not process Company Personal Data other than on Controller’s documented instructions.
2.2 Controller instructs Processor to process Company Personal Data to provide the Services and related technical support.
3. Processor Personnel
Processor shall take reasonable steps to ensure the reliability of any employee, agent or contractor of any Contracted Processor who may have access to Company Personal Data, ensuring in each case that access is strictly limited to those individuals who need to know / access the relevant Company Personal Data, as strictly necessary for the purposes of the Principal Agreement, and to comply with Applicable Laws in the context of that individual’s duties to the Contracted Processor, ensuring that all such individuals are subject to confidentiality undertakings or professional or statutory obligations of confidentiality.
4. Security
4.1 Taking into account the state of the art, the costs of implementation and the nature, scope, context and purposes of Processing as well as the risk of varying likelihood and severity for the rights and freedoms of natural persons, Processor shall in relation to the Company Personal Data implement appropriate technical and organizational measures to ensure a level of security appropriate to that risk, including, as appropriate, the measures referred to in Article 32(1) of the GDPR.
4.2 In assessing the appropriate level of security, Processor shall take account in particular of the risks that are presented by Processing, in particular from a Personal Data Breach.
5. Subprocessing
5.1 Controller provides a general authorization for Processor to engage Subprocessors to Process Company Personal Data in order to provide the Services. The Subprocessors engaged at any time are those listed under “Service subprocessors” in Processor’s Privacy Policy (the “Subprocessor List”).
5.2 Processor will impose data-protection obligations on each Subprocessor that are no less protective than those set out in this Agreement, and Processor remains fully liable to Controller for the performance of each Subprocessor’s obligations.
5.3 At least ten (10) calendar days before a new or replacement Subprocessor begins Processing Company Personal Data, Processor will email Controller at the address associated with its account under the Principal Agreement and at any notification address registered under section 5.4, identifying the proposed Subprocessor and the Processing it will perform, and will update the Subprocessor List.
5.4 Controller may register an additional email address for notices under section 5.3 by writing to support@docevent.io. Controller is responsible for keeping its notification addresses current.
5.5 Controller may object to a proposed Subprocessor on reasonable data-protection grounds by email to support@docevent.io before the end of the notice period in section 5.3. The Parties will discuss the objection in good faith. If the objection remains unresolved, Controller may cancel the affected Services with effect before that Subprocessor Processes Controller’s Company Personal Data. Cancellation is Controller’s sole commercial remedy for the proposed change, without limiting any rights under the SCCs or the UK Addendum.
6. Data Subject Rights
6.1 Taking into account the nature of the Processing, Processor shall assist Controller by implementing appropriate technical and organisational measures, insofar as this is possible, for the fulfilment of Controller obligations, as reasonably understood by Controller, to respond to requests to exercise Data Subject rights under the Data Protection Laws.
6.2 Processor shall:
- 6.2.1 promptly notify Controller if it receives a request from a Data Subject under any Data Protection Law in respect of Company Personal Data; and
- 6.2.2 ensure that it does not respond to that request except on the documented instructions of Controller or as required by Applicable Laws to which the Processor is subject, in which case Processor shall to the extent permitted by Applicable Laws inform Controller of that legal requirement before the Contracted Processor responds to the request.
7. Personal Data Breach
7.1 Processor shall notify Controller without undue delay upon Processor becoming aware of a Personal Data Breach affecting Company Personal Data, providing Controller with sufficient information to allow Controller to meet any obligations to report or inform Data Subjects of the Personal Data Breach under the Data Protection Laws.
7.2 Processor shall co-operate with Controller and take reasonable commercial steps as are directed by Controller to assist in the investigation, mitigation and remediation of each such Personal Data Breach.
7.3 Processor shall indemnify, defend, and hold harmless Controller (and its affiliates, officers, directors, agents and employees) from and against any and all claims, costs, damages, losses, liabilities and expenses (including reasonable attorneys’ fees and costs) resulting from any third-party claim or action arising from or related to a Personal Data Breach affecting Company Personal Data.
7.4 Subject to section 11.4 and to any liability that cannot lawfully be limited, Processor’s total aggregate liability arising out of or related to this Agreement, including under section 7.3 and including liability for negligence, will not exceed the fees actually paid or payable by Controller to Processor under the Principal Agreement in the six (6) months immediately preceding the event giving rise to the claim.
8. Data Protection Impact Assessment and Prior Consultation
8.1 Processor shall provide reasonable assistance to Controller with any data protection impact assessments, and prior consultations with Supervising Authorities or other competent data privacy authorities, which Controller reasonably considers to be required by article 35 or 36 of the GDPR or equivalent provisions of any other Data Protection Law, in each case solely in relation to Processing of Company Personal Data by, and taking into account the nature of the Processing and information available to, the Contracted Processors.
9. Deletion or return of Company Personal Data
9.1 Company Personal Data that the Services hold transiently, such as Channels file contents and transfer logs, is deleted automatically on the schedule set out in Schedule 3. Closing an account disables access to the Services but does not by itself delete the account record.
9.2 After the cessation of any Services involving the Processing of Company Personal Data, Processor shall, on Controller’s written request to support@docevent.io, delete the remaining Company Personal Data relating to those Services within 30 days of the request, except:
- (a) data that Processor must retain to comply with applicable law, such as billing and tax records, which Processor will retain only for the period required and protect in accordance with this Agreement; and
- (b) copies held in logs or backups, which are deleted on their ordinary retention schedule.
9.3 On request, Processor will confirm to Controller in writing that it has complied with section 9.2.
10. Audit rights
10.1 Subject to this section 10, Processor shall make available to Controller on request all information necessary to demonstrate compliance with this Agreement, and shall allow for and contribute to audits, including inspections, by Controller or an auditor mandated by Controller in relation to the Processing of the Company Personal Data by the Contracted Processors.
10.2 Information and audit rights of Controller only arise under section 10.1 to the extent that the Agreement does not otherwise give them information and audit rights meeting the relevant requirements of Data Protection Law.
11. Data Transfer
11.1 Processor hosts Company Personal Data in the data centre region selected by Controller, and offers regions within the European Economic Area (EEA). Processor is established in Australia, which is not recognised as providing an adequate level of protection under EU Data Protection Laws or UK Data Protection Laws. Account information and support access are handled from outside the EEA as described in Schedule 3, so the Processing involves Restricted Transfers whatever region Controller selects.
11.2 EU transfers. Each Restricted Transfer subject to EU Data Protection Laws is governed by the SCCs, which are incorporated into this Agreement by reference, with Controller as “data exporter” and Processor as “data importer”, as follows:
- (a) Module Two (controller to processor) applies where Controller is a controller, and Module Three (processor to processor) applies where Controller is a processor;
- (b) the optional docking clause in Clause 7 applies;
- (c) Option 2 of Clause 9(a) (general written authorisation) applies, and the time period for prior notice is the period set out in section 5.3;
- (d) the optional wording in Clause 11(a) does not apply;
- (e) the competent supervisory authority is determined in accordance with Clause 13(a), as set out in Schedule 3;
- (f) for Clause 17, Option 1 applies and the governing law is the law of Ireland;
- (g) for Clause 18(b), the courts of Ireland have jurisdiction;
- (h) Annexes I, II and III of the SCCs are completed by Schedule 3.
11.3 UK transfers. Each Restricted Transfer subject to UK Data Protection Laws is governed by the SCCs as set out in section 11.2, as varied by the UK Addendum, which is incorporated into this Agreement by reference. For the UK Addendum: Table 1 is completed with the Parties’ details in Schedule 3; Table 2 is completed by section 11.2; Table 3 is completed by Schedule 3; and for Table 4, the Importer may end the UK Addendum as set out in its Section 19. The UK Addendum is governed by the law of England and Wales, and disputes under it are resolved by the courts of England and Wales.
11.4 If there is any conflict between this Agreement (or the Principal Agreement) and the SCCs or the UK Addendum, the SCCs or the UK Addendum (as applicable) prevail to the extent of the conflict.
11.5 The Parties enter into the SCCs and the UK Addendum, as completed by this Agreement, when this version of this Agreement becomes binding under the Principal Agreement. That date is the date of signature of the SCCs and the Start Date of the UK Addendum.
11.6 If the SCCs or the UK Addendum are amended or replaced, Processor may update this section 11 to adopt the amended or replacement version, and that update takes effect as a change to this Agreement under the Principal Agreement.
12. General Terms
12.1 Confidentiality. Each Party must keep any information it receives about the other Party and its business in connection with this Agreement (“Confidential Information”) confidential and must not use or disclose that Confidential Information without the prior written consent of the other Party except to the extent that:
- (a) disclosure is required by law;
- (b) the relevant information is already in the public domain.
12.2 Notices. All notices and communications given under this Agreement must be in writing and will be sent by email. Controller shall be notified by email sent to the address related to its use of the Service under the Principal Agreement and to any notification address registered under section 5.4. Processor shall be notified by email sent to the address: support@docevent.io
13. Governing Law and Jurisdiction
13.1 This Agreement is governed by and construed in accordance with the laws of the State of New South Wales, Australia, consistent with the Principal Agreement, except that the SCCs and the UK Addendum are governed by the law, and subject to the jurisdiction, set out in section 11.
13.2 Any dispute arising in connection with this Agreement, which the Parties are unable to resolve amicably, will be submitted to the exclusive jurisdiction of the courts of Sydney, New South Wales, Australia.
Schedule 1: Service Description
The Service offered by DocEvent.io is DocEvent (“DocEvent”). DocEvent provides B2B data transfer services with an easy-to-use interface that connects endpoint protocols such as FTP, FTPS and SFTP to blob and file storage systems in the cloud, such as Amazon S3, Azure Blob Storage, Google Cloud Storage and S3-compatible storage. DocEvent comprises two principal services, which handle Company Personal Data differently:
Simple FTP Service (SFS)
The Simple FTP Service generally streams data directly between the Controller’s protocol client (FTP/FTPS/SFTP) and the Controller’s own cloud storage. Two exceptions apply: uploads to Azure Files storage are staged in a temporary file on the server, which is removed when the upload operation ends; and free test services store files in DocEvent-managed storage, where they are deleted automatically after one day. DocEvent does not otherwise retain the contents of transferred files. Data is encrypted in transit where the Controller uses an encrypted protocol (FTPS or SFTP). Transfer metadata (such as filename, file size, date and time, and operation type) is logged for the purposes of usability, billing and logging.
Channels
The Channels service routes and delivers files between parties. To perform this routing and delivery, file contents may be stored transiently in an encrypted, DocEvent-managed cloud storage bucket (Amazon S3 with server-side encryption) for the duration of the transfer and routing process, after which they are deleted in accordance with the applicable retention lifecycle. As with SFS, data is encrypted in transit and only transfer metadata is retained for usability, billing and logging.
Schedule 2: Data Processing and Security
1. Description of the data processing carried out on behalf of the Controller
In addition to the information provided elsewhere in the Agreement, the Parties wish to document the following information in relation to the data processing activities.
The data processing performed by the Data Processor on behalf of the Controller relates to the service of end-to-end data transfer. The data processing details and procedure can be found in the Company’s Privacy Policy document listed on the main website.
Schedule 3: Transfer Details (Annexes to the SCCs)
Annex I.A: List of Parties
Data exporter: Controller, as identified by the name, address and contact details associated with its account under the Principal Agreement. Role: controller (Module Two) or processor (Module Three). Activities relevant to the transfer: use of the Services. Signature and date: as set out in section 11.5.
Data importer: DocEvent Pty Ltd (ABN 30 632 307 781), trading as DocEvent.io, PO Box 3015, Rouse Hill NSW 2155, Australia. Contact for data protection matters: support@docevent.io. Role: processor (Module Two) or sub-processor (Module Three). Activities relevant to the transfer: provision of the Services described in Schedule 1. Signature and date: as set out in section 11.5.
Annex I.B: Description of Transfer
- Categories of data subjects: Controller’s users of the Services (including the users of its SFS services), and any individuals whose personal data is contained in files that Controller transfers using the Services.
- Categories of personal data: account and contact details (name, email address, username); service usernames; IP addresses and connection details; transfer metadata (filename, file size, date and time, and operation type); and the contents of files that Controller transfers, which Processor does not inspect.
- Sensitive data: none intended. If Controller transfers files containing special categories of data, the measures in Annex II apply to them.
- Frequency of the transfer: continuous, for as long as Controller uses the Services.
- Nature of the processing: receiving, transmitting, routing and logging files and transfer metadata, and storing account information, as described in Schedule 1.
- Purpose of the transfer and further processing: to provide the Services, including support, billing and security.
- Retention: SFS file contents are handled as described in Schedule 1. Channels file contents are deleted automatically within 2 days of receipt. Transfer logs are deleted after 120 days. Account information is kept while the account exists and, after closure, until deleted on request under section 9. Billing records are kept for as long as the law requires.
- Transfers to Subprocessors: for the subject matter, nature and duration set out in this Annex, to the Subprocessors listed in Annex III.
- Location of processing: file transfer and transfer logs are processed in the data centre region selected by Controller. Account information is held in the United States (AWS us-east-1). Support and operations staff access the Services from Australia.
Annex I.C: Competent Supervisory Authority
The competent supervisory authority is determined in accordance with Clause 13(a) of the SCCs, by reference to the data exporter’s establishment or representative or, where it has neither, the Member State in which the relevant data subjects are located, as confirmed by the data exporter. For transfers under the UK Addendum, it is the UK Information Commissioner’s Office.
Annex II: Technical and Organisational Measures
- Encryption in transit: TLS for the web console and APIs, and TLS (FTPS) or SSH (SFTP) for file transfer where Controller uses those protocols.
- Encryption at rest: server-side encryption of DocEvent-managed storage, and encryption of stored destination credentials with keys held in AWS Key Management Service.
- Data minimisation: SFS file contents are handled as described in Schedule 1, and Channels files expire automatically.
- Data location: Controller chooses the data centre region for its services.
- Access control: least-privilege access for systems and personnel, separate credentials for each internal service, and authentication of requests to customer data.
- Network protection: firewalls, IP allowlisting for administrative systems, and protection against repeated failed sign-in attempts.
- Logging and monitoring: logging of transfers and administrative actions, with automated health and security monitoring.
- Incident response: breach notification under section 7 of this Agreement.
- Deletion: deletion of Company Personal Data under section 9 of this Agreement.
Annex III: List of Subprocessors
The Subprocessors authorised by Controller are those on the Subprocessor List referred to in section 5.1, as updated in accordance with section 5.3.
For any questions contact support@docevent.io