Data processing agreement

Draft for counsel. Not in force.

Last updated: [date set by counsel].

This data processing agreement (the "DPA") forms part of the agreement between Atlas Meridian Inc. and the customer for Atlas Meridian Deal Intelligence (the "Agreement"). Terms not defined here have the meaning given in the Agreement. If the two conflict on personal information, this DPA governs.

1. Definitions

In this DPA:

  • "Affiliate" means an entity that controls, is controlled by, or is under common control with another entity. Control means the power to direct its management, by ownership of voting securities, by contract or otherwise.
  • "Applicable Data Protection Laws" means the laws on personal information that apply to the processing under the Agreement. These include PIPEDA, PIPA and, where Annex 2 or Annex 3 applies, the laws named there.
  • "Controller" means the party that decides why and how personal information is processed. Under PIPA and PIPEDA, this is the organization that has control of the information.
  • "Data Subject" means the identifiable individual that the personal information is about.
  • "Information Security Incident" means a breach of Atlas Meridian's safeguards that leads to loss of, or unauthorized access to, personal information held for the customer. Failed log-in attempts, port scans and other unsuccessful attacks are not Information Security Incidents.
  • "PIPA" means Alberta's Personal Information Protection Act. "PIPEDA" means Canada's Personal Information Protection and Electronic Documents Act. Each includes its regulations and any replacement law.
  • "Personal Information" means information about an identifiable individual that is part of Customer Content. It does not include information that Atlas Meridian receives from another source, independent of its relationship with the customer.
  • "Process" means any operation on personal information, such as collecting, storing, using, disclosing, combining or deleting it.
  • "Processor" means the party that processes personal information on behalf of the Controller. This includes a "service provider" under PIPA or a US state privacy law.
  • "Regulator" means a body with power to enforce Applicable Data Protection Laws.
  • "Restricted Transfer" means a transfer that a law outside Canada restricts without a lawful transfer mechanism. Examples are transfers from the European Economic Area, the United Kingdom or Switzerland.
  • "SCCs" means the standard contractual clauses approved by the European Commission in Decision (EU) 2021/914.
  • "Security Measures" has the meaning in Section 4.1.
  • "Services" means the services Atlas Meridian provides to the customer under the Agreement.
  • "Subprocessor" means a third party that Atlas Meridian engages to process personal information for the Services.
  • "UK Addendum" means the international data transfer addendum to the SCCs issued by the UK Information Commissioner's Office.

2. Duration and scope

2.1 This DPA stays in effect while Atlas Meridian processes personal information, even after the Agreement ends.

2.2 Annex 2 applies to personal information that is subject to European or UK data protection law.

2.3 Annex 3 applies to personal information under a United States state privacy law. It applies where the customer is a business or controller and Atlas Meridian is its service provider or processor.

2.4 The order form may extend this DPA to other jurisdictions.

3. Customer instructions

3.1 Atlas Meridian processes personal information only on the customer's documented instructions. By signing the Agreement, the customer instructs Atlas Meridian to process personal information to provide the Services and to meet its duties under the Agreement.

3.2 Annex 1 describes the processing and the role of each party. In the processing described there, the customer is the Controller and Atlas Meridian is the Processor.

3.3 Atlas Meridian tells the customer if it believes an instruction breaks Applicable Data Protection Laws. It may pause that processing until the customer confirms or changes the instruction.

4. Security

4.1 Security measures

Atlas Meridian maintains reasonable administrative, technical and physical safeguards to protect personal information against Information Security Incidents. Annex 4 describes them (the "Security Measures"). Atlas Meridian may update the Security Measures, if the update does not materially reduce the protection of personal information.

4.2 Staff

Atlas Meridian limits access to personal information to staff who need it for the Services. Those staff are bound by written confidentiality obligations.

4.3 Information Security Incidents

Atlas Meridian notifies the customer without undue delay after it becomes aware of an Information Security Incident. The notice describes the available facts, the steps taken to reduce harm, and the steps Atlas Meridian recommends the customer take.

Atlas Meridian cooperates with the customer's investigation and takes the reasonable steps the customer directs. A notice or response is not an admission of fault or liability.

The customer is responsible for any notice to a Regulator, a Data Subject or the public that the law requires of the customer. Where such a notice names Atlas Meridian, the customer gives Atlas Meridian advance notice where the law allows. The customer also considers in good faith any correction Atlas Meridian reasonably requests about its own role.

4.4 Customer responsibilities for security

The customer is responsible for its use of the Services. This includes using them in a way that fits the risk to its data, and protecting its account credentials, systems and devices. It also includes keeping its own copies of personal information.

4.5 Customer assessment

The customer has reviewed the Security Measures and this DPA. It has decided they meet its needs, including any security duties it has under Applicable Data Protection Laws.

5. Data subject rights

5.1 Individuals may ask the customer for access to their personal information, for correction, or for deletion. Atlas Meridian gives the customer the help that is reasonably necessary and technically possible to answer those requests.

5.2 The customer pays for that help at Atlas Meridian's then-current professional services rates, which Atlas Meridian provides on request. The customer stays responsible for its own compliance with Applicable Data Protection Laws.

5.3 If an individual sends a request directly to Atlas Meridian, Atlas Meridian notifies the customer and tells the individual to contact the customer. The customer is responsible for the response.

6. Customer responsibilities

6.1 The customer is responsible for the notices, consents or other lawful authority that the law requires for the processing the Agreement describes. This includes authority to disclose personal information in a data room for the purpose of a business transaction, where PIPA or PIPEDA permits it.

6.2 Customers upload data rooms from sellers, and those data rooms can hold personal information such as landowner names, employee lists and contact details. The customer represents that it has the right to upload that personal information and to have Atlas Meridian process it.

6.3 The customer must not knowingly upload any of the following, unless the order form allows it.

  • Health information.
  • Government identification numbers.
  • Financial account numbers and account log-in details.
  • Biometric or genetic data.
  • Personal information about children.
  • Precise location data about an individual.

If a data room holds such information, the customer must tell Atlas Meridian and agree the extra safeguards in writing before upload. Other categories that a law treats as sensitive are covered by the same rule.

6.4 The customer represents that it has a lawful basis for the processing and that its instructions are lawful. It also represents that individuals received the notices the law requires.

7. Subprocessors

7.1 General authorization

The customer generally authorizes Atlas Meridian to engage Subprocessors under this Section 7. Atlas Meridian may keep using the Subprocessors it engaged on the date of this DPA.

7.2 Information about Subprocessors

Atlas Meridian does not publish the names of its Subprocessors on this website. The current list, with their functions and locations, is available on request at [email protected]. A customer may ask to be told when the list changes.

7.3 Requirements

Atlas Meridian signs a written contract with each Subprocessor. The contract holds data protection duties no less protective than those in this DPA, as far as the Subprocessor's services allow. Atlas Meridian is liable for each Subprocessor's acts and omissions to the same extent as for its own.

7.4 Notice and objection

Atlas Meridian gives the customer 30 calendar days' written notice before a new Subprocessor starts to process personal information. The notice names the Subprocessor, its location and its activities. Atlas Meridian may send it by email or by another written means.

The customer may object in writing within 10 days of the notice. The objection must be made in good faith. It must give evidence that the new Subprocessor would put the customer in material breach of Applicable Data Protection Laws. It must also show that the breach cannot be avoided.

If the customer objects on those grounds, Atlas Meridian uses reasonable efforts to offer a commercially reasonable change that avoids the new Subprocessor. Suppose it cannot do so within 30 days of the objection, or the customer declines the cost of the change. Then the customer may end the affected Services, and only those Services, by giving at least 30 days' written notice. That is the customer's only remedy. The customer pays all amounts due up to the end date.

If the customer does not object within the 10 days, it is treated as having approved the new Subprocessor.

8. Audits

8.1 The customer may audit Atlas Meridian's compliance with this DPA once a year. It may also audit on other occasions that Applicable Data Protection Laws require, or after an Information Security Incident. Atlas Meridian gives the information and help reasonably needed for the audit. Because the Services are delivered remotely, an audit is done by documents and interviews and not by an on-site visit, unless a Regulator requires one.

8.2 To request an audit, the customer sends Atlas Meridian a proposed audit plan at least two weeks before the proposed start date. The plan states the scope, the length and the start date. Atlas Meridian reviews the plan, raises any concern, and works with the customer to agree a final plan.

8.3 Any third-party auditor must sign a confidentiality agreement that both parties accept. Atlas Meridian may object to an auditor that is not independent, that competes with Atlas Meridian, or that is clearly unsuitable. The customer then names another auditor or performs the audit itself.

8.4 Nothing in this Section 8 requires Atlas Meridian to breach a duty of confidence, or to give access to information about its other customers.

8.5 An independent audit report may cover the controls in question. If it was issued in the 12 months before the request, and those controls have not materially changed, the customer accepts it instead.

8.6 An audit takes place in business hours, follows the agreed plan, and does not unreasonably disrupt Atlas Meridian's business. The customer promptly tells Atlas Meridian of any non-compliance it finds. It gives Atlas Meridian a copy of the audit report unless the law prohibits it. The customer may use the report only to meet its regulatory duties or to confirm compliance with this DPA.

8.7 The customer pays the cost of the audit. It also reimburses Atlas Meridian's time and its third-party costs for the audit, at Atlas Meridian's then-current professional services rates, which are available on request.

9. Return and deletion

9.1 The Services that involve personal information may end (the "Cessation Date"). Atlas Meridian then stops processing that personal information, except to store it or as this DPA allows. This Section 9 does not apply to usage data that does not identify an individual.

9.2 The customer may ask in writing, within 14 days of the Cessation Date, for return or deletion of its personal information. Where technically possible, Atlas Meridian does one of the following within 14 days of the request. The customer elects which.

  • It returns a complete copy of the structured personal information by an agreed file transfer method. It then deletes or anonymizes all other copies.
  • It deletes or anonymizes the structured personal information.

9.3 The customer may give no instruction within the 14 days. Atlas Meridian then deletes or anonymizes the structured personal information promptly after that period, as far as is technically possible.

9.4 Atlas Meridian may keep personal information where the law permits or requires it, and for as long as the law allows. In that case it protects the information with reasonable safeguards and uses it only for the legal purpose of the retention.

9.5 Atlas Meridian confirms deletion in writing on the customer's written request.

10. Miscellaneous

10.1 Except as this DPA changes them, the terms of the Agreement stay in full force. Atlas Meridian's access to personal information is not part of the payment the customer makes under the Agreement.

10.2 Atlas Meridian may give notices under this DPA by any method the Agreement allows. It may also write to its usual contacts, or to an email address the customer gave for service notices. The customer is responsible for keeping those addresses current.

10.3 Atlas Meridian cooperates in good faith on amendments that are reasonably needed to meet Applicable Data Protection Laws.

10.4 Atlas Meridian may vary this DPA on notice to the extent it reasonably considers necessary to meet Applicable Data Protection Laws. This includes replacing the SCCs as Annex 2 describes.

10.5 If the DPA and the Agreement conflict, the DPA governs. If any SCCs apply and conflict with this DPA or the Agreement, the SCCs govern for the transfer they cover.

10.6 This DPA is governed by the laws of the Province of Alberta and the federal laws of Canada that apply there. This does not change the law that governs the SCCs under Annex 2. The courts of Alberta have jurisdiction, as the Agreement provides.

11. Limitation of liability

Each party's liability under the Agreement, this DPA and the SCCs (where they apply) is subject to the limits and exclusions in the Agreement. Nothing in this Section 11 limits the liability of any person to Data Subjects under the third-party beneficiary terms of the SCCs.

Annex 1: Processing details

ItemDetail
Atlas Meridian (data importer)Atlas Meridian Inc., Calgary, Alberta. Role: Processor.
Contact for data protection[email protected]
Customer (data exporter)The party to the Agreement, at the address and with the contact in the order form. Role: Controller.
Atlas Meridian activitiesProviding Atlas Meridian Deal Intelligence, a subscription service for due diligence on oil and gas packages in Alberta.
Customer activitiesUsing the Services to review packages it is evaluating for acquisition.
Categories of Data SubjectsIndividuals named in data rooms the customer uploads, such as landowners, current and former employees, contractors and business contacts. Also the customer's authorized users.
Categories of personal informationNames, contact details, job titles, and land or property references linked to an individual. Account details of authorized users.
Sensitive informationNone intended. See Section 6.3. Where the order form allows it, the extra safeguards agreed there apply.
Frequency of processingContinuous, as the customer uses the Services.
Nature and purposeStoring, reading, organizing and analyzing uploaded documents, and showing the results to the customer, to provide the Services and follow the customer's instructions.
Duration and retentionThe term of the Agreement, then as Section 9 provides.
SubprocessorsAs listed from time to time under Section 7.2.

Annex 2: European and UK transfers

1. This Annex applies to a Restricted Transfer from the customer to Atlas Meridian.

2. For a transfer from the European Economic Area, the SCCs are incorporated into this DPA. Module Two applies where the customer is a Controller. Module Three applies where the customer is itself a Processor.

3. The following choices apply to the SCCs.

  • The optional docking clause in Clause 7 is not used;.
  • Clause 9 uses general written authorization, with the notice period in Section 7.4;.
  • The optional language in Clause 11 is not used;.
  • The SCCs are governed by the law of Ireland, and the courts of Ireland resolve disputes under Clause 18;.
  • Annex I of the SCCs is completed from Annex 1 of this DPA, and Annex II from Section 4 and Annex 4.

4. For a transfer from the United Kingdom, the SCCs apply as varied by the UK Addendum. Its tables are completed from Annex 1, and the parties accept its mandatory clauses.

5. For a transfer from Switzerland, the SCCs apply with references to the GDPR read as references to the Swiss Federal Act on Data Protection. The Swiss Federal Data Protection and Information Commissioner is the supervisory authority.

6. Atlas Meridian may replace the SCCs on notice with a new form approved by the relevant authority, or with another lawful transfer mechanism.

7. Atlas Meridian gives the customer a signed copy of the completed SCCs on written request. This applies if a Regulator, an individual or another controller asks the customer for one.

Annex 3: United States state privacy laws

1. This Annex applies to personal information that a United States state privacy law governs. Its terms have the meaning that law gives them.

2. Atlas Meridian is the customer's service provider or processor. The customer discloses personal information only for the limited purposes in the Agreement.

3. Atlas Meridian does not sell or share the personal information. It does not use it for targeted advertising. It does not keep, use or disclose it outside the direct business relationship with the customer, or for any purpose other than providing the Services.

4. Atlas Meridian does not combine the personal information with information from another source, except as the law allows a service provider or processor to do.

5. Atlas Meridian complies with the obligations that apply to it under those laws. It tells the customer in writing if it can no longer meet them. The customer may take reasonable steps, on notice, to stop and fix unauthorized use.

6. Notice under Section 7 meets any duty to give notice of, and a chance to object to, a Subprocessor. An audit under Section 8 meets the customer's right to assess Atlas Meridian's compliance.

Annex 4: Security measures

Atlas Meridian applies the following measures, described in general terms.

  • Access to personal information is limited to staff who need it for the Services.
  • Staff are bound by confidentiality obligations.
  • Atlas Meridian applies reasonable administrative, technical and physical safeguards that fit the sensitivity of the information.
  • Atlas Meridian keeps an incident response process to detect, investigate, contain and report Information Security Incidents.
  • Atlas Meridian keeps backups and a plan to restore the Services after an outage.
  • Customer data is not used to train any model.
  • Models run inside Atlas Meridian's private cloud environment.