Legal

Privacy Policy

Effective date: October 3, 2026

Overview

Klarun is a B2B platform that data teams use to run their data organization: reports, data assets, platform, people, projects and cost. This Privacy Policy explains what information we collect, why, how we use it, and the choices you have.

We do not sell personal data. We do not use it for advertising.

Our Role

For the accounts of the people who use Klarun, and for billing, we are the controller. For the data a customer enters in its workspace or brings in through an integration, the customer is the controller and Klarun is the processor: we process that data only to provide the service, on the customer's instructions. Requests about that data are best sent to the customer; we help it answer them.

Information We Collect

Account information. When you sign in with Microsoft, we receive your name, email address and, if available, your profile picture. We use them to identify your account and to connect it to your organization's workspace.

Workspace data. What your team enters in Klarun: reports, data contracts, architecture entries, incidents, team members and their skills, objectives and initiatives, budgets, costs and payroll. It belongs to your organization.

Integration data. When your organization connects Fabric / Power BI, Databricks or Microsoft 365 Copilot, Klarun copies metadata and usage from them. This includes personal data about your organization's people:

  • workspace users, with their email addresses and roles;
  • the Power BI activity log: who viewed or changed which item, and when;
  • Databricks audit records, which carry the email of the user who acted;
  • Microsoft 365 Copilot license holders, if your organization lets Klarun read its users in Microsoft Graph: user principal name, display name, the license held and when it was assigned or released. These names are stored whatever your tenant's name-concealment setting;
  • Microsoft 365 Copilot usage per person (last activity and use per app), with user principal name and display name, unless your tenant conceals names in Microsoft's usage reports, in which case Microsoft sends a hashed identifier instead.

Klarun never copies the business rows in your data or the results of your queries.

Audit and security records. We record sign-ins, sign-outs and failed sign-ins, and security-relevant administrative changes, such as changes to roles, data access scopes and members, revoked sessions, integrations connected, disconnected or synced, data contract changes, Copilot user exports and links between People records and accounts. Each record carries the time and, where available, the user, the organization, the IP address and the browser's user agent; sign-ins, and the linking of an account to a People record, also carry the email address. Admins of your organization who can manage Settings can download up to the 1,000 most recent events as CSV. Separately, server request logs, which include IP addresses, are kept in Azure Monitor for 30 days for security and troubleshooting.

Billing information. When your organization buys a plan directly from Klarun, card payments are handled by Stripe; when it buys through Microsoft Marketplace, Microsoft handles the purchase and the billing. We store your plan, the state of your subscription and the provider's customer or subscription reference, never card numbers.

Business View counts. We count, per company and week, how many reports were opened and how many searches were made in the Business View. No reader, identifier or search word is kept with those counts.

Cookies. We use only strictly necessary cookies: a session cookie that keeps you signed in, cookies that secure sign-in with Microsoft (CSRF protection, the page to return to after sign-in, and OAuth verification), and a cookie that remembers your language. We use no advertising or analytics cookies.

How We Use It

  • to provide the service: sign-in, your workspace, syncing your integrations and showing their data;
  • to keep the service secure: access control, the audit log, and investigating misuse;
  • to bill paid plans, and to send the only emails Klarun sends: a request to join your organization (to the admins who can approve it), the approval (to the person who asked), domain verification codes, and sync health alerts to our own operations team. Invitations are not sent by email;
  • to run the AI features of your organization's plan, described below;
  • to understand, in aggregate, how the product is used, so we can improve it.

AI Processing

On the Corporate and Enterprise plans, these features send content to Microsoft Foundry, the AI service in Klarun's Microsoft Azure account:

  • 360 Assessment. It is generated automatically once a month for every company on these plans, whether or not anyone opens it; there is no setting to turn it off. It sends the organization's profile, governance metrics, data contracts, open incidents with their descriptions and root causes, architecture entries, the names of Databricks jobs and pipelines that failed, objectives, key results and initiatives, FinOps budget and spend totals (payroll included only as monthly totals), and each active team member by name, with role, seniority, squad, contract type, skills with their levels, and domains.
  • FinOps imports. When someone uploads an invoice or a payroll document, the file is sent, including the salaries it contains.
  • FinOps AI assistant. When someone uses it on the Actual Cost or Budget & Plan pages, it sends the text they type or paste, with the current monthly values of the rows being edited; for payroll, these are each team member's current monthly amounts.

The models run in Microsoft Foundry, in the United States. Microsoft processes this content as our subprocessor and does not use it to train models; OpenAI does not receive it. Content that Microsoft's abuse monitoring flags may be kept for human review, in the same geography.

Legal Bases

We process account and billing data to perform our contract with your organization, and billing records also to meet legal obligations. We process audit and security records and aggregate usage under our legitimate interest in keeping the service secure and improving it (LGPD Art. 7, IX and Art. 10; GDPR Art. 6(1)(b), (c) and (f)). Workspace and integration data are processed on the customer's instructions, under the legal basis the customer relies on as controller.

Where Data Is Stored

Klarun runs on Microsoft Azure, in the Central US region in the United States, and backups are copied to the East US 2 region. Our subprocessors may also process data in the United States and other countries. When personal data leaves Brazil, we apply the safeguards the LGPD requires for international transfers.

Data Retention

  • Account data: for the life of the account; deleted within 30 days of a verified deletion request.
  • Workspace data: until your organization deletes it or asks us to delete it after the contract ends.
  • Integration data: while your organization uses Klarun, including after an integration is disconnected, so its history stays available. Copilot usage per person is deleted automatically after 90 days, and Copilot seat history after 24 months. Your organization can ask us to delete it at any time.
  • Audit and security records: 12 months.
  • Server request logs: 30 days.
  • Access requests and rate-limit records: requests to join an organization (with the requester's name and email) and rate-limit records (some keyed by IP address) are kept until deleted on request.
  • Billing records: for as long as tax and accounting law requires.

Your Rights

Under the LGPD (Art. 18) you can ask us to:

  • confirm whether we process your personal data, and give you access to it;
  • correct incomplete, inaccurate or outdated data;
  • anonymize, block or delete data that is unnecessary, excessive or processed unlawfully;
  • port your data to another provider;
  • delete data processed with your consent, and tell you what happens if you do not consent;
  • tell you which organizations we share your data with;
  • withdraw consent, and object to processing based on legitimate interest.

Write to legal@klarun.app. We answer within 15 days. If your data sits in a customer's workspace or integration, we pass the request to that customer and help it answer.

Subprocessors

We use these providers to run Klarun:

ProviderPurposeLocation
Microsoft Azurehosting, database, file storage, task queue, encryption keys (Key Vault) and server logs (Azure Monitor)United States (Central US); backups copied to East US 2
Microsoft Entra IDsign-inUnited States and other countries where the provider operates
Microsoft 365 (Exchange Online)transactional emailUnited States and other countries where the provider operates
Microsoft Foundrythe AI features described aboveUnited States
Stripecard payments for plans bought directly from KlarunUnited States and other countries where the provider operates
Microsoft Marketplacepurchases and billing of plans bought through MicrosoftUnited States and other countries where the provider operates

Microsoft Power BI and Fabric, Microsoft Graph and Databricks are your organization's own providers: Klarun reads from them with the credentials your organization gives it. We will tell your organization's admins before a new subprocessor starts processing personal data.

Security

Data is encrypted in transit and at rest. The integration credentials Klarun stores are encrypted with a key held in an Azure Key Vault hardware security module. Inside your workspace, access follows roles and data access scopes, and security-relevant administrative changes are written to the audit log.

Changes to This Policy

We may update this Privacy Policy. When we do, we change the effective date above, and for material changes we tell account holders by email.

Contact

Questions about this Privacy Policy or your data, including for our data protection officer: legal@klarun.app.