Data processing agreement
An agreement on the processing of personal data under Article 28 of Regulation (EU) 2016/679 (GDPR). It is part of the terms of service and you conclude it by creating an office. We send a signed copy on request.
This is a translation. If it differs from the Czech version, the Czech version prevails.
1. Parties and roles
1.1 The controller is the customer, that is, the office using Kóta. The processor is Pavel Adámek, company ID (IČO) 14229650, registered office Řehákova 907, 549 41 Červený Kostelec (“we”).
1.2 The agreement covers personal data that is part of the content put into the service or created in it. We process data about accounts, billing and the operation of the service as an independent controller under the privacy notice.
1.3 If the customer itself processes the data as a processor for its client, we are a sub-processor and the customer is responsible for having permission to engage us.
2. Instructions
2.1 We process personal data only on the controller’s documented instructions. The instructions consist of this agreement, the terms of service, the office’s settings in the service and the actions of users (such as uploading a file, asking a question, deleting a project). We accept further instructions in writing from an office administrator.
2.2 If we consider an instruction unlawful, we tell the controller without undue delay and need not carry it out until it is clarified.
2.3 We do not process personal data for our own purposes, do not sell it and do not use it to train artificial intelligence models. If EU or Czech law requires us to process it, we inform the controller beforehand unless the law forbids that.
3. Confidentiality
We give access only to persons who are bound by confidentiality and need the access to perform the contract.
4. Security
We have adopted and maintain the technical and organisational measures in Annex 2. We may change the measures as long as the level of security is not reduced. The controller acknowledges that it has assessed whether the measures match the risk of its data.
5. Sub-processors
5.1 The controller gives us a general authorisation to engage the sub-processors in the public list of subprocessors.
5.2 We announce an intention to add or replace a sub-processor to office administrators by e-mail and publish it in the list at least 30 days in advance. We may use a shorter period only when the change is necessary to avert a security threat or an outage; even then we announce it without undue delay.
5.3 The controller may raise a reasoned objection to the change within that period. If we cannot find a solution together, the controller may terminate the contract as of the day the change takes effect and we refund the proportionate part of the prepaid price.
5.4 We contractually impose on sub-processors the same data protection obligations as we have under this agreement, and we are liable to the controller for their performance.
5.5 Providers the controller connects itself (its own key for an artificial intelligence provider, an outside assistant) are not our sub-processors. We pass data to them on the controller’s instruction.
6. Transfers outside the EEA
Some sub-processors process data outside the European Economic Area, mainly in the United States. The transfer relies on an adequacy decision or on the European Commission’s standard contractual clauses. Who, where and on what basis is stated in the list of subprocessors. The controller agrees to these transfers.
7. Assistance
7.1 If a data subject contacts us with a request concerning an office’s content, we pass it to the controller without undue delay and do not answer it ourselves.
7.2 We help the controller by reasonable means to meet its obligations towards data subjects, on security, on reporting personal data breaches and on data protection impact assessments. The functions of the service (search, export, correction, deletion) serve this first; we provide assistance beyond them to a reasonable extent free of charge.
8. Personal data breaches
8.1 We notify office administrators of a personal data breach by e-mail without undue delay, within 48 hours of becoming aware of it at the latest.
8.2 The notice contains what we know at that moment: the nature of the breach, the categories and approximate volume of data affected, the likely consequences, the measures taken and proposed, and a contact. We add further information as it becomes available.
9. Audit
9.1 On request we give the controller the information needed to show that we comply with this agreement, including answers to a reasonable written questionnaire, at most once a year.
9.2 If that is not enough, we allow the controller, or an auditor it appoints who is bound by confidentiality, to carry out an inspection at most once a year, announced at least 30 days in advance, during working hours and in a way that does not endanger other customers’ data. The controller bears the costs of the inspection. The frequency limit does not apply after a breach or at the request of a supervisory authority.
10. Term, return and deletion
10.1 The agreement lasts for as long as the service is provided and thereafter for as long as we hold the controller’s personal data.
10.2 After the service ends we return the personal data at the controller’s choice (the export under article 13 of the terms of service) and delete it within the periods stated there, unless EU or Czech law requires us to keep it.
10.3 What users delete while the service is provided is removed as follows: items in the trash after 30 days, and files and derived data that nothing refers to any more within a further 7 days.
11. Liability
Liability between the parties is governed by article 11 of the terms of service. This does not affect the rights of data subjects or the powers of the supervisory authority.
Annex 1: Description of the processing
| Subject matter and purpose | operating Kóta: storing and organising documentation, extracting text and data, search, answering questions, drafting documents |
| Nature of the processing | storage, reading, automated analysis (text recognition, classification, computing vector representations, processing by a language model), display, export, deletion |
| Duration | for the term of the contract and the period for return and deletion |
| Data subjects | the controller’s employees and collaborators; its clients, investors and builders; designers, authorised professionals, contractors; officials; owners of neighbouring plots and other persons named in the documentation |
| Types of data | identification and contact details (name, address, e-mail, telephone, signature, stamp), authorisation details, data on properties and their owners, data contained in correspondence, contracts and decisions, the text of questions and conversations |
| Special categories | the service is not intended for them; the controller does not put them into the service |
Annex 2: Technical and organisational measures
We list only measures that we actually operate and can demonstrate.
Separation of customers. Every record belongs to one office and access is verified on the server on every request. The separation of offices is verified by automated tests. Search and artificial intelligence receive only the data of the office they are working for.
Access control. Roles in the office and permissions per project. An outside assistant and the sync agent see only what the user or source they run under sees. Connections of devices and assistants can be revoked at any time; desktop devices that have not connected for 90 days are disconnected automatically.
Credentials. We store passwords only as a hash. We store access tokens of agents and assistants and device connection codes only as a hash. The service’s interface never returns the keys for artificial intelligence providers that you enter.
Transmission. The connection between your device and the service, and between the service and its subcontractors, is encrypted (TLS).
Artificial intelligence. For language models called through OpenRouter, every request carries an instruction that it may be served only by an endpoint with zero data retention and no use for training; a model without such an endpoint does not serve the request. Text recognition from scans (OCR) runs on our server.
Access by our staff. We look into content only for the reasons stated in the terms of service. Viewing the text of conversations from the administration console is logged.
Location. Office data is stored on a server in the Czech Republic that we manage ourselves. We announce a change of location or the engagement of a hosting provider as a change of sub-processor.
Deletion. Automatic removal of deleted items under paragraph 10.3.
Usage measurement. Product analytics never contains the text of pages, documents or questions.
What the service does not do. The service is not a backup of your archive (paragraph 5.5 of the terms of service). We do not guarantee application-level encryption of stored data or geographically separate copies.
Effective from October 1, 2026