Skip to content
Legal

Privacy policy

What Kairo collects, where it lives, who else sees it, and how to get it removed.

01

Scope

This policy covers the Kairo web application and the research reports it generates. Kairo is maintained by its app owner; this page describes the practices in place today and is updated when they change.

Kairo analyses public blockchain and market data. It never asks for wallet private keys, seed phrases, or signing permissions, and it cannot move funds.

02

Data we collect

  • Account data — email address, display name, and optional avatar URL, created when you sign up.
  • Research data — the contract addresses you submit, the generated report, and the evidence snapshot captured for it.
  • Usage data — report counts and outcome codes used to enforce plan quotas and diagnose failures.
  • Billing data — subscription tier, status, and period end. Card details are handled by the payment provider and never reach Kairo.
  • Referral data — your referral code and the signups attributed to it, if you use the referral programme.
03

How we use it

Data is used to run the product: authenticate you, generate and store your reports, enforce plan limits, process subscriptions, and investigate errors.

We do not sell personal data and we do not use your report history for advertising or profiling.

04

Storage and access

Application data is stored in a managed Postgres database on Lovable Cloud. Every user-owned table uses row-level security scoped to your account, so reports, evidence snapshots, usage records, and referrals are readable only by you and by server-side code acting on your behalf.

Reports are private by default. A report becomes publicly readable by link only after you choose to share it, and shared links expose presentation fields only — never your account identifier.

05

Third-party data providers

To build a report Kairo queries public and commercial data sources from its servers:

  • DexScreener and GeckoTerminal — market, pair, and price history data
  • Helius (Solana) and Etherscan (EVM chains) — on-chain holder, transfer, and contract data
  • The project's own website and public GitHub repositories — narrative and developer evidence
  • An AI model gateway — used to interpret already-collected evidence into readable analysis

These requests carry the token or contract being researched, not your identity. Payments are processed by our payment provider, which receives the billing details you enter on its checkout.

06

Cookies and local storage

Kairo uses browser storage for essentials only: your authenticated session, theme preference, onboarding state, and recently viewed reports. There are no third-party advertising or cross-site tracking cookies.

07

Retention

  • Reports and evidence snapshots are kept until you delete them or delete your account.
  • Usage records are kept for the rolling period needed to enforce monthly quotas and for basic diagnostics.
  • Market snapshots are aggregate, non-personal token data and are retained to power historical charts.
  • Deleting your account removes your profile, reports, evidence snapshots, saved items, and referral records.
08

Your choices and requests

You can edit your profile and delete individual reports from within the app at any time. For access, export, correction, or deletion of everything tied to your account, email the address below from your account email and we will action it.

Depending on where you live you may have additional statutory rights over your personal data.

09

Contact

Privacy and security questions, including suspected vulnerabilities: privacy@kairo.app. Please do not include private keys or credentials in your message.

Changes to this policy

If we change how data is collected or shared, this page is updated and material changes are announced in-app before they take effect.