Security

Security and data protection

How KitoDesk keeps each customer's information separate, who can see what, and what is recorded. These are controls in the product today, described plainly.

Each organisation is isolated

Customer data is separated at the database level with row-level security, so a workspace can only read its own records. Isolation does not rely on application code alone.

Access follows roles and scopes

Permissions are set per role with own, team and organisation scopes, and people can be limited to specific branches. The server checks every request, not just the screen you see.

Strong sign-in controls

Workspaces can require multi-factor sign-in, set session lengths and restrict invitations by email domain. Suspending or removing someone ends their sessions immediately.

Credentials are encrypted

Provider keys and channel secrets are encrypted at rest with AES-256-GCM and are never shown back in full.

Sensitive changes are logged

Changes to people, roles, access, ownership and AI actions are written to an audit log with who did it and when.

AI works inside your rules

Answers cite their sources. Low-risk actions run on their own and sensitive ones wait for an approver. Each workspace has its own usage allowance and AI activity is tenant-isolated.

Keeping private things private

Public website, private workspaces.

The marketing site is the only part of KitoDesk that search engines are asked to index. The application, API, administration console, development environment and every customer workspace require sign-in and are excluded from search results.

What we have not claimed

KitoDesk does not currently advertise third-party security certifications. Questions about hosting location, data retention, backups and your own regulatory obligations are best answered in a conversation, so get in touch and we will answer them directly.

Enough reading, see it live

Show us how your team works. We will build the walkthrough around it.

Tell us your channels, your volumes and who answers what. The demo uses your own situation, not a scripted one.

  • Built around your own workflow
  • Security and rollout questions answered
  • No obligation
app.kitodesk.com / Inbox
Inbox24 open
MineUnassignedAll
MW
Mercy Wanjiru2m
Order 4821 not delivered
WhatsApp
JO
John Otieno9m
Cannot log in to my account
Email
GA
Grace Achieng21m
Thank you for the quick help
Chat
PM
Peter Mwangi1h
Do you open on Sundays?
SMS
FK
Faith Kamau2h
Missed call, returned
Voice
Mercy WanjiruWhatsApp · Support team · Open
SLA 2h 10m
Hi, my order 4821 was meant to arrive yesterday. Where is it?
Hello Mercy, I have your order open. Checking with the courier now.
Private note · Grace W.: courier confirmed, redelivery set for tomorrow
Kito AI suggested reply

Your order 4821 is out for delivery today before 5pm. I have sent the tracking link to your phone. Anything else I can help with?

UseGrace
Your order 4821 is out for delivery today before 5pm. I have sent the tracking link to your phone. Anything else I can help with?Delivered
Write a reply or type / for macrosSend
Kito Cases / CS-1042
CS-1042 · BillingRefund not received
High
NewIn progressPending customerResolved
Resolution due in3h 12m
68% of SLA used
AssigneePO Peter Otieno
CategoryBilling
SourceWhatsApp
Time logged0h 42m
Timeline
Case created from conversation10:02
Assigned to Billing team10:04
Note: refund under review10:31
SLA at 80% warning sent12:40
Billing teamKito AI