This Data Processing Agreement ("DPA") is entered into between:
Clenta, Inc., a Delaware corporation, with its principal place of business at [REGISTERED ADDRESS PENDING C CORP COMPLETION] ("Clenta" or "Processor"),
and
The entity identified in the applicable Order Form or Clenta Account ("Customer" or "Controller").
This DPA forms part of, and is incorporated into, the Clenta Terms of Service or any other written agreement between the parties governing Customer's use of the Services (the "Agreement"). In the event of a conflict between this DPA and the Agreement, this DPA controls with respect to the subject matter herein.
1.1 "Applicable Data Protection Law" means all laws and regulations applicable to the processing of Personal Data under the Agreement, including, where applicable, GDPR, the UK GDPR, CCPA/CPRA, and any successor or implementing legislation.
1.2 "Customer Data" means all data, including Personal Data, submitted to or processed by Clenta on behalf of Customer in connection with the Services.
1.3 "Data Subject" means the identified or identifiable natural person to whom Personal Data relates. In the context of Clenta's Services, Data Subjects are typically end clients of Customer — shoppers, clientele, or contacts managed by Customer's retail or service operations.
1.4 "GDPR" means Regulation (EU) 2016/679 of the European Parliament and of the Council.
1.5 "Personal Data" has the meaning given to it under Applicable Data Protection Law (including "personal information" as defined under CCPA/CPRA).
1.6 "Processing" (and "Process," "Processes," "Processed") means any operation performed on Personal Data, including collection, recording, storage, use, disclosure, or deletion.
1.7 "Security Incident" means any confirmed unauthorized access to, use of, disclosure of, or destruction of Customer Data, or any breach of Clenta's security measures that affects the confidentiality, integrity, or availability of Customer Data.
1.8 "Services" means the Clenta platform and AI-powered clienteling agent ("Iris") as described in the Agreement.
1.9 "Sub-processor" means any third party engaged by Clenta to process Customer Data in connection with the Services.
1.10 "Benchmark Data Program" means Clenta's optional program under which participating Customers' data may be included in cross-organization, aggregated, anonymized industry benchmarks, subject to the conditions in Article 6.
2.1 Processor designation. As between the parties, Customer is the Controller of Customer Data, and Clenta is the Processor acting on Customer's behalf. Customer determines the purposes and means of processing Customer Data; Clenta processes Customer Data only as necessary to provide the Services and as otherwise set forth in this DPA.
2.2 Controller obligations. Customer represents and warrants that:
2.3 Clenta's processing obligation. Clenta shall process Customer Data only:
Clenta shall not process Customer Data for any other purpose, including for Clenta's own independent commercial purposes, to sell to third parties, or to train general-purpose AI models without Customer's explicit written consent.
2.4 Conflicting legal requirements. If Clenta is required by applicable law to process Customer Data in a manner inconsistent with Customer's instructions, Clenta shall notify Customer before processing (unless prohibited by law) and shall process only to the minimum extent required.
| Element | Details |
|---|---|
| Subject matter | Clenta's AI-powered clienteling platform |
| Duration | For the term of the Agreement, plus any post-termination period required for deletion |
| Nature of processing | Storage, retrieval, AI-assisted structuring, reminder scheduling, contextual surfacing of client relationship data |
| Purpose of processing | Enabling retail associates to log, retrieve, and act on client interaction history via the Iris AI agent |
| Types of Personal Data | Names, contact information (email, phone), interaction notes, purchase preferences, relationship history, associate-logged observations, scheduling information |
| Categories of Data Subjects | End clients (shoppers/clients) of the Customer; Customer's retail associates |
| Customer's role | Data Controller |
| Clenta's role | Data Processor |
4.1 Technical and organizational measures. Clenta shall implement and maintain appropriate technical and organizational measures ("TOMs") to protect Customer Data against unauthorized access, disclosure, alteration, or destruction, including:
See Annex 1 for a full description of Clenta's current technical and organizational security measures.
4.2 Sub-processor security. Clenta shall ensure that Sub-processors are bound by data protection and security obligations no less protective than those in this DPA.
5.1 Notification obligation. In the event Clenta becomes aware of a confirmed Security Incident affecting Customer Data, Clenta shall:
5.2 Notification content. The notification shall include, to the extent then known:
5.3 Updates. Clenta shall provide Customer with timely updates as additional information becomes available.
5.4 No admission. Notification under this Article does not constitute an admission of fault or liability.
6.1 Primary use restriction. Clenta processes Customer Data only as set forth in Articles 2 and 3. Clenta shall not use Customer Data for cross-organizational analysis, benchmarking, or any secondary purpose without Customer's express opt-in under this Article.
6.2 Benchmark Data Program — opt-in. Customer may elect, at its sole discretion, to participate in the Clenta Benchmark Data Program by enabling the benchmark participation setting in the Clenta admin interface (or by written agreement). Participation is disabled by default and requires affirmative Customer action to enable.
6.3 Eligibility conditions. Clenta shall not include Customer's data in any Benchmark Data output unless all of the following conditions are met:
6.4 Permitted uses of Benchmark Data. If the conditions in Section 6.3 are met, Clenta may use the resulting anonymized, aggregated benchmark data ("Benchmark Data") to:
6.5 Limitations. Clenta shall not:
6.6 Opt-out. Customer may withdraw consent to participate in the Benchmark Data Program at any time by disabling the benchmark participation setting. Withdrawal does not affect any Benchmark Data already derived and anonymized prior to withdrawal, provided such data met the conditions in Section 6.3 at the time of derivation.
7.1 Clenta's assistance. Clenta shall provide Customer with reasonable technical assistance to fulfill Customer's obligations under Applicable Data Protection Law to respond to Data Subject requests (including requests for access, correction, deletion, restriction, or portability of Personal Data), taking into account the nature of the processing.
7.2 Clenta not the controller. Clenta has no direct relationship with Data Subjects and is not responsible for responding to Data Subject requests directly. If a Data Subject contacts Clenta directly, Clenta shall promptly notify Customer and direct the Data Subject to Customer.
8.1 Customer-initiated deletion. Customer may delete Customer Data at any time using the tools and controls provided within the Services.
8.2 Deletion on termination. Upon expiration or termination of the Agreement, Customer may request return of Customer Data in a machine-readable format within 30 days of the termination date.
8.3 Clenta's deletion obligation. Following the earlier of: (a) Customer's request for deletion under Section 8.1 or 8.2, or (b) 30 days after the termination or expiration of the Agreement, Clenta shall:
8.4 Retained data. Notwithstanding the foregoing, Clenta may retain Customer Data to the extent required by Applicable Data Protection Law or legitimate business purposes (e.g., billing records, fraud prevention), provided that such retained data is: (a) kept confidential and not further processed except as required by law; and (b) deleted as soon as the legal or legitimate retention obligation expires.
8.5 Anonymized data. Anonymized and aggregated Benchmark Data derived prior to deletion (pursuant to Article 6 and where all conditions were met) is not "Customer Data" for purposes of this Article.
9.1 General authorization. Customer provides general written authorization for Clenta to engage Sub-processors to process Customer Data in connection with the Services, subject to the conditions in this Article.
9.2 Sub-processor obligations. Clenta shall:
9.3 Sub-processor list. Clenta shall maintain and make available to Customer, upon request, a current list of Sub-processors engaged to process Customer Data.
9.4 AI provider restriction. Without limiting Section 9.2, Clenta shall ensure that any AI model provider (including Anthropic and any successor provider) processing Customer Data is prohibited by written agreement from:
9.5 New Sub-processors. Clenta shall provide Customer with 10 days' advance notice before engaging a new Sub-processor that will process Customer Data, and shall update the sub-processor list accordingly. Customer may object to a new Sub-processor within 10 days of notice by providing written notice to legal@clenta.ai describing the basis for the objection. If the parties cannot resolve the objection within the notice period, Customer may terminate the Agreement on 30 days' written notice without penalty.
Emergency exception. If Clenta is required to engage a Sub-processor on an emergency basis to respond to a Security Incident or protect the integrity of the Services, Clenta may engage such Sub-processor immediately and shall provide Customer with written notice within 10 days of doing so.
10.1 EEA/UK/Switzerland transfers. Where Customer Data originates in the European Economic Area, the United Kingdom, or Switzerland and is transferred to Clenta or its Sub-processors in a third country lacking an adequacy decision, such transfers shall be subject to the appropriate transfer mechanism, which may include:
10.2 CCPA/CPRA. For purposes of CCPA/CPRA, Clenta is a "Service Provider" (and "Contractor") as those terms are defined under applicable California law. Clenta:
11.1 Information provision. Clenta shall make available to Customer all information reasonably necessary to demonstrate compliance with this DPA.
11.2 Audit right. Customer may, upon 30 days' written notice and no more than once per calendar year, conduct an audit of Clenta's data processing practices relevant to this DPA, at Customer's expense. Clenta may satisfy this obligation through provision of third-party audit reports, penetration test summaries, or equivalent certifications.
11.3 Confidentiality of audit. Any audit results are confidential and may not be shared with third parties without Clenta's consent, except as required by law or regulatory authority.
12.1 Application of Agreement cap. The liability of either party under this DPA shall be subject to the limitations of liability set forth in the Agreement, including any aggregate liability cap and exclusions.
13.1 This DPA shall remain in effect for as long as Clenta processes Customer Data under the Agreement. Termination of the Agreement shall automatically terminate this DPA, subject to the survival of deletion and return obligations in Article 8 and confidentiality obligations.
14.1 Governing law. This DPA shall be governed by the same governing law as the Agreement (State of Delaware), except where Applicable Data Protection Law requires otherwise.
14.2 Entire agreement. This DPA, together with the Agreement and any annexes, constitutes the entire agreement between the parties with respect to the processing of Customer Data.
14.3 Precedence. This DPA supersedes any prior agreements regarding data processing between the parties with respect to the subject matter herein.
14.4 Updates. Clenta may update this DPA from time to time to reflect changes in Applicable Data Protection Law or Clenta's Services. Clenta shall provide Customer with 30 days' advance notice of material changes. Continued use of the Services after the effective date constitutes acceptance.
Encryption
Access Controls
Incident Response
Backups
Vendor Security
Personnel
What it is: An optional, opt-in program that allows Clenta to include your anonymized, aggregated data in cross-organization industry benchmarks (e.g., average client reactivation rates by retail tier).
What is never included: Individual shopper names, contact information, purchase history, or any data that can identify a specific person or your organization.
Default: Off. You must explicitly enable this in your Clenta admin settings.
Cohort minimum: Clenta only generates benchmark outputs when at least 20 independent organizations have opted in — no single organization's data is identifiable in any output.
Opt-out: You can opt out at any time. Previously derived, properly anonymized benchmark data is not retroactively deleted.