1. Parties, scope and precedence
This DPA forms part of an accepted BotStacks service agreement only when adopted by the parties with completed schedules. Customer is controller (or a processor authorized by its controller); BotStacks is processor (or subprocessor) for covered Customer Personal Data. Each party remains responsible for its independent controller activities. Applicable Data Protection Law means the privacy and data-protection laws applying to the covered processing. This DPA prevails over conflicting service terms on data protection. Nothing here limits non-waivable data-subject rights.
2. Documented instructions
BotStacks will process Customer Personal Data only on documented instructions, including transfers. For processing governed by Article 28 GDPR, an exception applies only where Union or Member State law to which BotStacks is subject requires processing; BotStacks will inform Customer of that requirement before processing unless that law prohibits notice on important grounds of public interest. Other legal demands must be assessed under applicable data-protection and transfer rules and do not create a blanket exception for third-country law. BotStacks will promptly inform Customer if an instruction appears to infringe applicable data-protection law. Customer is responsible for lawful collection, notices and instructions.
3. Personnel and safeguards
Persons authorized to process personal data must be bound by confidentiality obligations and receive access only as necessary. BotStacks will implement risk-appropriate technical and organizational measures under Schedule 2 and review their effectiveness. Measures must not be materially reduced during the term without equivalent protection. This undertaking becomes effective only with an approved, accurate schedule; it does not certify controls that have not been verified.
4. Subprocessors
Customer grants general authorization only to providers identified in the completed Schedule 3. BotStacks will impose materially equivalent data-protection duties by written contract, remain responsible for its subprocessor obligations, and give at least 30 days’ prior notice of additions or replacements. Customer may reasonably object on data-protection grounds during that period. The parties will seek an alternative; if none is reasonably available, Customer may terminate the affected service before the new processing begins and receive a proportional refund of unused prepaid fees. No undisclosed provider is authorized by this document.
5. Requests and cooperation
Taking account of the nature of processing, BotStacks will assist Customer with access, correction, deletion, restriction, portability, objection and other applicable data-subject requests. It will forward requests received directly and not respond substantively without instructions unless legally required. BotStacks will provide reasonable assistance with security obligations, breach notifications, impact assessments and regulator consultations, considering the information available to it. Any additional fees for exceptional assistance must be agreed in advance and cannot prevent mandatory assistance.
6. Personal-data breaches
BotStacks will notify Customer without undue delay after becoming aware of a personal-data breach affecting covered data. Initial notice will include available facts on the incident, categories and approximate numbers of affected people and records, likely consequences, mitigation and a contact point; missing facts will follow as available. BotStacks will contain, investigate and remediate the incident and cooperate with Customer. No arbitrary wait for a completed investigation is permitted. Notifications are not admissions of liability.
7. Return and deletion
At Customer’s choice following the end of processing, BotStacks will return or delete covered personal data and existing copies unless law requires retention. Schedule 2 must state export method, deadlines, backup expiry, derived index deletion and provider deletion handling. Required retained data must be isolated, protected and processed only for the required purpose. BotStacks will provide confirmation on request. Service exit periods do not override mandatory DPA deletion/return obligations.
8. Information and audits
BotStacks will make available information necessary to demonstrate compliance and allow and contribute to audits and inspections by Customer or its mandated independent auditor. Reasonable notice, confidentiality and security procedures may protect other customers and systems but must not defeat statutory audit rights or urgent regulator/incident needs. Existing independent reports may be used where adequate; they are not the sole remedy. BotStacks will address substantiated deficiencies and cooperate with competent supervisory authorities.
9. International transfers and US state processing
No restricted transfer may occur without the required lawful mechanism. Complete the exporter/importer roles, countries, transfer assessment, applicable EU SCC module and annexes, UK addendum/IDTA where needed, and supplementary measures before such processing. A hyperlink or reference alone does not execute these instruments. Where US state service-provider/contractor restrictions apply, BotStacks will not sell or share covered data, retain/use/disclose it outside specified service purposes or the direct business relationship, or combine it with unrelated data except as law permits. BotStacks will notify Customer if it can no longer comply and allow reasonable steps to stop and remediate unauthorized processing.
Schedule 1 — Processing particulars
Subject matter: operating customer-configured AI assistants, retrieval, hosting, support and security. Nature: ingestion, storage, indexing/embedding, retrieval, inference, transmission, access, export and deletion as enabled. Purpose: deliver the contracted Services on Customer’s instructions. Duration: subscription and agreed exit/retention period, subject to lawful exceptions.
Data subjects: Customer personnel, authorized users, website visitors, correspondents and people represented in lawfully supplied knowledge sources. Categories: account identifiers, contact information, conversation content, source documents, assistant instructions, outputs and associated technical metadata. Special categories are excluded unless separately agreed. Customer must complete any customer-specific categories, frequency, locations and controller contact details.
Schedule 2 — Security and retention — customer-specific schedule
Record verified access controls, tenant isolation, authentication, encryption in transit/at rest, key management, vulnerability/patch management, backup and restore, logging, incident response, employee confidentiality, deletion of vector/index/provider copies, business continuity, export method, retention durations and backup expiry. For each, identify the accountable owner and verification evidence. No SOC 2, ISO, HIPAA, fixed incident deadline, or data-residency guarantee is implied by an empty schedule.
Schedule 3 — Providers, transfers and adoption — customer-specific schedule
The customer-specific schedule must identify the applicable providers, services, data categories, purposes, regions, transfer safeguards and notice contact. The parties must also identify their legal names, acceptance or signatories, agreement date, privacy contacts and order. These published terms are available for adoption from the effective date; a customer DPA applies only when accepted with its required schedules. Publication alone does not execute transfer instruments or approve an unverified processing arrangement.