DATA PROCESSING AGREEMENT

Let’s Whisper s.r.o. (Yasan)

Effective Date: 19 October 2026
Last Updated: 19 October 2026
Version: 2.1 (replaces the Data Processing Agreement effective 1 February 2026)


This Data Processing Agreement (“DPA”) is entered into between:

the Customer — the entity identified as the customer in the account registration, Platform installation or Order for the Yasan service (the “Controller”), and

Let’s Whisper s.r.o., Company ID 23849959, Křižíkova 148/34, Karlín, 186 00 Praha 8, Czech Republic, registered in the Commercial Register maintained by the Municipal Court in Prague, Section C, Insert 433436 (the “Processor”),

(each a “Party”, together the “Parties”).

This DPA forms an integral part of the Terms of Service at https://yasan.ai/terms (the “Terms”) and is concluded electronically by the Controller’s acceptance of the Terms, installation of the Service through a Platform, or signature of an Order. The person accepting on behalf of the Controller represents that they are authorised to do so. Capitalised terms not defined here have the meaning given in the Terms.


1. SUBJECT MATTER, ROLES AND PRECEDENCE

1.1. This DPA governs the processing of personal data by the Processor on behalf of the Controller in the course of providing the Service, as further described in Schedule 1.

1.2. The Parties agree that, for the personal data described in Schedule 1, the Controller is the controller (or, where the Controller itself acts as a processor for a third party, a processor, in which case the Processor acts as sub-processor and the Controller warrants that its own controller has authorised the engagement of the Processor and the terms of this DPA) and the Processor is the processor within the meaning of Article 4(7) and (8) GDPR.

1.3. The Processor acts as an independent controller only for the limited security and service-integrity processing described in its Privacy Policy (Section 6.4) and for its own account, billing and usage data; such processing is outside the scope of this DPA.

1.4. This DPA is intended to satisfy Article 28(3) GDPR. “GDPR” means Regulation (EU) 2016/679 and, where the Controller or the processing is subject to the law of the United Kingdom, also the UK GDPR and the Data Protection Act 2018 (“UK Data Protection Law”); “Data Protection Law” means the GDPR, UK Data Protection Law, applicable national implementing and ePrivacy legislation. Terms used in this DPA have the meaning given in the GDPR.

1.5. In case of conflict, this DPA prevails over the Terms with respect to the processing of personal data; the Standard Contractual Clauses (Section 8) prevail over this DPA with respect to international transfers. Nothing in this DPA increases the Processor’s liability beyond the limits in the Terms (Section 13).


2. CONTROLLER’S OBLIGATIONS AND WARRANTIES

2.1. The Controller is solely responsible for the lawfulness of the processing it instructs, including for: (a) having a valid legal basis for the processing of personal data of its End Users, Users and other data subjects through the Service; (b) providing data subjects with all information required by Articles 13 and 14 GDPR, at a minimum as set out in Section 7.2 of the Terms; (c) obtaining any consent required by ePrivacy law before enabling Features that store or read identifiers on End Users’ devices, and passing the consent state to the Service; (d) assessing whether its use of the Service involves special categories of personal data (Article 9 GDPR) and, if so, establishing a lawful basis and configuring the Service appropriately, including keeping cross-visit history disabled; (e) carrying out any data protection impact assessment required for its own processing; (f) keeping records of processing; (g) responding to data subjects and supervisory authorities.

2.2. The Controller’s instructions must comply with Data Protection Law. The Controller shall not instruct the Processor to process data in a manner that is unlawful, that exceeds the functionality of the Service, or that would require the Processor to breach any law or third-party agreement. The Processor may refuse to execute an instruction it considers unlawful or outside the Service, and shall inform the Controller.

2.3. The Controller warrants that it is entitled to transfer the personal data to the Processor and to authorise the processing and the onward transfers described in this DPA, and that the personal data has been collected lawfully.

2.4. The Controller shall indemnify and hold the Processor harmless from third-party claims, fines and penalties, and the resulting damages and reasonable costs, to the extent caused by the Controller’s breach of this Section 2, by its unlawful instructions, or by the content of the personal data it entrusts to the Processor, on the terms set out in Section 7.9 of the Terms.


3. PROCESSOR’S OBLIGATIONS

The Processor shall:

3.1. Instructions. Process personal data only on documented instructions from the Controller, including with regard to transfers to third countries, unless required to do so by EU, Member State or UK law to which the Processor is subject, in which case the Processor shall inform the Controller of that legal requirement before processing, unless the law prohibits such information on important grounds of public interest. The Terms, this DPA, the Controller’s configuration of the Service (including Features enabled, integrations connected, settings and instructions given to the assistant), and the Controller’s use of the Service’s functions constitute the Controller’s complete and documented instructions. Additional instructions require written agreement and may be subject to additional fees.

3.2. Confidentiality. Ensure that persons authorised to process the personal data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality, and that they process personal data only on instructions.

3.3. Security. Implement the technical and organisational measures set out in Schedule 2, and such further measures as are required by Article 32 GDPR, taking into account the state of the art, the costs of implementation, the nature, scope, context and purposes of processing and the risk. The Processor may update Schedule 2 provided that the overall level of security is not materially reduced.

3.4. Sub-processors. Engage sub-processors only in accordance with Section 5.

3.5. Data subject rights. Taking into account the nature of the processing, assist the Controller by appropriate technical and organisational measures, insofar as this is possible, in fulfilling the Controller’s obligation to respond to requests for exercising data subjects’ rights, as set out in Section 6.

3.6. Assistance. Assist the Controller in ensuring compliance with Articles 32 to 36 GDPR (security, breach notification, DPIA, prior consultation), taking into account the nature of the processing and the information available to the Processor, as set out in Section 7.

3.7. Deletion and return. At the Controller’s choice, delete or return all personal data after the end of the provision of the Service, and delete existing copies, unless EU, Member State or UK law requires storage, as set out in Section 9.

3.8. Information and audits. Make available to the Controller all information necessary to demonstrate compliance with Article 28 GDPR and allow for and contribute to audits, as set out in Section 10.

3.9. Notification of infringing instructions. Immediately inform the Controller if, in the Processor’s opinion, an instruction infringes the GDPR or other EU, Member State or UK data protection provisions. The Processor is not obliged to perform a legal review of the Controller’s instructions.


4. SPECIFIC COMMITMENTS FOR THE SERVICE

4.1. Purpose limitation and per-Customer isolation. The Processor shall process personal data of the Controller’s End Users (including chat conversations, search queries, e-mails and analytics events) exclusively for the provision of the Service to the Controller. The Processor shall not combine, link or cross-reference such personal data with personal data processed for any other customer, shall not use it to build profiles of individuals across websites, and shall not use it for advertising. This does not prevent the Processor from (a) using Service Content to configure, tune and improve the assistant for the Controller’s own account, and (b) creating and using aggregated and anonymised data from which no individual or Controller can be identified, as set out in the Terms.

4.2. No training of general-purpose models. The Processor shall not use the Controller’s personal data to train, fine-tune or improve general-purpose artificial intelligence or machine-learning models, whether its own or those of third parties, and shall contractually require its AI sub-processors not to use such data to train their models and not to retain it beyond what is necessary to process the request and to prevent abuse.

4.3. AI model providers. The Processor engages providers of large language models as sub-processors for the generation of answers, drafts and classifications. Depending on the Feature, the content of a query, message or e-mail, the relevant product information, order context and page context are transmitted to the model provider. The current providers and their locations are listed at https://yasan.ai/subprocessors.

4.4. Consent signal and identifiers. Where the Controller enables Features that store an identifier in the End User’s browser: (a) the Controller is solely responsible for obtaining any legally required consent and for informing End Users; (b) the Processor shall technically honour the consent signal made available by the Controller through a supported mechanism and shall not create or store a visitor identifier in the absence of a positive signal; (c) upon withdrawal of consent, the Processor shall cease collection for the respective visitor and delete the visitor identifier from the browser; (d) the Processor shall offer the Controller a setting to disable cross-visit linking of search and chat history.

4.5. Data minimisation built into the Service. From the page address, only origin and path are stored with conversations, searches and analytics events (query strings and fragments are discarded); from the basket, only item count, total value and currency; one-time verification codes are stored only as cryptographic hashes (unless an End User types a code into a chat message); as-you-type suggestions are not stored; relevance-assessment requests carry no visitor or session identifier, and only their technical results, without the query text, are kept for a limited time; IP addresses are not stored with conversations or searches; they are recorded in the error and performance logs of the Service, which are deleted within 90 days; where the End User has consented to analytics, the IP address may be recorded with analytics events and is deleted with them no later than 24 months after creation.

4.6. Retention. The Processor deletes End User data of the Chat Widget, AI Search and Analytics Feature (conversations, search records, analytics events) no later than 24 months after creation, and in any event within 30 days after the Controller’s account is closed (Section 9.2), save for backups, which are overwritten in the ordinary backup cycle (no longer than 90 days). E-mail support history (threads, drafts, replies and derived embeddings) is retained for as long as the Controller’s account exists so that agents have access to past conversations, and is deleted earlier on the Controller’s instruction or on a platform privacy request. Order and customer data retrieved from the Controller’s e-commerce platform is read on demand and not stored separately; order details quoted in a conversation, e-mail or proposed action are kept as part of that record; the Processor does not keep a copy of the Controller’s customer list. Integration credentials and access tokens are erased immediately when the integration is disconnected or the app is uninstalled. Records of searches that are associated with neither a visitor identifier nor a conversation cannot be attributed to an individual and are therefore not retrievable in response to a data subject request; they are deleted within the same 24-month period. Operational metrics of AI model calls that contain no personal data (provider, token counts, latency, cost, result counts) are retained beyond this period for service operation.

4.7. Special categories. The Service does not require and does not solicit special categories of personal data. Free-text queries and messages are authored by End Users and may incidentally contain such data, in particular where the Controller’s catalogue relates to health. The Controller remains responsible under Section 2.1(d). The Processor applies the measures in Schedule 2 to all free-text content regardless of its classification.

4.8. Location of processing. The Processor hosts the Service’s databases and application servers in the European Union. Sub-processors may process data outside the EU as described in Section 8 and at https://yasan.ai/subprocessors.


5. SUB-PROCESSORS

5.1. General authorisation. The Controller grants the Processor a general authorisation to engage sub-processors for the processing of personal data under this DPA. The sub-processors engaged as of the Effective Date are listed in Schedule 3 and at https://yasan.ai/subprocessors (the “Sub-processor List”) and are approved by the Controller.

5.2. Changes. The Processor shall inform the Controller of any intended addition or replacement of a sub-processor at least 7 days before the new sub-processor starts processing personal data, by updating the Sub-processor List and by e-mail from [email protected] to the Controller’s account e-mail address (or by in-app notification). The Controller is responsible for keeping its account e-mail address current and for ensuring e-mails from [email protected] are received. Where a change is required urgently for security, legal or availability reasons, the Processor may give shorter notice and will explain the reason.

5.3. Objection. The Controller may object to the intended change on reasonable, documented data-protection grounds by written notice to [email protected] within 7 days of the notification. The Parties shall discuss the objection in good faith. If the Processor does not propose a reasonable alternative within 14 days of the objection, the Controller may terminate the affected part of the Service (and, if the Service cannot reasonably be provided without the sub-processor, the Terms) by written notice with effect from the end of the notice period, with a pro-rata refund of prepaid Fees for the period after termination; this is the Controller’s sole remedy. If the Controller does not object within the period, or continues to use the Service after the sub-processor starts processing, the sub-processor is deemed approved.

5.4. Sub-processor contracts. The Processor shall impose on each sub-processor, by written contract, data protection obligations providing at least the same level of protection as this DPA, in particular sufficient guarantees to implement appropriate technical and organisational measures, and shall remain fully liable to the Controller for the performance of the sub-processor’s obligations.

5.5. Third-party services connected by the Controller. Services, applications and systems that the Controller itself connects to the Service (its e-commerce Platform, mailbox provider, CRM, help desk, consent-management platform and similar) are not sub-processors of the Processor; the Controller contracts with them directly.


6. DATA SUBJECT REQUESTS

6.1. The Controller is responsible for handling requests of data subjects. On the Controller’s request, the Processor shall export, correct and delete personal data of identifiable data subjects (by e-mail address, visitor identifier, session identifier or conversation identifier) across all systems in which the Processor stores it, including analytics storage. Erasure shall be executed within 30 days of the Controller’s instruction and shall cover message bodies, attachments, conversation and search records, analytics rows and derived embeddings, save for backups, which are overwritten in the ordinary backup cycle. Privacy requests received through an e-commerce platform’s mechanism (such as Shopify’s customers/data_request, customers/redact and shop/redact webhooks) are logged on receipt with a 30-day deadline and treated as the Controller’s instruction to export or erase, respectively.

6.2. Where a data subject addresses a request directly to the Processor, the Processor shall not respond on the merits but shall forward the request to the Controller without undue delay and inform the data subject that the request has been forwarded, unless the request concerns processing for which the Processor is itself the controller.

6.3. Assistance beyond the functions of the Service is provided to the extent commercially reasonable and may be charged at the Processor’s then-current rates.


7. PERSONAL DATA BREACH, DPIA AND PRIOR CONSULTATION

7.1. The Processor shall notify the Controller without undue delay, and in any event within 48 hours, after becoming aware of a personal data breach affecting the Controller’s personal data, to the Controller’s account e-mail address. The notification shall, to the extent known, describe the nature of the breach, the categories and approximate number of data subjects and records concerned, the likely consequences, the measures taken or proposed, and a contact point; information may be provided in phases as it becomes available. The Processor shall assist the Controller in meeting its obligations under Articles 33 and 34 GDPR. The Processor’s notification is not an acknowledgement of fault or liability.

7.2. The Controller is responsible for notifying supervisory authorities and data subjects. The Controller shall not name the Processor in any public statement about a breach without the Processor’s prior consent, except where required by law.

7.3. Taking into account the nature of the processing and the information available, the Processor shall provide reasonable assistance to the Controller with data protection impact assessments and prior consultations relating to the Service, primarily by making available this DPA, Schedule 2, the Sub-processor List and its standard security documentation. Further assistance may be charged at the Processor’s then-current rates.


8. INTERNATIONAL TRANSFERS

8.1. The Controller authorises the Processor and its sub-processors to process personal data outside the EU/EEA and the UK as described in the Sub-processor List, provided that the transfer is covered by one of the following safeguards:

(a) an adequacy decision of the European Commission (for EU/EEA data) or adequacy regulations of the UK Secretary of State (for UK data), including the EU–U.S. Data Privacy Framework and its UK Extension where the recipient is certified;

(b) the Standard Contractual Clauses adopted by the European Commission under Decision (EU) 2021/914 (the “SCCs”), with, for UK data, the UK International Data Transfer Addendum issued by the Information Commissioner under s.119A of the Data Protection Act 2018 (the “UK Addendum”), together with supplementary measures where required; or

(c) another valid transfer mechanism under Data Protection Law.

8.2. The Controller authorises the Processor to conclude the SCCs and the UK Addendum with sub-processors in its own name and on behalf of the Controller (Module 3 — processor to processor) in respect of such transfers.

8.3. To the extent that the Controller is established outside the EU/EEA in a country without an adequacy decision and the Processor’s provision of the Service constitutes a transfer from the Controller to the Processor requiring a transfer mechanism under the Controller’s law, the Parties shall enter into the appropriate mechanism on request. For Controllers established in the UK, the transfer to the Processor in the Czech Republic is covered by the UK’s adequacy regulations for the EEA.

8.4. The Processor shall inform the Controller if a transfer mechanism relied upon ceases to be valid and shall use reasonable efforts to implement an alternative; the Controller’s sole remedy if no alternative is available within a reasonable period is termination of the affected Feature in accordance with Section 5.3.


9. DELETION AND RETURN OF DATA

9.1. During the term, the Controller may request the export and deletion of its data as described in Section 6.1.

9.2. Upon termination of the Terms, meaning closure of the Controller’s account at the Controller’s request or by the Processor in accordance with the Terms (the cancellation or expiry of a paid Plan or trial does not by itself end the provision of the Service), the Processor shall delete all personal data processed on behalf of the Controller within 30 days, unless the Controller requests return of the data in a commonly used electronic format before the end of that period (which the Processor will provide to the extent reasonably practicable), and unless EU, Member State or UK law requires continued storage. Backups are overwritten in the ordinary backup cycle. Aggregated and anonymised data is not deleted.

9.3. Upon written request, the Processor shall confirm deletion in writing.


10. AUDITS AND INFORMATION

10.1. The Processor shall make available to the Controller, on request, the information reasonably necessary to demonstrate compliance with Article 28 GDPR, primarily in the form of this DPA, Schedule 2, the Sub-processor List, completed security questionnaires and, where available, third-party audit reports or certifications. The Controller shall first rely on such documentation.

10.2. Where the documentation is not sufficient to demonstrate compliance, or where a supervisory authority requires it, the Controller may conduct an audit, including an inspection, of the Processor’s processing of the Controller’s personal data, subject to the following: (a) no more than once in any 12-month period, unless required by a supervisory authority or following a personal data breach affecting the Controller; (b) at least 30 days’ prior written notice, with a description of scope; (c) during business hours, in a manner that does not unreasonably disrupt the Processor’s business and does not give access to data of other customers, the Processor’s trade secrets or security-sensitive information; (d) by the Controller or an independent auditor bound by confidentiality and not a competitor of the Processor; (e) the Controller bears all costs of the audit, including the Processor’s reasonable time at its then-current rates; (f) the Controller shall share the audit report with the Processor and treat it as the Processor’s confidential information.

10.3. The Processor shall inform the Controller of any inspection or request by a supervisory authority concerning the Controller’s personal data, where legally permitted.


11. LIABILITY

11.1. Each Party is liable to data subjects in accordance with Article 82 GDPR and to the other Party in accordance with Data Protection Law and the Terms.

11.2. The limitations and exclusions of liability in the Terms apply to this DPA and to all claims arising out of or in connection with the processing of personal data, in aggregate for the Terms and this DPA together, to the maximum extent permitted by law.

11.3. The Controller is fully responsible for the lawfulness of its instructions, the purposes of processing and the data it entrusts to the Processor, and shall indemnify the Processor as set out in Section 2.4 and in the Terms.

11.4. Each Party shall promptly inform the other of any proceedings, inspections or claims relating to the processing under this DPA, and the Parties shall cooperate in good faith in their defence.


12. TERM, CHANGES AND FINAL PROVISIONS

12.1. This DPA applies for as long as the Processor processes personal data on behalf of the Controller under the Terms, and the provisions on deletion, confidentiality and liability survive its termination.

12.2. The Processor may amend this DPA in accordance with Section 14 of the Terms, in particular to reflect changes in law, guidance of supervisory authorities, standard contractual clauses or the Service.

12.3. This DPA is governed by the laws of the Czech Republic and the courts of the Czech Republic have exclusive jurisdiction, in accordance with the Terms, without prejudice to the governing law and forum provisions of the SCCs and the UK Addendum and to the rights of data subjects under Data Protection Law.

12.4. If any provision of this DPA is invalid or unenforceable, the remaining provisions remain in force and the Parties shall replace the invalid provision with a valid one that most closely achieves its purpose. This DPA, with the Terms, constitutes the entire agreement regarding the processing of personal data and supersedes any prior data processing terms between the Parties. The Controller’s own data processing terms, questionnaires or purchase conditions do not apply unless expressly accepted in writing by the Processor.

12.5. The English version of this DPA prevails over any translation.


SCHEDULE 1 — DETAILS OF THE PROCESSING

Subject matter. Provision of the Yasan AI sales and customer-service assistant (Chat Widget, AI Search, Email Agent, Analytics Feature and related administration interface, integrations and APIs) to the Controller.

Duration. For the term of the Terms and until deletion in accordance with Section 9.

Nature and purpose. Collection, storage, retrieval, analysis, transmission to AI model providers, generation of answers and drafts, execution of actions in the Controller’s systems, statistical evaluation, and deletion, for the purposes of: (i) answering questions and recommending products to visitors of the Controller’s website through AI chat; (ii) providing AI-assisted product search on the Controller’s website; (iii) automating the Controller’s customer communication by e-mail and related channels, including retrieval of context from and execution of actions in the Controller’s systems; (iv) where enabled, measuring the performance of the assistant and the website for the Controller; (v) automated assessment of the relevance of search results and a daily quality evaluation of search results on a sample of recent queries, for the Controller’s shop.

Categories of data subjects.

  • Visitors and customers of the Controller’s website(s) who interact with the Chat Widget or AI Search, including visitors who are not registered customers (End Users);
  • Persons who send e-mails or messages to the Controller’s connected mailboxes or channels, and persons referred to in such communications;
  • Customers of the Controller whose order, account or profile data is retrieved from the Controller’s systems;
  • The Controller’s employees, contractors and agents who use the Service (Users), and persons mentioned in the Controller’s knowledge base or instructions.

Categories of personal data.

  • Chat Widget: content of conversations, AI responses, session identifier, page URL and language, e-mail address provided by the visitor, hashed verification codes, order data retrieved after verification, basket context, timestamps;
  • AI Search: search queries, follow-up messages, products displayed, filters applied and results on screen, assistant answers, page address (origin and path), basket summary (item count, value, currency), language, timestamps, technical delivery data; where consent is given, a random visitor identifier; session identifier; technical relevance-assessment results (no query text, no visitor or session identifiers);
  • Email Agent: e-mail addresses, names, message content, attachments, headers, labels, timestamps, drafts and replies, data retrieved from connected systems (orders, invoices, delivery status, customer profiles, support history), records of actions executed;
  • E-commerce platform data (Shoptet, Shopify, WooCommerce, custom API): product catalogue (titles, descriptions, variants, prices, stock, images, translations); orders and line items, notes and comments, fulfilment, financial and return status, and the customer named on an order (name, e-mail, phone number, billing and shipping address), read on demand for a specific question or permitted action (including updating the shipping address and its phone number); theme/widget settings; store languages and markets. No copy of the Controller’s customer list is retained;
  • Analytics Feature: events of website visitors (page views, interactions with the assistant, add-to-cart and other basket events as made available by the Controller’s Platform), linked to a pseudonymous visitor identifier where the visitor has consented; technical browser data;
  • Users: name, e-mail, role, credentials (hashed), activity in the administration interface;
  • Security (processed for the Controller only insofar as tied to its records): IP address and user agent used transiently for rate limiting and for the derivation of a daily rotating pseudonymous identifier; IP address recorded in the error and performance logs of the Service, deleted within 90 days.

Special categories of personal data. None intended. Incidental special-category data may be contained in free-text content authored by data subjects (see Section 4.7).

Frequency. Continuous, for as long as the Controller uses the Service.

Retention. See Section 4.6.

Sub-processors. See Schedule 3.


SCHEDULE 2 — TECHNICAL AND ORGANISATIONAL MEASURES

The Processor implements and maintains at least the following measures (Article 32 GDPR):

1. Encryption and pseudonymisation

  • Encryption in transit of all personal data using TLS 1.2 or higher; encryption at rest of databases, object storage and backups using AES-256 or equivalent.
  • One-time verification codes of End Users stored only as cryptographic hashes (save where typed into a chat message); IP addresses not stored with conversations or searches (they are kept only in error and performance logs, deleted within 90 days, and, with analytics consent, in analytics events, deleted within 24 months); the daily visitor-counting identifier derived from IP address and user agent uses a key derived anew for every calendar day, and records are not linked across days.
  • Visitor identifiers are random values generated in the browser, created only on a positive consent signal and removed on withdrawal.

2. Confidentiality and access control

  • Role-based access control; production access restricted to named engineering staff on a need-to-know basis; mandatory multi-factor authentication for all production, cloud-console and code-repository access; individual accounts (no shared credentials); prompt revocation on role change or departure.
  • Access to Service Content by staff is limited to support requested by the Controller, security investigations, quality review for the Controller’s account, or legal requirements; staff switching into a Customer’s account is logged.
  • All staff and contractors bound by written confidentiality obligations; data protection awareness training.
  • Logical separation of each Customer’s data (tenant isolation by organisation identifier at the application and query level); separation of production, staging and development environments; no production personal data in development or test environments.

3. Integrity and availability

  • Hosting in ISO 27001 / SOC 2 certified data centres in the European Union; infrastructure as code; automated deployment with code review; dependency and vulnerability scanning; timely patching.
  • Encrypted, automated backups stored in a separate availability zone with defined retention (overwritten within 90 days); periodic restore tests.
  • Rate limiting, bot protection and web application firewall at the edge; DDoS mitigation by the edge provider; monitoring and alerting of availability, errors and anomalous access.
  • Logging of staff access to Customer accounts and of the extraction of integration credentials.

4. Processes for regular testing, assessment and evaluation

  • Documented information-security and incident-response procedures; personal-data-breach procedure with notification to Controllers under Section 7.
  • Periodic review of access rights, sub-processors, and the effectiveness of the measures; vulnerability scanning; external security review at least annually or upon material change.
  • Secure software development practices including code review for all production changes.

5. Data subject rights and deletion

  • Procedures for export, correction and targeted erasure of personal data by e-mail address, visitor identifier, session identifier or conversation identifier across all storage systems (primary database and analytics storage); scheduled deletion of widget data older than 24 months; deletion within 30 days of termination.

6. AI-specific measures

  • Enterprise API agreements with model providers prohibiting training on and limiting retention of Customer content; no use of consumer-grade AI services; model providers listed in the Sub-processor List; abuse filters and system-level instructions limiting the assistant to the Controller’s catalogue and configured scope; AI disclosure and privacy link displayed in every widget.
  • Google API Services User Data Policy (Limited Use) compliance for data from Google Workspace integrations.

The Processor shall provide a current description of its measures on request, and may update this Schedule provided the overall level of protection is not materially reduced.


SCHEDULE 3 — APPROVED SUB-PROCESSORS

The current list is maintained at https://yasan.ai/subprocessors. As of the Effective Date it includes:

Sub-processor Entity Purpose Location of processing Transfer mechanism
DigitalOcean DigitalOcean, LLC Cloud hosting and data storage EU — (EU) ; SCCs/DPF for support access from the US
Cloudflare Cloudflare, Inc. Content delivery and security EU; global network; USA EU–U.S. DPF (certified); SCCs
Google Google Ireland Limited / Google LLC AI models; business productivity tools EU; USA EU–U.S. DPF (certified); SCCs
OpenAI OpenAI Ireland Ltd / OpenAI, L.L.C. AI models USA; EU where available EU–U.S. DPF (certified); SCCs
Anthropic Anthropic Ireland, Limited / Anthropic, PBC AI models USA EU–U.S. DPF (certified); SCCs
TypeSafe AI TypeSafe AI, Inc., 255 California St, Suite 1300, San Francisco, CA 94117, USA AI models USA EU SCCs (Module 3) and UK Addendum, incorporated in TypeSafe’s DPA; not DPF-certified
Amazon Web Services Amazon Web Services EMEA SARL AI model hosting EU; USA EU–U.S. DPF (certified); SCCs
Tinybird Tinybird Co. Analytics data storage EU — (EU); SCCs for support access
Postmark ActiveCampaign, LLC Transactional e-mail delivery USA EU–U.S. DPF (certified); SCCs
LangSmith LangChain, Inc. Quality monitoring of the Service EU — (EU); SCCs for support access
Smartlook Smartlook.com, s.r.o. (Cisco) Product analytics of the administration interface (Users only; End Users are not tracked) EU — (EU)
Stripe Stripe Payments Europe, Ltd. Payment processing and invoicing EU; USA SCCs; DPF
Sentry Functional Software, Inc. Error monitoring of the Service EU — (EU); SCCs for support access
OpenStreetMap Nominatim OpenStreetMap Foundation Address lookup for some integrations UK UK adequacy decision
Linear Linear Orbit, Inc. Issue tracking USA EU–U.S. DPF (certified); SCCs
CodeRabbit CodeRabbit, Inc. Software development tooling (no personal data by design) USA SCCs

SCHEDULE 4 — UK ADDENDUM

Where UK Data Protection Law applies to the Controller’s processing:

  1. References in this DPA to the GDPR, to EU or Member State law and to supervisory authorities are read as references to the UK GDPR, UK law and the Information Commissioner respectively, as the context requires.
  2. Transfers of personal data from the UK to the Processor in the Czech Republic are made under the UK’s adequacy regulations for EEA countries.
  3. Onward transfers by the Processor to sub-processors outside the UK and the EEA are made under the UK Extension to the EU–U.S. Data Privacy Framework where the recipient is certified, and otherwise under the EU SCCs incorporating the UK International Data Transfer Addendum (Version B1.0, in force 21 March 2022), with the Parties’ details, the processing details in Schedule 1, the measures in Schedule 2 and the sub-processors in Schedule 3 forming Tables 1 to 3 of the UK Addendum, and with the Processor entitled to end the Addendum on the terms set out in its Section 19.
  4. The Controller is responsible for its own obligations under UK Data Protection Law, including the Privacy and Electronic Communications (EC Directive) Regulations 2003 (as amended). The Service requires a positive consent signal before storing a visitor identifier for UK End Users in the same way as for EU End Users; the Service does not rely on the statistical-analytics exemption.

Let’s Whisper s.r.o. · Křižíkova 148/34, 186 00 Praha 8, Czech Republic · IČO 23849959 · [email protected]

  • Terms of Service
  • Privacy Policy
  • Data Processing Agreement
  • Sub-processors
  • Shopify app terms
  • Shoptet add-on terms
  • AI assistant privacy notice

Previous versions ·

Let’s Whisper s.r.o. · Křižíkova 148/34, 186 00 Praha 8 · IČO 23849959 · [email protected]