Security

Updated: 21 November 2026

This page describes how Clarifo keeps customer data apart and protected, and how to report a security vulnerability to us. Firms that need more detail for vendor due diligence can ask us at [email protected].

How we keep customer data apart

  • Your workspaces, documents, notes, chats, portfolios and API keys can be opened only by you, by the people you share them with, and by the members of your Commercial organization for the workspaces you share into it. Our servers check this on every request.
  • Automated tests check that people outside a workspace get nothing back, and that every route that changes workspace content requires write access.
  • Clarifo itself does not train AI models on your questions, documents or workspace content.

Infrastructure and encryption

  • The application, its databases and its search index run on Hetzner servers in the EU (Germany and Finland).
  • Traffic to clarifo.com, api.clarifo.com and mcp.clarifo.com is encrypted with TLS, and browsers are told to use HTTPS only (HSTS).
  • The databases and the search index accept connections only from our own servers.
  • Filings are indexed for search on our own servers.
  • Payment card details are handled by Stripe and are never stored on our servers.

AI providers and sub-processors

To write an answer, Clarifo sends your question, and the documents or workspace content you use as context, to the AI provider that writes it: Anthropic, OpenAI or Google. The full list of sub-processors, and where they process data, is in our Privacy Policy.

API keys

  • A Data API key is shown once, when it is created. We store only a hash of each key.
  • A revoked key stops working at once.

Report a vulnerability

Email [email protected] with:

  • a description of the issue and its impact
  • the steps to reproduce it, or a proof of concept
  • the affected URL, endpoint or component
  • any screenshots, logs or request and response captures

Test only against your own account. Do not access, change or download other users' data, and do not degrade the service for others.

Scope

In scope: clarifo.com and its subdomains (including api.clarifo.com and mcp.clarifo.com), the Clarifo MCP server and the Clarifo mobile app.

Out of scope:

  • third-party services we use but do not operate (please report those to the vendor)
  • denial of service, spam and social engineering of our staff
  • findings that need physical access to a user's device
  • automated scanner output without a demonstrated, exploitable impact

What you can expect

  • We confirm receipt within 3 business days.
  • We send an initial assessment within 10 business days.
  • We keep you updated until the issue is fixed, or explain why we consider it out of scope or cannot reproduce it.

Please give us reasonable time to fix an issue before you disclose it publicly, typically 90 days. We are happy to agree on a disclosure date with you.

Safe harbour

If you act in good faith under this policy, we will not take legal action against you or report your research to law enforcement, and we will work with you to understand and fix the issue. Good faith means no access to accounts that are not yours, no data taken beyond what a proof of concept needs, no disruption of the service, and reporting to us privately before any public disclosure.

Recognition

We do not run a paid bug bounty. With your permission, we thank the reporters of valid issues publicly.

Security documentation for firms

On request we provide a data processing agreement (DPA) and answers to security questionnaires. Email [email protected].