Hosted in the UK and EU
Kuuba is hosted in UK and EU data centres.
Security
Security, stated plainly
What is built into Kuuba, and what we are still confirming. If you need a detail that is not here, contact sales.
In place
How Kuuba is built
Each firm kept separate
Every dashboard request is limited to the signed-in person's own firm. Knowledge, conversations and enquiries are stored against that firm.
Signed-in access
The dashboard needs an account, and each sign-in session expires after 30 days.
Passwords protected
Passwords are stored as salted hashes, never as plain text.
Publishing kept to the right people
Only the people you allow can approve or publish knowledge.
A narrow website snippet
The key in your snippet can only send visitor questions and enquiries. It does not open your dashboard or your records.
A clear record
Each reply is stored with the published version behind it, and each entry records who changed it and when.
Permission first
A visitor's name and contact details reach your team only after they agree.
Only what is needed
A handover asks for a name and one way to reply.
AI disclosure
Every conversation opens by telling visitors they are talking to your firm's AI assistant.
Contact sales
Still being confirmed
Contact sales for the current position on any of these.
Third-party processorsBeing confirmed
Encryption in transit and at restBeing confirmed
Retention periods, and deletion on requestBeing confirmed
A data processing agreement for firmsBeing confirmed
Backups and recoveryBeing confirmed
Privacy
Designed to collect less
Kuuba is built around data minimisation and clear visitor disclosure. A handover asks only for a name and one way to reply. As the firm using Kuuba on your website, you decide what your own privacy notice tells visitors about enquiries.
Reporting
Found a security issue?
Tell us through the contact form and choose “A security concern”.
Contact salesNeed more for your own checks?
Tell us what your firm needs to see, and we will tell you where things stand.