Data Processing Agreement (DPA)
Agreement under Article 28 of Regulation (EU) 2016/679 (GDPR).
Between the customer organization that has accepted Reaktive's Terms of Use (the Controller) and [Company name], registered office at [address], VAT number [number] (the Processor or Reaktive). This agreement forms part of the Terms of Use and applies to all personal data that the Controller has Reaktive process through the Service.
1. Subject matter, duration, nature and purpose
1.1 Reaktive processes personal data on behalf of the Controller for the sole purpose of providing the Service described in the Terms of Use and in the Guide: storing content and transmitting it to artificial intelligence models to generate replies, running automations and tools, storing and indexing documents, sending emails on behalf of the Controller, support.
1.2 The duration is the same as that of the contract. The details of the processing (categories of data and of data subjects, operations) are in Annex 1.
1.3 The Controller warrants that it has a legal basis for the data it has processed and that it has informed the data subjects; it decides which content to upload, which tools to activate and which accounts to connect.
2. Controller's instructions
2.1 Reaktive processes data only on documented instructions from the Controller. The instructions are: the Terms of Use, this agreement, the settings chosen by the Controller in the Service (active tools, models, limits, approvals) and the actions requested by its users. The instructions also include memory across chats (facts saved only on the user's explicit request, visible only to that user, editable, exportable and deletable, deleted with their account; the Controller's administrators can turn it off) and projects (shared instructions and a Library folder, shareable among the Controller's users without widening read permissions on documents). The instructions also include meeting minutes (transcription of recordings uploaded by users, with the audio deleted within 2 days) and weekly reports (automatic reading, without storage, of the title and first 200 characters of questions to group them by theme; the report contains only themes and counts, is visible to the Controller's administrators and, only as themes and counts, to Reaktive's system administrators for support). Further instructions must be sent in writing to assistenza@reaktive.cloud; Reaktive informs the Controller if, in its opinion, an instruction infringes data protection law.
2.2 Reaktive does not process the data for its own purposes, except those provided for by law or by its Privacy Notice for the data for which it is the controller (account, billing, security, costs without content).
2.3 Reaktive does not use the Controller's data to train models and contractually binds the model providers not to do so either.
3. Confidentiality
The persons authorized by Reaktive are bound by confidentiality. By design of the Service, Reaktive staff do not access the Controller's content (conversations, files, memory, agent instructions): they see only metadata, amounts, statuses and outcomes. Content is accessed only if one of the Controller's users expressly shares it with support, for the period they choose (7 days at most, revocable), and the access is logged.
4. Security
Reaktive implements the technical and organizational measures in Annex 2, keeps them up to date and may improve them without lowering their level. The Controller is responsible for security on its side: credentials, roles and caps assigned to its users, choice of tools and connected accounts, uploaded content.
5. Sub-processors
5.1 The Controller gives general authorization for the sub-processors in Annex 3. Reaktive imposes on them, by contract, obligations equivalent to those of this agreement and remains liable for their performance.
5.2 Reaktive announces any addition or replacement with 30 days' notice on this page and by email to the Owner. The Controller may object on reasonable, documented grounds within the notice period; if no solution is found, it may ask for the organization to be closed, with a refund of the unused credit.
5.3 Sub-processors that the Controller activates on its own initiative, by connecting its own accounts (Google, Telegram) or by choosing a model with a global profile, act under those providers' terms with the Controller; Reaktive transmits to them only the data needed for the requested action.
6. Transfers outside the European Union
Data is stored and processed in the European Union (Ireland). Transfers to third countries take place only to the sub-processors listed in Annex 3, on the basis of an adequacy decision (Article 45 GDPR, including the Data Privacy Framework) or with the safeguards of Article 46 GDPR (standard contractual clauses), or by explicit choice of the Controller in the Settings (models with a global profile), which counts as an instruction.
7. Assistance to the Controller
7.1 Reaktive assists the Controller in responding to data subjects' requests (access, rectification, erasure, portability, objection) with the functions of the Service (deleting conversations and files, deactivating users: on deactivation the user's personal content passes to the colleague the user named in advance or, failing that, is deleted; cost records are kept without content) and, for everything else (for example exporting data or closing the organization), within 10 working days of the written request. If it receives a request from a data subject concerning the Controller's data directly, it forwards it to the Controller without responding, unless otherwise agreed.
7.2 Reaktive assists the Controller, with the information available to it, in complying with Articles 32–36 GDPR (security, breaches, data protection impact assessment, prior consultation).
8. Personal data breaches
Reaktive notifies the Controller, at the Owner's email address, of any personal data breach affecting it without undue delay and in any case within 48 hours of becoming aware of it, with the information available (nature, categories and approximate number of data subjects and records, likely consequences, measures taken or proposed), supplemented as it becomes available. Reaktive cooperates in any notifications to the authority and to data subjects, which remain the Controller's responsibility.
9. Deletion and return
When the organization is closed or upon written request, Reaktive makes the Controller's data available for export in the Service's formats and then deletes conversations, files, memory, indexes, secrets and schedules within 30 days; backups expire at the end of the retention period in Annex 2. Cost records, audit logs and tax documents, without content, are kept to meet legal obligations.
10. Audits
Upon request and no more than once a year, Reaktive provides the Controller with the information needed to demonstrate compliance with this agreement: description of the security measures, results of internal reviews and security tests, reports from infrastructure providers (for example AWS compliance attestations). On-site audits are possible with 30 days' notice, during working hours, at the Controller's expense, limited to what is not already covered by the documentation, and without access to other customers' data.
11. Liability and final provisions
Liability is governed by the Terms of Use, within the limits of Article 82 GDPR. In case of conflict between this agreement and the Terms of Use, this agreement prevails as regards personal data. Italian law and the jurisdiction set out in the Terms of Use apply.
Annex 1 — Details of the processing
| Item | Description |
|---|---|
| Categories of data subjects | the Controller's users (employees, collaborators); people whose data appears in uploaded or generated content (customers, suppliers, contacts, authors of documents, email recipients); people mentioned in the results of web or social media searches |
| Categories of data | identification and contact data; content of conversations, documents, emails, calendars and files; voice and meeting recordings and their transcriptions; professional data; memory-across-chats facts and project instructions; any other data the Controller decides to have processed. Special categories (Art. 9) only if the Controller includes them, under its own responsibility |
| Operations | collection, recording, storage, organization, text extraction, indexing, transmission to models and tools, generation of replies and documents, transcription of recordings, grouping of questions by theme for usage reports, sending emails, erasure |
| Location | European Union (Ireland), with the exceptions in Article 6 and Annex 3 |
| Duration | duration of the contract; deletion according to Article 9 |
Annex 2 — Technical and organizational measures
- Isolation. Every record carries the organization's identifier; row-level security policies in the database prevent cross-access; every transaction is bound to the requester's organization; objects of other organizations appear not to exist.
- Encryption. TLS 1.2 or higher in transit, with HSTS; encryption at rest of the database, storage and backups (AWS KMS); tokens and secrets encrypted with dedicated keys; passwords stored only as a strong hash.
- Access. Authentication with a protected session (
__Host-cookie, no tokens in URLs), blocking after 5 failed attempts, request limits per IP address, checks on the origin of requests, password change at first sign-in for users created by an administrator, session revocation on password change and on deactivation; roles with least privilege; no administrative reading of content. - Data minimization in logs. Technical logs contain no prompts, texts, tool parameters, tokens or secrets; retention 30 days.
- Content and models. No training on customer data; checks against hidden instructions in the content read by tools; human approval for outgoing messages when configured; anti-abuse limits on outgoing messages.
- Application. Security headers (full CSP, nosniff, frame-ancestors, Referrer-Policy), no external images in replies, antivirus scanning of files uploaded to the Library and of support request attachments before use, license checks of dependencies in continuous integration, isolation (IDOR) tests on every route.
- Infrastructure. Private network with controlled egress, web application firewall (AWS WAF), secrets in AWS Secrets Manager, infrastructure defined as code and subject to review.
- Continuity. Automatic backups in the same region with a retention of [35] days, point-in-time recovery, periodic restore tests, monitoring and alarms.
- Organization. Staff bound by confidentiality; multi-factor authentication for access to systems; log of administrative access (audit); incident management procedure with notification to customers (Article 8); periodic security reviews with a report.
Annex 3 — Sub-processors
| Sub-processor | Registered office | Activity | Place of processing | Transfer safeguard |
|---|---|---|---|---|
| Amazon Web Services EMEA SARL | Luxembourg | infrastructure (compute, database, storage, queues, service emails, firewall), running the models with Amazon Bedrock | Ireland (eu-west-1); Claude models in European Union regions; models with a global profile only if activated by the Controller | established in the Union; for the global profile, AWS standard contractual clauses and the Controller's choice |
| Stripe Payments Europe, Limited (once online payment is activated) | Ireland | online payments (payer and transaction data) | Ireland; Stripe may transfer data within the Stripe group with its own safeguards | established in the Union |
| Brave Software, Inc. | United States | web search (only the text of the search), only if the tool is active | United States | Data Privacy Framework, if Brave is certified; otherwise standard contractual clauses |
| Apify Technologies s.r.o. | Czech Republic | social media search (search terms), only if the tool is active | European Union | established in the Union |
| Google Ireland Limited | Ireland | Google services connected by the Controller's users (Gmail, Drive, Docs, Sheets, Slides, Calendar, Tasks, Contacts) | under Google's terms; activated by the Controller | Google's terms with the Controller |
| Telegram Messenger Inc. | [registered office] | Telegram bot, only if activated by the Controller | outside the European Union | the Controller's explicit choice in the Settings (instruction) |
| OpenAI Ireland Limited, with OpenAI, L.L.C. | Ireland; United States | image generation and editing (Design): job description without personal data, reference images without private metadata, images produced; only if the Controller's administrator accepts “Design providers outside the EU” | United States | standard contractual clauses and the Data Privacy Framework, where applicable; the Controller's recorded acceptance |
| Google Cloud EMEA Limited, with Google LLC (Vertex AI) | Ireland; United States | image and video generation (Design and Video), with the same data as the previous row; only if the Controller's administrator accepts “Design providers outside the EU” | global endpoint (Google regions) and us-central1 (United States) | Cloud Data Processing Addendum, standard contractual clauses and the Data Privacy Framework; the Controller's recorded acceptance |
| Apple Inc. and Google LLC (once the app is published) | United States | push notifications and distribution of the mobile app (device identifiers, notification titles without content) | United States | Data Privacy Framework or standard contractual clauses |
The list is updated with the notice set out in Article 5; a summary is also on the Data and security page.