Data Processing Addendum
Version 1.3 · effective November 21, 2026
This addendum forms part of the Human Reviewed Terms of Service and governs the processing of personal data that CLEARDAYLABS S.A.S. (the "processor") carries out on behalf of the client (the "controller"), under article 34 of Ecuador's Organic Law on Personal Data Protection (LOPDP). It applies when a service involves access to the client's users' personal data, in particular monitoring real conversations of chatbots and agents, and reviews in which the client's database exposes personal data.
1. Subject matter, duration and purpose
- Subject matter: reviewing the security and behavior of the client's app or agent, as contracted.
- Duration: for as long as the contracted service lasts, plus the deletion periods in section 8.
- Sole purpose: providing that service. The processor does not use the data for any other purpose, its own or anyone else's.
2. Categories of data and data subjects
- Data subjects: the controller's users and end customers.
- Data that may appear: identification and contact details (name, email, phone), the content of conversations with the bot and data those users have shared, including, unintentionally, sensitive data.
- The processor does not seek sensitive data; if it appears, it is handled with the same restrictions and is not extracted.
- Masking names, emails and phone numbers does not by itself make a conversation anonymous: it may still allow a person to be identified from context. Pseudonymized conversations are therefore still treated as personal data, with all the safeguards of this addendum.
3. Controller's instructions
- The processor processes data only on the controller's documented instructions: these terms, the signed authorization and anything the controller states in writing.
- If an instruction appears to breach the law, the processor says so before following it.
- Conversation monitoring: whenever possible, the controller provides anonymized or pseudonymized conversations. If it provides identifiable data, it represents that it has a valid legal basis to allow access and that it has informed its users as required by the LOPDP.
4. Confidentiality
Only the people named in the client's authorization access the data, under confidentiality obligations. Data is not disclosed to third parties unless required by law.
5. Security measures
- Access credentials stored separately from other information, on protected devices with authentication.
- Users' data is not copied into reports: we record that an issue exists, not its content. In Monitoring, report examples are shown with personal data masked.
- Minimum necessary access, and only during the authorized period.
6. Sub-processors
The controller authorizes the use of these sub-processors, which process data only to provide their service to the processor. The processor imposes on them data protection obligations equivalent to those in this addendum, through their contractual terms, and is liable to the controller for their compliance.
| Sub-processor | Specific service | What data of the controller's users it receives | Applicable terms |
|---|---|---|---|
| Anthropic | Claude, used through Claude Code and the Claude app | Code and configuration excerpts; Monitoring conversations with direct identifiers masked; record counts and column names | Anthropic's commercial terms or an account setting that excludes use of content to train its models |
| Gmail (Google Workspace or Google account) | Only reports, with examples masked; never conversation exports | Google's privacy terms applicable to the account |
- What they do not receive: no sub-processor receives full exports of the controller's database, real users' passwords or conversations without direct identifiers masked.
- How conversations arrive: through a download link or read-only access controlled by the controller, never as email attachments. If they arrive by email by mistake, they are downloaded to the work device and the email is deleted.
- Providers with no access to the controller's users' data: Cloudflare (website, email forwarding and recording acceptance of the terms), Namecheap (domain registration), PayPal (payments) and the AI assistants queried in the visibility service (OpenAI, Google, Anthropic and Perplexity), which only receive questions about the business, with no personal data.
- Artificial intelligence: AI tools are used as support and do not replace professional validation. Controller data is not used to train the processor's own models.
- Changes: the processor will notify the controller at least 15 days in advance before adding or replacing a sub-processor that processes its users' data; the controller may object and, failing agreement, terminate the service with a refund for the period not provided. If a sub-processor changes its terms in a way that reduces data protection, the processor stops sending it the controller's data and notifies the controller.
- Location: these sub-processors process data mainly in the United States. They act within a processing arrangement subject to this addendum and to article 34 of the LOPDP; the mere fact that a processor is abroad does not turn the arrangement into an international transfer to a third party.
7. Security incidents
If the processor detects an incident affecting the controller's personal data, it notifies the controller without undue delay and within 48 hours at the latest, with the information available, and helps the controller meet its own notification obligations.
8. Deletion and return of data
- Real conversations from Monitoring: deleted within 30 days after the report for the month in which they were reviewed is delivered.
- Credentials, tokens and access: deleted when no longer operationally needed and at most 30 days after the report is delivered or the subscription ends.
- Backups that might contain that data expire within 60 days at most.
- At the controller's request, the processor deletes the data earlier or returns it.
- Every deletion is documented (what was deleted, when and by whom) and the processor gives the controller a written certificate when the service closes.
9. Processor's liability
The controller remains the controller of the processing towards its users. The processor has its own obligations as processor (following instructions, confidentiality, security, incident notification, oversight of sub-processors, assistance and deletion) and is liable for breaching them towards the controller, data subjects and the authority, as provided by the LOPDP. The liability limits in the Terms of Service do not apply to breaches of this addendum.
10. Assistance to the controller
The processor helps the controller respond to requests from its data subjects (access, rectification, deletion, objection and other rights) and forwards to the controller, without answering them itself, any it receives directly.
11. Verification
The controller may request reasonable information showing compliance with this addendum, with 10 business days' notice and without access to other clients' data.
The Spanish version of this addendum prevails in case of discrepancy.
AI-assisted, human-verified: every finding is reproduced and signed off by a person who stands behind it. AI is a support tool and does not replace professional validation.