Skip to main content
This page is the overview. It links to the pages that hold the mechanics: Privacy & data ownership, Data subject requests, Exports, Account ownership.
Kair does not measure how much data a workspace holds, so this page describes what is kept and for how long, not volumes. Audio is by far the largest item.

Where personal data goes and where it is cleaned

Red holds identifiable material (the audio itself). Green has been through redaction. Redaction is automatic, not perfect, and uploaded documents are not redacted. See the warning on Privacy.

What we keep and what we never keep

Short-lived data


Personal versus organisation level

Every workspace belongs to an organisation, and the organisation’s kind decides who controls its data. A member who leaves a workspace does not take their contributions with them. Their only route is a data request, and for a single remark in someone else’s organisation, asking that organisation’s admin. Leaving or being removed clears their ownership of sessions in that workspace (sessions.owner_user_id), so they lose access; the session keeps former_owner_user_id, which erasure and export still treat as theirs.

What an erasure does to each kind of data

The neo4j topic graph is re-projected after topic history is cleaned, so it holds no erased session. The step-by-step table, including checkpointing and retries, is in Data subject requests.

Exports by level

All four need a sign-in from the last 10 minutes, and API keys or OAuth/MCP tokens are refused. Full column-by-column detail: Exports.

Accountability trail