KaiwaDB
DocsOpen dashboard

Effective 9 October 2026

Data Processing Agreement

This Data Processing Agreement ("DPA") forms part of the KaiwaDB Terms of Service between DEEP VISION s.r.o., ID No. (IČO) 27540065, Hlaváčova 207, Zelené Předměstí, 530 02 Pardubice, Czech Republic ("Processor", "we", "us") and the customer organization that accepts the Terms ("Customer", "you").

It sets out the terms required by Article 28 of the General Data Protection Regulation (EU) 2016/679 ("GDPR") for personal data we process on your behalf. You accept this DPA by accepting the Terms. If you need a countersigned copy, contact info@kaiwadb.com.

1. Definitions

  • "Personal data", "processing", "controller", "processor", "data subject" and "personal data breach" have the meanings given in the GDPR.
  • "Customer Personal Data" means personal data that you or your users submit to the Service, or that the Service processes from your databases, as described in Annex 1.
  • "Sub-processor" means a third party we engage to process Customer Personal Data.

Personal data about your users' accounts, which we process as a controller, is covered by our Privacy Policy, not by this DPA.

2. Roles

You are the controller of Customer Personal Data and we are your processor. If you act as a processor for another controller, we act as your sub-processor, and you confirm that the controller has authorized our processing.

3. Your responsibilities

  • You have a lawful basis for the processing and have given data subjects any information the law requires.
  • You decide which databases and data you make available through the Service and which features you use.
  • If you use features that store query results, such as the Telegram integration, for special categories of personal data (Article 9 GDPR) or data on criminal convictions (Article 10 GDPR), you are responsible for ensuring this is lawful and for any additional safeguards it requires.
  • You connect the tunnel with a database user that has only the permissions it needs.
  • Your instructions to us comply with the GDPR.

4. Our obligations

4.1 Instructions

We process Customer Personal Data only on your documented instructions. The Terms, this DPA, and your use and configuration of the Service are your instructions. If EU or Member State law requires other processing, we will tell you before processing unless that law prohibits it. We will tell you if we believe an instruction infringes the GDPR.

4.2 No other use

We do not sell Customer Personal Data, do not use it to train AI models, and do not process it for our own purposes.

4.3 Confidentiality

Everyone we authorize to process Customer Personal Data is bound by confidentiality.

4.4 Security

We implement the technical and organizational measures in Annex 2, as required by Article 32 GDPR.

4.5 Assistance

  • If we receive a request from a data subject about Customer Personal Data, we forward it to you and do not answer it ourselves unless you instruct us to. We help you respond, taking into account the nature of the processing.
  • We help you meet your obligations under Articles 32 to 36 GDPR (security, breach notification, data protection impact assessments and prior consultation), using the information available to us.

4.6 Personal data breaches

We notify you without undue delay, and in any case within 48 hours, after becoming aware of a personal data breach affecting Customer Personal Data. We give you the information you need to meet your own notification obligations, as far as it is available, and update it as we learn more.

4.7 Deletion and return

When the Terms end, we delete Customer Personal Data within 30 days, unless EU or Member State law requires us to keep it. If you ask before the Terms end, we first provide a copy in a common machine-readable format. Deleted data may remain in backups until the backup rotation overwrites it; until then it stays protected and is not otherwise processed.

4.8 Audits

We make available the information necessary to demonstrate compliance with this DPA and Article 28 GDPR, and we allow for and contribute to audits, including inspections, by you or an auditor you mandate who is bound by confidentiality. We will first try to answer your questions in writing. On-site audits require 30 days' notice, take place during business hours, are at your cost, and are limited to once every 12 months unless a supervisory authority requires otherwise or a personal data breach has occurred.

5. Sub-processors

  • You give us general authorization to engage the sub-processors listed in Annex 3.
  • We notify you by email at least 30 days before adding or replacing a sub-processor and update Annex 3. You may object on reasonable data protection grounds within that period. If we cannot address your objection, you may terminate the affected part of the Service without penalty.
  • We impose on each sub-processor, by contract, data protection obligations equivalent to those in this DPA. We remain liable to you for our sub-processors' performance.
  • Telegram. If you enable the Telegram integration, you instruct us to transmit data to Telegram. Telegram provides its service under its own terms as a provider you have chosen and is not our sub-processor.

6. International transfers

We transfer Customer Personal Data outside the European Economic Area only with a safeguard under Chapter V GDPR: an adequacy decision, including the EU–US Data Privacy Framework for certified recipients, or the European Commission's Standard Contractual Clauses.

7. Liability

Each party's liability under this DPA is subject to the limitations in the Terms, except where applicable law does not permit such limitation.

8. Term and precedence

This DPA applies for as long as we process Customer Personal Data. If it conflicts with the Terms on the processing of personal data, this DPA prevails. It is governed by the laws of the Czech Republic.

Annex 1: Details of processing

Subject matterProvision of the KaiwaDB Service
DurationFor the term of the Terms, plus the deletion period in section 4.7
Nature of processingCollection, storage, transmission, retrieval, use to generate queries and compose replies, and deletion
PurposeProviding the Service to Customer under the Terms
Categories of data subjectsCustomer's authorized users, as authors of questions and messages; individuals whose personal data is stored in Customer's databases, such as Customer's customers, employees or patients
Types of personal dataPersonal data contained in schema metadata, aliases or descriptions; personal data contained in questions; Telegram conversation history, including query results and notifications included in replies; query results passing through the tunnel, in transit only
Special categoriesOnly where Customer's databases contain them and Customer chooses to query them (see section 3)
RetentionStored content is kept while Customer's account exists and deleted within 30 days after it ends. Query results outside the Telegram integration are not stored.

Annex 2: Technical and organizational measures

  • Encryption in transit. All connections between users, the Service, the tunnel and our sub-processors use TLS.
  • Tenant isolation. Each customer organization's data is isolated from other organizations.
  • Access control. Access to production systems and Customer Personal Data is limited to personnel who need it.
  • Data minimization. Queries are generated from schema metadata. Outside the Telegram integration, query results are not stored.
  • Tunnel architecture. The tunnel runs on Customer's infrastructure and opens the connection to our servers. Customer controls the database permissions it uses.
  • Restricted query language. Our pipeline language is designed to prevent destructive operations.
  • AI providers. Requests are routed only to model providers that do not retain prompts or outputs.
  • Incident response. Personal data breaches are handled and notified as set out in section 4.6.

Annex 3: Sub-processors

Sub-processorPurposeLocation and transfer safeguard
VSHosting s.r.o., Praha, Czech RepublicBackend servers: query generation service and tunnel connectionsCzech Republic (EU); no transfer
Vercel Inc.Website and dashboard hostingUSA; EU–US Data Privacy Framework
Supabase Pte. Ltd.Application database, authentication and user accountsData hosted in the EU (Frankfurt, Germany); contracting entity in Singapore; Standard Contractual Clauses
ResendTransactional email deliveryUSA; EU–US Data Privacy Framework
OpenRouter and the zero-data-retention model providers it routes toAI query generation and reply compositionUSA; Standard Contractual Clauses