Data Processing Agreement
This Data Processing Agreement ("DPA") is part of the Terms of Service between the customer (the "controller") and Webdock.io ApS, CVR 40630015, Tværvejen 9A, 5580 Nørre Aaby, Denmark (the "processor"), and applies whenever we process personal data on your behalf inside your DockBots team box. It is accepted with the Terms; you do not need to sign a separate copy. If you need a countersigned PDF for your records, write to hello@dockbots.io.
1. Subject, nature and purpose
We host and operate a dedicated server (the team box) on which AI bots work on your instructions: reading and writing your Brain and CRM, drafting and, after your approval, sending messages, and reading from and writing to the tools you connect. The purpose is to provide the DockBots service as described in the Terms. The processing lasts for the term of the agreement.
2. Categories of data and data subjects
The data you and your bots put into the team box. Typically: contact and business data about your customers, prospects, suppliers and partners; the names, emails and messages of your own team members; the content of emails, documents, spreadsheets and CRM records your bots work with. Data subjects are your team members and the people in your business relationships. You decide what goes in; special categories of data should not be processed unless you have a legal basis and tell us in advance.
3. Our obligations
We will:
- process personal data only on your documented instructions, which are the Terms, this DPA, the settings you choose in the console and the instructions you give the bots, unless EU or Danish law requires otherwise, in which case we tell you before processing unless the law forbids it;
- ensure that persons we authorise to process the data are bound by confidentiality;
- implement the technical and organisational measures in Annex 1;
- engage subprocessors only under section 5;
- help you, taking the nature of the processing into account, to answer requests from data subjects, and help you with security, breach notification, impact assessments and prior consultation under Articles 32 to 36;
- at the end of the service, delete the personal data and existing copies as set out in Data deletion, unless EU or Danish law requires storage;
- make available the information needed to demonstrate compliance, and allow and contribute to audits, including inspections, conducted by you or an auditor you mandate, at reasonable notice and no more than once a year unless a supervisory authority or a breach requires more.
4. Personal data breach
We notify you without undue delay, and at the latest within 48 hours, after becoming aware of a personal data breach affecting your team box, with the information Article 33(3) requires as far as we have it, and we keep you informed as we learn more.
5. Subprocessors
You give general authorisation for the subprocessors listed in Subprocessors. We inform you of intended additions or replacements by email or in the console at least 30 days before they take effect, so that you can object. If you object on reasonable grounds and we cannot offer an alternative, you may terminate the affected part of the service without penalty. We impose the same data protection obligations on each subprocessor and remain fully liable to you for their performance.
6. Transfers
Personal data is stored in Denmark. Where a subprocessor processes data outside the EU/EEA, we rely on an adequacy decision or the EU Standard Contractual Clauses, as noted in the subprocessor list, and we assess the transfer.
7. Your obligations
You are responsible for the lawfulness of the processing you instruct, including having a legal basis for the data you load into the team box and the messages you let the bots send, for answering data subject requests, and for the settings you choose in the console, in particular which actions require approval.
8. Liability and term
Liability under this DPA follows the Terms. The DPA applies as long as we process personal data for you, and the confidentiality obligations survive it.
Annex 1: technical and organisational measures
- One dedicated server per customer, in our own datacenter in Denmark, with no shared tenancy of customer data.
- Encrypted transport (TLS) for the console, the API, the model gateway and all connector traffic; disk encryption at rest on the hosting platform.
- Credentials for connected tools stored only on the customer's own server; the control plane brokers sign-ins and does not retain tokens.
- Sign-in with password and optional two-step verification; role-based access (admin, operator, restricted) inside the console; session expiry.
- Human approval before a bot sends or changes anything outside the server, by default.
- Daily snapshots of each team box, restricted to recovery; purged within 30 days after deletion.
- Access by our staff only for support, fault fixing or legal obligation, logged in the customer's event log.
- Separation of the control plane (provisioning, billing, model gateway) from customer servers; secrets on the control plane kept outside the code and never on customer servers.
- Vendor contracts with our subprocessors, including no training on customer data by AI model providers.
Annex 2: subprocessors
The current list, with locations and transfer mechanisms, is published at dockbots.io/legal/subprocessors. The identity of the AI model providers used under the plan, their locations and the transfer mechanism are provided on request at hello@dockbots.io and form part of this annex.