Legal · Security & data
Security & data
How your brand brain is stored, isolated, and protected — in plain language, with nothing hidden.
Last updated · 2026-10-13
1 · Isolated by design
Every workspace on kbie is separated at the database level using Postgres Row-Level Security (RLS). One customer’s brand brain is never visible to another — the isolation is enforced by the database itself, not just by application code.
2 · Encrypted, always
Your data is encrypted in transit (TLS) and at rest. Every connection to kbie runs over HTTPS, end to end.
3 · Where your data lives
Today, your brand brain is stored in India (Mumbai): data at rest in India; model inference by a provider under a data-processing agreement.
4 · You stay in control
- You own your data. You can export your brand brain and delete it at any time.
- Nothing learns silently.Your brain only learns what you approve — kbie surfaces each proposed learning with its evidence, and it enters your brand’s truth only when you accept it.
5 · We never train AI models on your data
Your brand brain is stored only with kbie. We never use your brand data to train a shared or third-party AI model. To generate your content, the relevant context is sent to your chosen model’s API solely to produce your output — never to train it. The major model providers’ API terms state the same: data sent through their API isn’t used to train their models. kbie’s learnings are rules reviewed by people, not model weights; nothing moves between customers.
6 · Model-agnostic by design
Your verified brand truth lives in your brand brain — a store you own — never locked inside a single AI model. kbie already works across multiple engines: your brand is audited across ChatGPT, Claude and Gemini. Broader engine choice and bring-your-own-model are on our roadmap.
7 · Built on trusted infrastructure
kbie runs on Supabase (database), Vercel (application), and Cloudflare (delivery and storage) — established providers with their own enterprise-grade security programs. Our current sub-processors are listed in our Data Processing Agreement, available on request.
8 · Working toward more
We’re actively pursuing formal security certification (SOC 2) and will publish our progress here. We’d rather tell you exactly where we stand today than imply a badge we haven’t earned yet.
9 · Report a security issue
Found a vulnerability? Email security@kbie.ai. We welcome responsible disclosure and will respond quickly.