> For the complete documentation index, see [llms.txt](https://docs.kula.digital/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kula.digital/get-started/trust.md).

# Is my data safe?

Short answer: **yes, and you stay in control.** Here's the plain-English version. The full detail is in [Security & data handling](/trust-and-legal/security.md) and our [Privacy policy](/trust-and-legal/privacy.md).

## Your data is yours alone

Every studio gets its **own private database**. Your numbers are never mixed with another studio's. There is no way for the AI to answer one studio's question using another studio's data — they aren't even stored in the same place. This isn't a setting you have to switch on; it's how the whole thing is built.

## It reads, it doesn't spend

Kula Intelligence reads from the tools you connect so it can answer questions. It will happily draft a win-back email for you — but **you** send it. It never moves money, never charges a card, never posts to your socials, and never messages your members on its own.

## You decide how much it can see

Every connector you create is set to a **permission level**. The everyday default keeps member emails, phone numbers, and payment details hidden — the AI sees enough to help, not more. You only create a higher-level connector for a specific job that needs it. See [Permission levels](/connect-claude-and-access/scopes.md).

## You can see what happened, and stop it anytime

* Every connection shows you what was read and when.
* You can disconnect a data source or revoke your AI assistant's access with one click. Access stops within about a minute.
* Privileged actions are recorded, so there's always a trail.

## Where your data lives

Your studio's data is stored in the cloud region you're set up in (Australian studios stay in Australia). We use trusted infrastructure providers (for databases, hosting, and sign-in) and never sell your data. The full list of providers and how long we keep things is in the [Privacy policy](/trust-and-legal/privacy.md).

## Have a tougher question?

If you (or your accountant, or a security-minded client) want the technical detail — encryption, isolation, how access is revoked, what we deliberately *don't* do — it's all in [Security & data handling](/trust-and-legal/security.md). Found a security issue? See [Responsible disclosure](/trust-and-legal/disclosure.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.kula.digital/get-started/trust.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.