Security
Your customers’ words, kept apart.
What protects a workspace’s data today — each point a control in the code, not a policy we intend to write. And, at the end, what we do not claim.
Each workspace is walled off in the database
Isolation is enforced by Postgres itself, not only by the application’s queries.
- Every table that holds a workspace’s data has row-level security switched on and forced, so not even the database owner is exempt.
- Each policy governs reads and writes alike: a request can neither see another workspace’s rows nor write a row in its name.
- Application queries filter by workspace as well — the policy is the safety net, not the only check.
- The API refuses to start under a database role that could bypass these policies, in every environment.
- Isolation test suites, run against a real database, must pass before a change ships.
Secrets are sealed, and logs stay clean
What you hand over to connect your systems is stored so that a database read alone cannot use it.
- API keys for your actions, and WhatsApp, Messenger and Instagram tokens and app secrets, are encrypted at rest with AES-256-GCM in a dedicated table.
- Tokens are checked with Meta server-side and never sent to the browser.
- Public API keys are stored as hashes, carry only the permissions you choose, and can be revoked at any time.
- Logs never contain message bodies, attachments, contact details, tokens or connection strings.
The public widget can only do what you allow
The chat widget is the one part of ikazebot anyone on the internet can reach, so it carries its own limits.
- An agent’s widget can be framed only by the domains you list — none listed, nowhere.
- Each visitor may send 10 messages a minute, with a per-address backstop behind it.
- Visitors are known by a random id in their browser. Their IP addresses are used briefly for rate limits and never stored.
- Signed-in users of your site can be verified with HMAC or a signed JWT, so the agent knows who it is talking to.
- Spam checks run on visitor messages by default; a spam conversation is paused and costs nothing.
Requests we make on your behalf are fenced in
Crawling your website and calling your API mean fetching addresses someone typed in — which is treated as hostile input.
- Private and internal network addresses are refused, after the name is resolved, so a crawl or an action cannot be pointed at our own infrastructure.
- Every redirect is checked again; writes are never redirected.
- Each request has hard caps on time and size.
- Incoming messages from Meta must carry Meta’s signature over the exact bytes received, and repeated deliveries are stored once.
- Webhooks we send you are signed, so your endpoint can reject anything that did not come from us.
You decide how long it is kept
Your customers’ conversations are your data. The controls for it are in the dashboard, not behind a support ticket.
- Choose how long conversations are kept, or keep them until you delete them; a daily job enforces it.
- Workspace owners can export the whole workspace, and anyone can export their own account, at any time.
- An account can be erased immediately — refused only while its owner is the sole owner of a workspace, so nobody else’s data goes with it.
What we do not claim
If your business needs one of these today, ikazebot is not the right fit yet.
- No SOC 2, ISO 27001 or HIPAA certification is held, and we do not sign BAAs.
- Single sign-on, two-factor authentication and audit logs are planned, not built.
- The hosting region is still to be confirmed, so we make no data-residency promise yet.
The privacy controls are on every plan, Free included.
Start free