Data Processing Agreement
This Data Processing Agreement (“Agreement“) forms part of the Contract for Services (“Principal Agreement“) between
The Client to the SalesAlly Service
(the “Client”) and
OIKOSO.LTD (Trading as SalesAlly Studio/SalesAlly)_____
(the “Data Processor”)
(together as the “Parties”)
WHEREAS
(A) The Client acts as a Data Controller.
(B) The Client wishes to subcontract certain Services, which imply the processing of personal data, to the Data 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 Agreement shall have the following meaning:
1.1.1 “Agreement” means this Data Processing Agreement and all Schedules;
1.1.2 “Client Personal Data” means any Personal Data Processed by a Contracted Processor on behalf of Client pursuant to or in connection with the Principal Agreement;
1.1.3 “Contracted Processor” means a Subprocessor;
1.1.4 “Data Protection Laws” means EU Data Protection Laws and, to the extent applicable, the data protection or privacy laws of any other country;
1.1.5 “EEA” means the European Economic Area;
1.1.6 “EU Data Protection Laws” means EU Directive 95/46/EC, as transposed into domestic legislation of each Member State and as amended, replaced or superseded from time to time, including by the GDPR and laws implementing or supplementing the GDPR;
1.1.7 “GDPR” means EU General Data Protection Regulation 2016/679;
1.1.8 “Data Transfer” means:
1.1.8.1 a transfer of Client Personal Data from the Client to a Contracted Processor; or
1.1.8.2 an onward transfer of Client 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.9 “Services” means the provision of the SalesAlly AI Customer Service, including data synchronization, processing of customer conversations, and dual-location storage of client and business data___.
1.1.10 “Subprocessor” means any person appointed by or on behalf of Processor to process Personal Data on behalf of the Client 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 Client Personal Data
2.1 Processor shall:
2.1.1 comply with all applicable Data Protection Laws in the Processing of Client Personal Data; and
2.1.2 not Process Client Personal Data other than on the relevant Client’s documented instructions.
2.2 The Client instructs Processor to process Client Personal Data.
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 the Client Personal Data, ensuring in each case that access is strictly limited to those individuals who need to know / access the relevant Client 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 Client 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 Processor shall not appoint (or disclose any Client Personal Data to) any Subprocessor unless required or authorized by the Client.
6. Data Subject Rights
6.1 Taking into account the nature of the Processing, Processor shall assist the Client by implementing appropriate technical and organisational measures, insofar as this is possible, for the fulfilment of the Client obligations, as reasonably understood by Client, to respond to requests to exercise Data Subject rights under the Data Protection Laws.
6.2 Processor shall:
6.2.1 promptly notify Client if it receives a request from a Data Subject under any Data Protection Law in respect of Client Personal Data; and
6.2.2 ensure that it does not respond to that request except on the documented instructions of Client 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 Client of that legal requirement before the Contracted Processor responds to the request.
7. Personal Data Breach
7.1 Processor shall notify Client without undue delay upon Processor becoming aware of a Personal Data Breach affecting Client Personal Data, providing Client with sufficient information to allow the Client 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 the Client and take reasonable commercial steps as are directed by Client to assist in the investigation, mitigation and remediation of each such Personal Data Breach.
8. Data Protection Impact Assessment and Prior Consultation Processor shall provide reasonable assistance to the Client with any data protection impact assessments, and prior consultations with Supervising Authorities or other competent data privacy authorities, which Client 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 Client Personal Data by, and taking into account the nature of the Processing and information available to, the Contracted Processors.
9. Deletion or return of Client Personal Data
9.1 Subject to this section 9 Processor shall promptly and in any event within 10 business days of the date of cessation of any Services involving the Processing of Client Personal Data (the “Cessation Date”), delete and procure the deletion of all copies of those Client Personal Data.
10. Audit rights
10.1 Subject to this section 10, Processor shall make available to the Client on request all information necessary to demonstrate compliance with this Agreement, and shall allow for and contribute to audits, including inspections, by the Client or an auditor mandated by the Client in relation to the Processing of the Client Personal Data by the Contracted Processors.
10.2 Information and audit rights of the Client 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 The Processor may not transfer or authorize the transfer of Data to countries outside the EU and/or the European Economic Area (EEA) without the prior written consent of the Client. If personal data processed under this Agreement is transferred from a country within the European Economic Area to a country outside the European Economic Area, the Parties shall ensure that the personal data are adequately protected. To achieve this, the Parties shall, unless agreed otherwise, rely on EU approved standard contractual clauses for the transfer of personal data.
12. General Terms
12.1 Confidentiality. Each Party must keep this Agreement and 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 delivered personally, sent by post or sent by email to the address or email address set out in the heading of this Agreement at such other address as notified from time to time by the Parties changing address.
13. Governing Law and Jurisdiction
13.1 This Agreement is governed by the laws of England and Wales_________.
13.2 Any dispute arising in connection with this Agreement, which the Parties will not be able to resolve amicably, will be submitted to the exclusive jurisdiction of the courts of London, United Kingdom, subject to possible appeal to_____________________________.
IN WITNESS WHEREOF, this Agreement is entered into with effect from the date first set out below.
The Client
Signature ______________________________
Name: ________________________________
Title: _________________________________
Date Signed: ___________________________
Processor Company
Signature ______________________________
Name ________HUANG YAO_________________
Title ________Director_____________________
Date Signed ________2025-11-17_____________
Schedule 1: Details of Processing
This Schedule defines the scope, nature, and purpose of the data processing to ensure compliance with Article 28(3) of the GDPR.
1. Parties and Processing Roles
| Role (GDPR) | Entity Name (or Legal Identity) |
|---|---|
| Data Controller | Client (The Subscriber to the SalesAlly Service) |
| Data Processor | OIKOSO.LTD (Trading as SalesAlly Studio/SalesAlly) |
2. Scope, Purpose, and Duration of Processing
| Area | Description |
|---|---|
| Subject Matter | Provision of AI-driven customer service and question-answering support for the Client’s WooCommerce store visitors. |
| Purpose | 1. To provide personalized, accurate, real-time AI customer service based on the Client’s synchronized business data. 2. To store conversation logs and synchronized data for AI model optimization, service improvement, and data maintenance. |
| Nature of Processing | Synchronization, Storage, Analysis, Retrieval, and Transfer of data (via bidirectional flow between the Client’s WordPress database and the Processor’s server). |
| Duration | For the duration of the Principal Agreement. Data shall be deleted within 10 calendar days of contract termination. |
| Category (GDPR) | Description (Tailored to SalesAlly) |
|---|---|
| Data Subjects | Visitors and Customers of the Client’s e-commerce store interacting with the AI service. |
| Client Personal Data (PII) |
Buyer Session/Identification Data: Conversation logs, Session IDs, and PII actively provided by the user during chat (e.g., email or name for order lookup). Transactional Data: Order IDs, Order Status, Purchased Product Names (pulled only when required by the AI service). |
| Business Data (Non-PII) | Synchronized Business Data: Product names, SKUs, pricing, descriptions, coupon codes, and general web page content from the Client’s WordPress database. |
- Data Flow: Merchant’s WordPress Website ➔ OIKOSO.LTD Server (API) ➔ AI Processing Unit (LLM).
- Dual Storage:
-
- Client’s WordPress Database (as a primary or synchronized copy).
- OIKOSO.LTD Server Database, hosted on Tencent Cloud (US Region).
Schedule 2: Technical and Organisational Measures (TOMs)
This Schedule outlines the specific security measures taken by the Data Processor (OIKOSO.LTD) to protect Client Personal Data, as required by Article 32 of the GDPR.
| Area(GDPR Requirement) | Measure Type | Customized Description |
|---|---|---|
| 1. Confidentiality | Access Control | Access to production environments and customer data is strictly limited to core Software Development Engineers on a need-to-know basis. All access strictly requires Multi-Factor Authentication (MFA). |
| Physical Security | Our server infrastructure is physically hosted in Tencent Cloud’s data centers located in the United States. These facilities are protected by Tencent Cloud’s strict physical security controls, including 24/7 surveillance, biometric access, and multiple security perimeters. | |
| 2. Integrity and Availability | Transmission Security | All data transfer (API calls, conversation flow) is encrypted using TLS 1.2 or higher. |
| Storage Encryption | Databases and storage volumes are encrypted at rest using AES-256. Highly sensitive credentials (e.g., Merchant API Keys) are encrypted at the application level. | |
| Redundancy & Backup | Daily automated database backups are performed, encrypted (using AES-256), and stored redundantly in a separate location (Cross-AZ storage) to ensure business continuity. | |
| 3. Resilience and Testing | Incident Response | Implementation of a Data Incident Response Plan (DIRP). Processor commits to notifying the Client without undue delay, typically within 24 hours, upon discovery of a breach. |
| Regular Testing | Internal security reviews and vulnerability scanning are conducted periodically to assess the effectiveness of the TOMs. All code changes undergo security-focused code review before deployment. | |
| 4. Data Erasure Protocol | Deletion Trigger | Upon receipt of a deletion request via the WordPress Privacy Tools or API instruction from the Controller. |
| Knowledge Base Erasure | The Processor shall identify the Knowledge Base ID associated with the Merchant and permanently delete the Knowledge Base index, documents, and related vector embeddings from the server database. | |
| Session Erasure | The Processor shall query all Session IDs associated with the specific Buyer ID provided and execute a hard delete of all conversation logs and metadata associated with those sessions. |