Last updated: November 8, 2026
This Data Processing Agreement ("DPA") forms part of the Terms of Service and any order form or other agreement for the Service (together, the "Agreement") between Claro Historia, Inc., a Delaware corporation ("Claro Historia," "we," "us," or "our"), and the customer that accepted the Agreement for a workspace ("Customer"). It applies whenever we process Customer Personal Data on Customer's behalf.
This DPA takes effect when Customer accepts the Agreement and needs no separate signature. A Customer that needs a countersigned copy for its records can request one at support@clarohistoria.com.
Capitalized terms not defined here have the meanings given in the Agreement.
2.1 Roles. Customer is the controller of Customer Personal Data, or a processor acting for its own controller, and we are Customer's processor, or subprocessor, as the case may be.
2.2 Data we control. This DPA does not cover personal data we process as a controller for our own purposes, such as account registration and sign-in, billing, security and abuse prevention, service communications, and our website. Our Privacy Policy describes that processing.
2.3 Customer's responsibilities. Customer decides which sources to connect and link to its projects, and is responsible for having a lawful basis, giving any required notices, and having the right to make that data available to the Service. Every member of a workspace can open every project, so content synced into a project is visible to all of the workspace's members. The Service is not designed to process special categories of personal data or data about children, and Customer should not link sources that contain them.
3.1 We process Customer Personal Data only on Customer's documented instructions. Customer instructs us to process Customer Personal Data to provide the Service as described in the Agreement and this DPA, as configured and used by Customer and its users (including the sources they connect and link, the AI model each project uses, and whether AI tool access through MCP is turned on), and as otherwise agreed in writing.
3.2 If a law we are subject to requires other processing, we will tell Customer before processing unless that law prohibits it. We will tell Customer if, in our opinion, an instruction infringes Data Protection Laws.
3.3 We do not use Customer Personal Data to train AI models, sell or share it, or use it for advertising. Each AI provider listed in Annex III is used under its commercial API terms, under which this content is not used to train its models.
3.4 When Customer or its users connect a tool or AI assistant of their own choosing, for example through AI tool access (MCP), the data they retrieve goes to that tool's provider at Customer's direction and under the agreement between Customer or the user and that provider. Those providers are not our Subprocessors.
We limit access to Customer Personal Data to personnel who need it to provide, support, or secure the Service, and ensure they are bound by appropriate obligations of confidentiality.
We implement and maintain the technical and organizational measures described in Annex II. We may update these measures over time, provided the updates do not materially decrease the overall protection of Customer Personal Data.
6.1 Authorization. Customer gives general authorization for us to engage Subprocessors. Our current Subprocessors are listed in Annex III and on our Trust page.
6.2 Obligations. We impose on each Subprocessor, by written agreement, data protection obligations that provide at least the same level of protection as this DPA, to the extent applicable to the services it provides. We remain responsible to Customer for our Subprocessors' performance of those obligations.
6.3 New Subprocessors. At least 14 days before a new Subprocessor starts processing Customer Personal Data, we will update the Trust page and email Customer's workspace admins.
6.4 Objections. Customer may object to a new Subprocessor on reasonable data protection grounds by emailing support@clarohistoria.com within 14 days of our notice. We will discuss the objection in good faith. If we cannot resolve it within a reasonable period, Customer may terminate the affected part of the Service by written notice, and we will refund any prepaid fees covering the remainder of the subscription term for the terminated part.
Taking into account the nature of the processing, we will assist Customer by appropriate technical and organizational measures in responding to requests from data subjects to exercise their rights under Data Protection Laws. The Service lets Customer disconnect sources, remove synced content, and delete projects. For anything Customer cannot do itself, Customer can email support@clarohistoria.com. If we receive a request directly from a data subject about Customer Personal Data, we will forward it to Customer without undue delay and will not respond to it ourselves, other than to direct the data subject to Customer, unless the law requires otherwise.
8.1 We will notify Customer without undue delay, and in any event within 72 hours, after becoming aware of a Security Incident.
8.2 Our notice will describe, to the extent known, the nature of the Security Incident, the categories and approximate number of data subjects and records concerned, its likely consequences, the measures we have taken or propose to take, and a contact point. Where we cannot give all of this at once, we will give it in phases without further undue delay.
8.3 We will send notices to the email addresses of Customer's workspace admins. Our notice of, or response to, a Security Incident is not an acknowledgment of fault or liability.
Taking into account the nature of the processing and the information available to us, we will give Customer reasonable assistance with data protection impact assessments and prior consultations with supervisory authorities that Data Protection Laws require of Customer in relation to the Service.
10.1 During the Agreement. Customer can delete Customer Personal Data using the Service. Projects moved to the trash are permanently deleted after 30 days. Content synced from Jira or Confluence is removed 30 days after the source is disconnected unless it is reconnected first, or immediately if Customer chooses. For other sources, we delete synced content on request.
10.2 After the Agreement. Within 30 days after the Agreement ends, or after Customer asks us in writing to close its workspace and delete its data, we will delete Customer Personal Data. Before deletion, Customer may ask us for a copy of its content in a commonly used, machine-readable format.
10.3 Backups and logs. Copies in backups expire within 14 days, and application logs within 30 days. Until they expire, they remain protected under this DPA and are not used for any other purpose.
10.4 Legal retention. We may keep Customer Personal Data where the law requires us to, only for as long as required, and it remains protected under this DPA. We will certify deletion in writing on request.
11.1 Information. On request, we will make available the information reasonably necessary to demonstrate our compliance with this DPA, including answers to Customer's security questionnaire, our written security policies, and the reports or certifications of our Subprocessors where those Subprocessors allow us to share them.
11.2 Audits. If that information is not sufficient to demonstrate compliance, or a supervisory authority or Data Protection Laws (including the SCCs) require it, Customer or an independent auditor it appoints may audit our compliance with this DPA. Audits are limited to once in any 12 month period, except after a Security Incident or at a supervisory authority's request. Customer must give at least 30 days' written notice and agree the scope with us in advance. The auditor must be bound by confidentiality, and audits take place during business hours without disrupting the Service or giving access to other customers' data. Customer bears its own costs. We prefer audits by document review and remote meetings where they meet the purpose.
12.1 Location. We host the Service in the United States (Amazon Web Services, us-east-1). Subprocessors may process Customer Personal Data in other countries, as described in their own terms.
12.2 EEA. To the extent that providing the Service involves a transfer of Customer Personal Data from the European Economic Area to us in a country without an adequacy decision, the SCCs are incorporated into this DPA and apply as follows:
12.3 United Kingdom. To the extent the UK GDPR applies to a transfer, the SCCs apply as set out in section 12.2 together with the UK Addendum, which is incorporated into this DPA. In the UK Addendum, Table 1 is completed by Annex I, Table 2 by section 12.2, and Table 3 by Annexes I to III, and for Table 4 either party may end the UK Addendum as set out in its Section 19.
12.4 Switzerland. To the extent the FADP applies to a transfer, the SCCs apply as set out in section 12.2 with these changes: the Swiss Federal Data Protection and Information Commissioner is the competent supervisory authority for transfers governed by the FADP; references to the GDPR are read as references to the FADP; and the term "Member State" does not prevent data subjects in Switzerland from bringing claims where they habitually reside.
12.5 Onward transfers. Where a Subprocessor receives Customer Personal Data outside the EEA, the UK, or Switzerland, we rely on a transfer mechanism recognized under Data Protection Laws, such as the Standard Contractual Clauses in that Subprocessor's data processing terms.
12.6 Changes. If a transfer mechanism we rely on is invalidated or replaced, we will work with Customer in good faith to put an appropriate alternative in place. If the SCCs or UK Addendum conflict with this DPA or the Agreement, the SCCs or UK Addendum prevail.
To the extent the CCPA or a similar US state privacy law applies, we act as Customer's service provider or processor. We will not sell or share Customer Personal Data; retain, use, or disclose it for any purpose other than the business purposes specified in the Agreement, or outside our direct business relationship with Customer; or combine it with personal information we receive from others, except as those laws permit. We will comply with those laws, provide the same level of privacy protection they require, and tell Customer if we can no longer meet our obligations under them. Customer may take reasonable and appropriate steps to stop and remediate any unauthorized use of Customer Personal Data. We certify that we understand and will comply with these restrictions.
14.1 Liability. Each party's liability arising out of or relating to this DPA is subject to the limitations of liability in the Agreement, except where Data Protection Laws or the SCCs do not permit those limitations, including with respect to data subjects' rights under the SCCs.
14.2 Order of precedence. If there is a conflict concerning the processing of Customer Personal Data, the SCCs and UK Addendum prevail over this DPA, and this DPA prevails over the rest of the Agreement.
14.3 Term. This DPA lasts for as long as we process Customer Personal Data.
14.4 Changes. We may update this DPA to reflect changes in Data Protection Laws, our Subprocessors, or the Service by posting a new version on this page. An update will not materially reduce the protection of Customer Personal Data during Customer's current subscription term without Customer's agreement.
14.5 Governing law. This DPA is governed by the law that governs the Agreement, except where the SCCs or Data Protection Laws require otherwise.
14.6 Contact. Questions about this DPA: support@clarohistoria.com. Security matters: security@clarohistoria.com.
Data exporter: Customer, as identified in its workspace account. Contact: the workspace admins on the account. Activities: use of the Service under the Agreement. Role: controller, or processor on behalf of its own controller. Signature and date: by accepting the Agreement.
Data importer: Claro Historia, Inc., 2810 N Church St STE 90502, Wilmington, DE 19802. Contact: support@clarohistoria.com. Activities: providing the Service under the Agreement. Role: processor, or subprocessor. Signature and date: by providing the Service under the Agreement.
Categories of data subjects: Customer's users of the Service (workspace admins and members), and people whose personal data appears in the content Customer links from connected sources, such as Customer's employees, contractors, clients, and partners named as assignees, authors, reviewers, commenters, attendees, or senders.
Categories of personal data:
Sensitive data: None intended. See section 2.3. The measures in Annex II apply to all Customer Personal Data.
Frequency of transfer: Continuous, for the duration of the Agreement.
Nature of the processing: Collecting content from the sources Customer links; storing, indexing, organizing, and analyzing it, including with AI models; sending users' questions and the relevant content to the AI model provider the project uses; retrieving and displaying results to authorized users; and deleting it.
Purpose: To provide, support, and secure the Service under the Agreement.
Retention: For the duration of the Agreement, then deleted as described in section 10.
Transfers to Subprocessors: As described in Annex III, for the purposes listed there and for the duration of the Agreement.
As determined under Clause 13 of the SCCs, or as set out in sections 12.3 and 12.4 for the UK and Switzerland.
We host the Service in the United States (Amazon Web Services, us-east-1). The providers of the tools Customer chooses to connect are listed because the Service exchanges data with them on Customer's behalf; they are involved only when Customer connects them. The current list is also on our Trust page.
| Provider | What it does | Data involved | When |
|---|---|---|---|
| Amazon Web Services | Hosting, database, file storage, backups and encryption keys | All customer data, encrypted | Always |
| Anthropic | Claude AI models that answer questions and read documents when they sync | Your questions and the project content relevant to them | When you use the chat or document syncing in a project that uses a Claude model (the default) |
| OpenAI | GPT AI models that answer questions and read documents when they sync | Your questions and the project content relevant to them | Only for projects set to use a GPT model |
| Google (Gemini) | Gemini AI models that answer questions and read documents when they sync | Your questions and the project content relevant to them | Only for projects set to use a Gemini model |
| Postmark | Sends email: invitations, password resets, trial notices | Recipient email address and name, workspace name | Always |
| Sign in with Google; Google Drive, Gmail and Calendar | Sign-in email; content you link or let the AI use | Only if you use Google sign-in or connect a Google account | |
| Microsoft | Sign in with Microsoft; OneDrive, Outlook and Teams | Sign-in email; content you link or let the AI use; Teams channel messages are summarized, not stored | Only if you use Microsoft sign-in or connect a Microsoft account or Teams |
| GitHub | Source code hosting | Pull requests, issues and commits you link | Only if you connect GitHub |
| Atlassian | Jira, Confluence and Bitbucket | Issues, pages and pull requests you link | Only if you connect an Atlassian tool |
| Slack | Team messaging | Messages in channels you link (summarized; new messages held encrypted for up to a day until then); your own direct messages if you opt in | Only if you connect Slack |
| Linear | Project management | Cycles, projects and issues you link | Only if you connect Linear |
| GitLab | Source code hosting | Issues, merge requests and milestones you link | Only if you connect GitLab |
| Notion | Notes and wikis | Pages and databases you share | Only if you connect Notion |