• Про програму
    • Склад команди
    • Про програму
    • Зв'язатись
  • Try it for Free
  • Увійти
  • Зареєструватись

DATA PROCESSING AGREEMENT

Institutional controller–processor agreement | applicable data protection laws

WORKING MASTER — 19 November 2026 | Complete Annex 1 and outstanding legal and operational checks before signature

This Data Processing Agreement (the “DPA”) is entered into on [effective date] between:

(1) [Customer full legal name], a [entity type] established under the laws of [jurisdiction], with its principal address at [address] and registration number [number, if applicable] (the “Customer”); and

(2) Smartsettle Resolutions Inc. (SRI), a company incorporated under the laws of British Columbia, Canada, of 32855 Capilano Place, Abbotsford BC V2S 7B4, Canada.

each a "Party" and together the "Parties".

Background

(A) The Parties have entered, or intend to enter, into an agreement under which SRI provides the Smartsettle platform and related services to the Customer (the "Principal Agreement").

(B) In performing the Principal Agreement, SRI processes personal data on behalf of the Customer.

(C) This DPA sets out the parties’ obligations for processing Customer Personal Data and is intended to meet applicable controller–processor contracting requirements, including Article 28(3) of the UK GDPR or EU GDPR where applicable.

1. Definitions and interpretation

1.1 In this DPA the following terms have the following meanings:

  • "Customer Personal Data" means personal data processed by SRI on behalf of the Customer under or in connection with the Principal Agreement, as further described in Annex 1;
  • “Data Protection Legislation” means all privacy and data protection laws applicable to the processing described in Annex 1, including, where applicable, the UK GDPR, the UK Data Protection Act 2018, Regulation (EU) 2016/679 (EU GDPR), relevant EEA Member State laws, and applicable Canadian federal or provincial privacy legislation;
  • "EU SCCs" means the standard contractual clauses annexed to Commission Implementing Decision (EU) 2021/914 of 4 June 2021;
  • "Restricted Transfer" means a transfer of Customer Personal Data to a country or territory not the subject of an adequacy decision or adequacy regulations applicable to that transfer;
  • "Sub-processor" means any third party engaged by SRI to process Customer Personal Data;
  • “UK Addendum” means the UK International Data Transfer Addendum to the EU SCCs, as issued and amended by the UK Information Commissioner, where applicable;
  • The terms “controller”, “processor”, “data subject”, “personal data”, “personal data breach” and “processing” have the meanings given under the applicable Data Protection Legislation. Where local legislation uses different terminology, the closest equivalent applies.

1.2 This DPA is incorporated into and forms part of the Principal Agreement. Where there is a conflict between this DPA and any other part of the Principal Agreement in relation to the processing of personal data, this DPA prevails.

1.3 Where the EU SCCs or the UK Addendum apply and conflict with this DPA, the EU SCCs or the UK Addendum prevail.

1.4 Headings are for convenience only and do not affect interpretation. References to a statute include any amendment or re-enactment of it.

2. Status and responsibilities of the Parties

2.1 For the Customer Personal Data identified in Annex 1, the Customer acts as controller and SRI acts as processor, unless Annex 1 identifies a different lawful allocation of roles for a distinct processing activity. The parties shall document any independent-controller or joint-controller activity separately rather than assume it is covered by this processor agreement.

2.2 SRI may act as an independent controller for its own business contacts, billing and other genuinely independent administrative processing, as described in its Privacy Notice. Operational logs or account information processed on the Customer’s behalf remain Customer Personal Data even where used to secure or maintain the service. SRI may use genuinely anonymous, aggregated statistics that identify neither the Customer nor an individual.

2.3 Nothing in this DPA constitutes the Parties as joint controllers.

2.4 The Customer is responsible for identifying an applicable lawful basis and, where required, any special-category condition for the processing it instructs, for giving appropriate privacy information to data subjects, and for the lawfulness of its instructions and submitted data. SRI remains responsible for its own obligations as processor under applicable law.

3. Processing on documented instructions

3.1 SRI shall process Customer Personal Data only on the documented instructions of the Customer, including in relation to transfers to a third country, unless required to do so by law to which SRI is subject. In that case SRI shall inform the Customer of that legal requirement before processing, unless the law prohibits such information on important grounds of public interest.

3.2 The Principal Agreement, this DPA and the completed Annex 1 constitute the Customer’s documented instructions at commencement. Further instructions shall be given in writing to the contact identified in Annex 1. Any additional work outside the agreed services may be subject to a fee agreed in advance.

3.3 SRI shall immediately inform the Customer if, in its opinion, an instruction infringes the Data Protection Legislation and may suspend performance of that instruction until the matter is resolved.

3.4 SRI shall not sell, rent or otherwise make Customer Personal Data available to any third party for that party’s own purposes; shall not use Customer Personal Data to train, fine-tune, evaluate or otherwise develop any machine learning or artificial intelligence model; and shall not use Customer Personal Data for any purpose of its own other than as permitted by clause 2.2. Aggregated statistics derived from the service may be used by SRI only where they do not permit the identification of any data subject or of the Customer.

4. Confidentiality and personnel

4.1 SRI shall ensure that persons authorised to process Customer Personal Data are bound by an appropriate duty of confidentiality, whether contractual or statutory, that survives the end of their engagement.

4.2 SRI shall limit access to Customer Personal Data to personnel who require it to perform their duties under the Principal Agreement. SRI shall ensure that such personnel are informed of their confidentiality and data protection obligations and receive security guidance appropriate to their responsibilities.

4.3 SRI shall take reasonable steps to ensure the reliability of any person with access to Customer Personal Data.

5. Security

5.1 SRI shall implement and maintain the technical and organisational measures set out in Annex 2, and such further measures as are appropriate to ensure a level of security appropriate to the risk, having regard to the state of the art, the costs of implementation, and the nature, scope, context and purposes of the processing.

5.2 SRI shall not materially reduce the overall level of security provided by the measures in Annex 2 during the term of this DPA.

5.3 The Customer is responsible for its own configuration of the service, including the management of its administrator accounts, the access rights it grants to its users, and the content its users choose to upload.

6. Sub-processors

6.1 The Customer gives SRI general written authorisation to engage the Sub-processors listed in Annex 3.

6.2 SRI shall give the Customer at least 30 days’ prior written notice of any intended addition or replacement of a Sub-processor. The Customer may object on reasonable data protection grounds within that period. If the Parties cannot resolve the objection, the Customer may terminate the affected part of the Principal Agreement without penalty on written notice, and SRI shall refund any prepaid fees for the unexpired term.

6.3 SRI shall impose on each Sub-processor, by written contract, data protection obligations no less protective than those in this DPA and shall remain fully liable to the Customer for the performance of each Sub-processor’s obligations.

6.4 SRI shall maintain an up-to-date list of Sub-processors and make it available to the Customer on request.

7. Assistance with data subject rights

7.1 Taking into account the nature of the processing, SRI shall assist the Customer by appropriate technical and organisational measures, insofar as this is possible, in fulfilling the Customer’s obligation to respond to requests to exercise data subject rights under Chapter III of the UK GDPR or the EU GDPR.

7.2 Where the service provides functionality enabling the Customer to access, retrieve, correct or delete Customer Personal Data, the Customer shall use that functionality where reasonably practicable. Where such functionality is unavailable or insufficient, SRI shall provide reasonable assistance in accordance with clause 7.1.

7.3 If SRI receives a request directly from a data subject relating to Customer Personal Data, it shall notify the Customer without undue delay and in any event within three business days, shall not respond substantively to the request other than to confirm that it has been referred to the Customer, and shall await the Customer’s instructions.

8. Assistance with Articles 32 to 36

8.1 Taking into account the nature of the processing and the information available to it, SRI shall provide reasonable assistance to the Customer in ensuring compliance with its obligations under Articles 32 to 36, including in relation to security, personal data breach notification, data protection impact assessments and prior consultation with a supervisory authority.

8.2 SRI shall provide the Customer, on request, with the information reasonably required to complete a data protection impact assessment in respect of the service.

9. Personal data breach

9.1 SRI shall notify the Customer without undue delay after becoming aware of a personal data breach affecting Customer Personal Data. SRI shall endeavour to provide an initial notification within 24 hours, even if its investigation is incomplete, and shall provide further information as it becomes available.

9.2 The notification shall describe, so far as known: the nature of the breach including the categories and approximate number of data subjects and records concerned; the likely consequences; the measures taken or proposed to address the breach and mitigate its effects; and the name and contact details of a point of contact at SRI. Where the information is not all available at once, it shall be provided in phases without undue further delay.

9.3 SRI shall co-operate with the Customer and take such reasonable steps as the Customer directs to assist in the investigation, mitigation and remediation of the breach.

9.4 SRI shall not notify any supervisory authority or data subject of a breach affecting Customer Personal Data without the Customer’s prior written consent, unless required to do so by law.

10. Return and deletion

10.1 On termination or expiry of the Principal Agreement, SRI shall, at the Customer’s election, delete or return all Customer Personal Data and delete all existing copies, unless storage is required by law to which SRI is subject.

10.2 The Customer shall notify SRI of its election within 30 days of termination or expiry. If no election is made, SRI shall retain the data for a further 30 days to allow the Customer to export it, and shall then delete it.

10.3 Customer Personal Data held in routine backups shall be deleted in accordance with SRI’s ordinary backup cycle, and in any event within 90 days of the date of deletion under clause 10.1. Until deleted, that data remains subject to this DPA and shall not be actively processed.

10.4 SRI shall certify deletion in writing on the Customer’s written request.

11. Records, information and audit

11.1 SRI shall maintain a written record of the categories of processing carried out on behalf of the Customer, as required by Article 30(2), and shall make available to the Customer all information necessary to demonstrate compliance with Article 28.

11.2 SRI shall allow for and contribute to audits, including inspections, conducted by the Customer or an auditor mandated by the Customer, as required by applicable Data Protection Legislation. Routine audits shall ordinarily be limited to one in any twelve-month period, on at least 30 days' written notice, during normal business hours, subject to reasonable confidentiality obligations and measures to minimize disruption to SRI's operations. These limitations shall not prevent additional audits where reasonably necessary following a significant personal data breach, where required by a supervisory authority, or where the Customer has reasonable grounds to believe that SRI is materially failing to comply with its obligations under this DPA.

11.3 SRI may discharge its obligations under clause 11.2 in the first instance by providing its current Security and Data Handling Summary, completed responses to the Customer’s security questionnaire, and any independent certification or assurance report it holds.

12. International transfers

12.1 SRI uses DigitalOcean to host the ICANS application and Amazon Web Services (AWS) to host application databases, uploaded documents and database backups. These services are configured to use Canadian data centre regions. SRI also uses third-party service providers for email communications, payment processing, application error monitoring and infrastructure management, as described in Annex 3. These providers may process or access Customer Personal Data from countries outside Canada. Such processing may include application logs, diagnostic information, email addresses, IP addresses, payment information and other personal data relevant to the services provided. SRI shall ensure that international transfers of Customer Personal Data are subject to applicable data protection requirements and appropriate transfer mechanisms where required by law.

12.2 Where Customer Personal Data is transferred from the European Economic Area or the United Kingdom to SRI in Canada, the Parties may rely on the applicable adequacy arrangements for Canadian recipients subject to the Personal Information Protection and Electronic Documents Act (PIPEDA), to the extent that those arrangements cover the particular transfer. SRI is a commercial organization established in British Columbia, Canada, and is subject to the Personal Information Protection Act of British Columbia (BC PIPA) and, in respect of applicable interprovincial and international commercial activities involving personal information, the federal Personal Information Protection and Electronic Documents Act (PIPEDA). SRI confirms that it is subject to PIPEDA in respect of the relevant commercial processing activities and shall notify the Customer if that position materially changes.

12.3 Where a transfer of Customer Personal Data is not covered by an applicable adequacy decision or regulations, SRI shall ensure that an appropriate transfer mechanism is in place before the transfer occurs. Depending on the circumstances, this may include the European Commission's Standard Contractual Clauses, the UK International Data Transfer Addendum or another mechanism permitted by applicable Data Protection Legislation. Where the EU SCCs or UK Addendum are used between the Parties, they shall be completed in accordance with Annex 4.

12.4 Where a Sub-processor processes Customer Personal Data outside a jurisdiction covered by an applicable adequacy arrangement, SRI shall ensure that the transfer is covered by an appropriate mechanism under applicable Data Protection Legislation. SRI shall maintain information about the relevant Sub-processors and transfer arrangements in Annex 3 or an updated Sub-processor list made available to the Customer.

12.5 SRI shall notify the Customer in advance of material changes to the countries used for primary hosting of Customer Personal Data. Changes involving the appointment or replacement of Sub-processors shall be subject to the notification and objection provisions in Clause 6.2.

13. Representatives and contacts

13.1 Where applicable law requires SRI to appoint a representative in the United Kingdom or European Union, SRI shall make the representative’s identity and contact details available to the Customer and data subjects. SRI shall record the applicable representative details, or its documented determination that no appointment is required, in Annex 1.

13.2 Notices and data-protection communications shall be sent to the SRI contact identified in Annex 1 and the Customer contact identified there. Each party shall notify the other promptly of contact changes. SRI operational contact: ec@smartsettle.com.

14. Liability

14.1 Liability arising under this DPA is subject to the limitations expressly agreed in the Principal Agreement and clause 14.2, except to the extent a limitation is prohibited by applicable law. Nothing in this DPA restricts statutory rights of data subjects or the powers of supervisory authorities.

14.2 Any separate contractual liability cap for this DPA, including its relationship to the Principal Agreement cap and any exclusions, must be expressly agreed in Annex 1. If no separate cap is specified, clause 14.1 applies, subject to applicable law. Nothing in this clause creates an indemnity for regulatory fines or third-party claims.

15. Term

15.1 This DPA takes effect on the date first written above and continues for the term of the Principal Agreement and thereafter until all Customer Personal Data has been deleted or returned in accordance with clause 10.

15.2 Clauses 4, 9, 10, 11, 12 and 14 survive termination.

16. Governing law and jurisdiction

16.1 Except for mandatory provisions of applicable Data Protection Legislation and any applicable international transfer clauses, this DPA is governed by the law and subject to the courts specified in Annex 1. If no governing law or forum is specified, the parties must agree these before signing.

16.2 Any EU SCCs, UK Addendum or other mandatory transfer instrument shall have its own required governing law and forum, as completed in Annex 4, and shall prevail over inconsistent terms of this DPA.

17. General

17.1 Any variation to this DPA must be in writing and signed by both Parties.

17.2 If any provision is held invalid or unenforceable, the remainder continues in effect.

17.3 Save for data subjects where the Data Protection Legislation or the EU SCCs so require, no third party has any right to enforce this DPA.

17.4 This DPA may be executed in counterparts, each of which is an original and which together constitute one agreement.

Signed for and on behalf of the Parties:

For and on behalf of the Customer

Signature: ______________________________________________________________

Name: ____________________________________________________________________

Title: _____________________________________________________________________

Date: ____________________________________________________________________

For and on behalf of Smartsettle Resolutions Inc.

Signature: ______________________________________________________________

Name: ____________________________________________________________________

Title: _____________________________________________________________________

Date: ____________________________________________________________________

Complete Annex 1 for each customer. Confirm that Annexes 2 and 3 describe the relevant deployment and current suppliers. Complete and attach applicable transfer instruments where legally required. Do not execute with unresolved bracketed fields.

Annex 1 — Customer-Specific Processing Schedule

Where EU SCCs apply, the completed processing description in this Annex may be used for Annex I.B of the SCCs, together with all other information required by the SCCs.

ItemStandard description and customer-specific details
Customer and serviceCustomer: [full legal name and jurisdiction]. Principal Agreement: [title, date or reference]. Service/deployment: [Smartsettle product, platform, environment and institutional program]. Customer contact for processing instructions: [role and monitored email].
Subject matterProvision of Smartsettle software and related hosting, negotiation, mediation, educational simulation, dispute-resolution or collaborative decision-making services, as specified in the Principal Agreement. Customer-specific scope: [describe program, users, case types and any excluded activities].
DurationProcessing takes place during the Principal Agreement and any agreed transition period, followed by return or deletion under clause 10. Service commencement and end dates (if different): [specify].
Nature of processingAs required for the agreed service: account provisioning and authentication; receipt, storage, organization, retrieval and transmission of submissions and documents; collection and analysis of participant preferences; algorithmic generation of candidate agreements; case communications; creation of case outcomes or settlement records; technical support, security monitoring, logging, backup, export and deletion. Customer-specific additions or exclusions: [specify].
Purposes of processingTo deliver and support the Customer-authorized service and its cases or simulations, administer user roles and access, communicate with authorized participants, maintain security and comply with documented instructions. Research, assessment, analytics or publication involving identifiable data is NOT authorized merely by this description; specify any such purpose, permitted recipients, lawful basis and safeguards in the customer-specific instructions below.
Categories of data subjectsAs applicable: (a) Customer staff, officers, students, members, administrators and other authorized users; (b) parties to negotiations or disputes and their representatives; (c) advisers, mediators, facilitators, expert neutrals and other case participants; (d) individuals mentioned in case submissions or uploaded materials. Applicable categories and any exclusions: [specify].
Types of personal dataAs applicable: identity and contact details (name, email, telephone, address); account identifiers, authentication information, roles and permissions; case assignments; party submissions, preferences, priorities, offers, messages, uploaded documents and outcome records; technical data (IP address, device/browser details, access records, timestamps and diagnostic logs). Payment/billing data: [none / institution invoiced centrally / specify user-level payment processing]. Data minimization or restrictions: [specify].
Special category and sensitive dataSpecial-category or similarly sensitive data may be included in free text or uploaded materials. Whether such data is permitted, and any safeguards, lawful conditions or restrictions, must be specified in the customer-specific data restrictions above. Financial circumstances alone are not automatically special-category data under GDPR.
Children and age restrictions[Specify minimum age and whether minors may participate. Do not assume every institutional customer serves adults only. Verify that account registration controls match the agreed restriction.]
Recipients and accessCustomer-designated users and participants may receive data only as authorized by the service roles, case permissions and Customer instructions. SRI personnel and approved sub-processors may access data as necessary under this DPA. Customer-specific recipients, external advisers, researchers or exports: [specify]. Any sharing of confidential offers or private preferences must follow the product permissions and case instructions.
Frequency and locationProcessing and data transfers may occur continuously during the service. Primary hosting and relevant international access arrangements are described in clause 12 and Annex 3. Customer-specific hosting, access or geographic restrictions (only if SRI has agreed and can implement them): [specify / none].
Retention during the engagementCustomer instruction: [specify retention periods or deletion triggers for accounts, case records, simulations, exports and logs, including the event from which time is measured]. If no schedule is agreed, SRI applies its documented default retention policy, taking account of inactivity of all parties to a case OR inactivity of the case itself, subject to applicable legal requirements. The precise default period and operational triggers must be confirmed before this schedule is signed. A participant closing an account does not by itself require deletion of shared case records. At termination, clause 10 governs return and deletion, including backups.
Customer-specific instructionsPermitted case types and workflows: [specify]. Instructions on account invitations, user roles and access: [specify]. Restrictions on uploads, special categories, minors, exports or disclosure: [specify]. Research or evaluation: [none / describe identifiable or pseudonymized data, recipients, purpose, legal basis, safeguards and retention]. Any authorized binding or expert-neutral procedure: [specify or reference Principal Agreement]. Other documented instructions: [specify / none].
Sub-processorsApproved sub-processors and their roles are described in Annex 3, subject to clause 6. Customer-specific restrictions or agreed exceptions: [specify / none].
Review and authorizationCustomer representative: [name/role, date]. SRI representative: [name/role, date]. This schedule forms part of the documented instructions under clause 3.2. Changes must be agreed and recorded in accordance with the DPA and Principal Agreement.
Applicable law, forum and contactsGoverning law and courts for clause 16: [specify]. Applicable sector-specific law: [specify / none]. Customer privacy/security and breach notice email: [specify]. SRI contact: ec@smartsettle.com; escalation contact: [confirm].
Roles and optional usesCustomer controller/SRI processor for listed processing: [confirm]. Separately controlled activities: [identify / none]. Research, reporting, external sharing and analytics involving identifiable data: [describe with authorization and safeguards / prohibited].
Transfers and representativesApplicable data export/import countries and restrictions: [specify]. EU/UK transfer instruments, if required: [identify executed instruments and Annex 4 selections / not applicable]. UK Article 27 representative: [details / documented reason not required]. EU Article 27 representative: [details / documented reason not required].
Liability electionSeparate DPA contractual cap: [amount and currency / none]. Relationship to Principal Agreement cap: [replaces / supplements / same cap]. Agreed exclusions and treatment of third-party claims: [specify].

Annex 2 — Technical and organisational measures

This annex describes current technical and organisational measures for the relevant deployment. Any planned improvements are identified as such and are not represented as implemented.

MeasureExpected content / current position
Encryption in transitAll connections between users and the service use HTTPS with TLS 1.2 or higher. HTTP is redirected to HTTPS and HSTS is enabled. The application's primary database connection (AWS RDS for PostgreSQL) uses TLS 1.2, the application verifies the database server's certificate, and the database rejects unencrypted connections, as verified by testing on November 2, 2026. Per-customer database connections are configured through environment variables. They use the same certificate verification settings. Email is submitted to Google over TLS (port 465, implicit TLS), and onward delivery to recipients uses opportunistic TLS. Connections to other sub-processors (AWS S3, Bugsnag, Stripe) use TLS.
Encryption at restThe AWS RDS database and its automated backups are encrypted at rest. Uploaded documents are stored in Amazon S3 with server-side encryption (SSE-S3, AES-256). The application server is not intended to store case data. There is no case data in logs, temporary files or uploads on local disk.
PseudonymisationIdentifiers and case content are held in separate records within the same database. No further pseudonymisation is applied.
Access control — logicalAccess within the application is role-based. Facilitators and mediators can view only the cases assigned to them, with access restrictions enforced through Pundit authorisation. Application sessions time out after one hour. Passwords must contain at least eight characters, including at least one uppercase letter, one lowercase letter, one number and one special character. Multi-factor authentication is required for access to DigitalOcean, AWS and the source code repository. Multi-factor authentication is not currently required for administrator accounts within the ICANS web application. Introducing multi-factor authentication for these accounts is a planned future security improvement, but no implementation date has yet been established.
Access control — administrativeAccess to production customer data is restricted to a limited group of authorised personnel. Three developers have SSH and Rails console access to the application servers. SSH access requires key-based authentication, and password-based SSH authentication is disabled. Database access is restricted by IP allowlisting to the application servers. Seven individuals have AWS console access, protected by multi-factor authentication. Within the application, five facilitators or mediators can access their assigned cases, while two administrators/programmers have access to all case and user data. Access to customer data for support and maintenance purposes is infrequent. Administrative access is not currently time-limited, although mediator access is assigned on a case-by-case basis. Web server and SSH authentication logs are retained. Database queries and Rails console commands are not comprehensively logged. There is currently no formal approval or periodic access review process. As a future improvement, SRI intends to maintain a documented list of individuals with administrative and infrastructure access, including access through Cloud66, and introduce periodic reviews to confirm that permissions remain appropriate. No implementation date has yet been established.
Joiners, movers and leaversA basic process exists for administrator accounts in the web application. There is currently no formal documented process for granting, modifying or removing access to AWS, DigitalOcean and the application servers. As a future improvement, SRI intends to document the procedures for managing infrastructure access, including maintaining access records and introducing a checklist to ensure that access is removed when an individual no longer requires it. No implementation date has yet been established.
Tenant separationEach ODR customer's data is held in its own dedicated database. Documents uploaded by each customer are stored in a separate Amazon S3 bucket dedicated to that customer. Within each database, access is controlled by role-based authorisation in the application.
Network and infrastructure securityServers are protected by a host firewall (UFW), managed through Cloud66, with only required ports open. Database access is restricted to the application servers by IP address. Redis, which is used for background jobs and caching, requires password authentication and is protected by firewall restrictions that prevent access from outside the application's private network. Redis is not currently bound exclusively to the private network interface, and connections over the private network are not TLS-encrypted. Restricting Redis to the private network interface is planned as a future security improvement, but no implementation date has yet been established. SSH access is restricted to authorised administrators and requires key-based authentication. Password-based SSH authentication is disabled. Operating system and application dependency updates are applied as needed rather than according to a fixed schedule.
Logging and monitoringWeb access logs and SSH authentication logs are retained for approximately one month. Database query logging is limited, and application errors are monitored through Bugsnag. Detection and investigation of anomalous activity are currently performed manually. AWS CloudTrail is not currently enabled.
Vulnerability managementAn independent penetration test was previously conducted by Cobalt.io, and all identified findings were remediated. Penetration testing is not currently performed on a fixed schedule. The application currently runs on Ruby 2.7 and Rails 6.0, which are no longer supported by their maintainers. Upgrading to supported versions is planned as a future security improvement, but no implementation date has yet been established. Automated dependency vulnerability scanning is not currently in place. Introducing regular dependency vulnerability scanning is a planned future improvement, but no implementation date has yet been established. Formal remediation timescales based on vulnerability severity have not yet been defined.
Secure developmentDevelopment, staging and production environments are separate. Live customer personal data is not used in development or staging. Code is written by a single developer and is not currently peer reviewed.
Backup and restoreAWS RDS backups are taken daily and retained for 30 days. They are encrypted and held within AWS Canada. Restoration from backup has previously been successfully performed, although the date of the last successful restoration has not been documented. S3 versioning is not currently enabled. Automated DigitalOcean server backups are not currently enabled. The application is deployed and configured through Cloud66, while the primary application database and uploaded documents are stored in AWS RDS and S3, respectively. The DigitalOcean server may contain application logs, temporary files and other operational data that would not be preserved if the server were lost. The application can be redeployed through Cloud66, although recovery of locally stored operational data is not currently provided for.
Availability and resilienceThe service runs on a single application server and a single-AZ database, without redundancy. No formal availability target, recovery time objective or recovery point objective is defined. The AWS RDS database is backed up daily, with backups retained for 30 days. The most recent recoverable backup ordinarily provides a recovery point within approximately 24 hours, subject to successful backup completion and restoration. SRI does not currently guarantee a specific recovery point objective or recovery time objective.
Business continuity and disaster recoveryNo formal written business continuity or disaster recovery plan currently exists. AWS RDS backups are retained for 30 days, and database restoration has previously been performed successfully, although the date has not been documented. The application is deployed and configured through Cloud66 and can be redeployed to a replacement DigitalOcean server. A formal written disaster recovery plan is intended for future development, but no implementation date has yet been established.
Physical securityHosting facilities are operated by AWS and DigitalOcean. Physical security is inherited from them and evidenced by their certifications, available on request. No customer data is held on SRI office equipment.
PersonnelStaff sign confidentiality agreements. No formal pre-engagement screening is currently carried out. No formal data protection or security awareness training is currently provided. Formal training is planned for future implementation, but no implementation date has yet been established.
Supplier managementSub-processors (DigitalOcean, AWS, Google, Bugsnag and Stripe, where acting as a processor) were selected on the basis of reputation and established security practices. Data Processing Agreements with these providers are incorporated into their applicable service terms. No formal periodic review of sub-processors is currently carried out.
Incident managementNo formal written incident response procedure currently exists. Security incidents are handled by an authorised member of SRI management, who is responsible for investigating incidents, coordinating remedial action and notifying affected customers where required. Customers will be notified of a personal data breach without undue delay after SRI becomes aware of it, in accordance with the notification obligations set out in this Agreement. Notifications will be sent using the designated customer contact details or other agreed communication channels. Developing a written incident response procedure is planned as a future improvement, but no implementation date has yet been established.
Secure deletionOn termination, the customer's RDS database and S3 data are deleted through AWS. S3 versioning is not enabled, so deletion is permanent. Automated backups are deleted with the instance and no final or manual snapshot is retained. Web and authentication logs are retained for one month and then deleted.
CertificationSRI does not currently hold an independent security certification or assurance report. Obtaining independent certification or assurance is a longer-term objective, but no timetable has been established. AWS and DigitalOcean hold their own certifications, available on request.

Annex 3 — Approved Sub-processors

Annex 3 identifies providers that may process Customer Personal Data. Confirm the correct legal entities, processing locations, and applicable transfer arrangements for each deployment before execution.

CategoryService providedSub-processorLocationTransfer basis
HostingCloud infrastructure hosting the applicationDigitalOcean [confirm contracting legal entity]Canada[Confirm applicable transfer mechanism and any onward access; do not assume adequacy or DPF certification.]
HostingCloud infrastructure hosting the databaseAmazon Web Services [confirm contracting legal entity]Canada[Confirm applicable transfer mechanism and any onward access; do not assume adequacy or DPF certification.]
BackupOff-site or secondary backup storageAmazon Web Services [confirm contracting legal entity]Canada[Confirm applicable transfer mechanism and any onward access; do not assume adequacy or DPF certification.]
EmailTransactional email delivery — invitations, notifications, password resetsGoogle LLCUnited States (and global data centers)[Confirm applicable transfer mechanism and any onward access; do not assume adequacy or DPF certification.]
PaymentsPayment processing, where applicableStripe LLCUnited States[Confirm applicable transfer mechanism and any onward access; do not assume adequacy or DPF certification.]
DevelopmentProduction error monitoring and crash reporting, potentially involving email addresses, IP addresses and other application dataBugsnag, IncUnited States (and global cloud infrastructure)[Confirm applicable transfer mechanism and any onward access; do not assume adequacy or DPF certification.]
Deployment ManagementDeployment, server configuration, application log processing and access to environment variables that may permit access to AWS databases and S3 storageCloud 66 [confirm contracting legal entity]United States (Primary), United Kingdom[Confirm applicable transfer mechanism and any onward access; do not assume adequacy or DPF certification.]
Analytics (Exhibition only)Google Analytics is enabled on the International eNegotiation Exhibition; not enabled on Smartsettle ONE sites. Confirm data collected and controller/processor role.Google [confirm service and contracting entity][confirm processing and access locations][confirm role, lawful basis, disclosures and transfer safeguards]

Annex 4 — Completion of the EU SCCs and UK Addendum

This Annex is a completion schedule only. Where EU SCCs or a UK transfer instrument is required, the applicable official clauses must be incorporated or executed in full, with all required tables and annexes completed. This schedule alone does not establish a lawful transfer mechanism.

ProvisionElection
ModuleModule Two (controller to processor), where that module matches the parties’ actual roles and transfer.
Data exporterThe Customer, as identified in the preamble. Role: controller. Contact as at clause 13.2.
Data importerSRI, as identified in the preamble. Role: processor. Contact as at clause 13.2.
Clause 7 (docking clause)[Include / omit — include if the Customer may add group entities]
Clause 9 (sub-processors)Option 2, general written authorisation. Notice period: [30] days, as at clause 6.2.
Clause 11 (redress)The optional independent dispute resolution paragraph is not included.
Clause 17 (governing law)[Select an eligible EU Member State governing law when EU SCCs apply; otherwise not applicable. UK transfers: complete applicable UK instrument.]
Clause 18 (forum)[Courts of the selected eligible EU Member State when EU SCCs apply; otherwise not applicable.]
Annex I.A, I.BAs set out in the preamble and Annex 1 of this DPA.
Annex I.C (supervisory authority)[Identify competent supervisory authority for the actual transfer, if SCCs apply.]
Annex II (measures)As set out in Annex 2 of this DPA.
Annex III (sub-processors)As set out in Annex 3 of this DPA.
UK Addendum, Table 4Neither Party may end the Addendum as set out in Section 19.

Авторське право © 1997 - 2026 "АйКен" Сістемс Інк. & Смартсетл Резолушнс Інк. Всі права захищені.

  • Офіційне повідомлення
  • ⋅
  • Політика конфеденційності
  • ⋅
  • Умови використання
  • ⋅
  • DPA