Is my data safe?

The short, plain-English version of how we protect your studio's data — and where to read the detail.

Short answer: yes, and you stay in control. Here's the plain-English version. The full detail is in Security & data handling and our Privacy policy.

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.

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.

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. Found a security issue? See Responsible disclosure.