Privacy policy
How Kamba Risk handles personal data, what we keep, for how long, and what you can ask us to do with it.
Effective 26 October 2026
Kamba Risk is supplied to businesses, not to consumers. The organisation that holds the account, usually your employer, decides who may use it. In data protection terms it is the controller for the risk data held in the system and Kamba Risk Limited is the processor acting on their instructions. For the account and security data described below, we are the controller.
1. What we collect
Data you give us
- Authentication data. Email address and a password, which is hashed and never stored in readable form.
- Profile data. Name and the organisation you belong to.
- Communication data. Correspondence about account activity and security.
- Billing data. For plans paid by card, the billing contact’s name, email address and billing address. Card details are entered directly with our payment provider, Stripe, and never reach our servers.
Data collected automatically
- Session data. A session token, used only to keep you signed in.
- Usage data. Which endpoints an account calls and how often, daily counts of which product features each organisation uses, and a log of the features each account uses and any errors it meets, with the time. The log is seen only by Kamba Risk staff, is used to fix problems and improve Kamba Risk, and is deleted after 90 days.
- Sign-in and activity data. When you sign in, how (password, Google, Microsoft or single sign-on), your browser type, and how long the app is open and in use each day. Your organisation’s administrators can see this for members of their organisation, so they can manage access.
- Enquiry data. If you ask for a walkthrough or to talk to us, the details you enter (your name, work email, organisation, role and message) and, if you tick the box, that you would like occasional product updates. We keep a record of exactly what you submitted and which version of this notice you were shown. Only Kamba Risk staff can see it.
- Technical data. IP address, browser and device type.
- Error data. Application errors and crashes.
Risk data you upload
Risk records and their descriptions, classifications, owners and dates; comments and annotations; and the audit trail recording who changed what and when. This is your organisation’s data. We process it to run the service and for no other purpose.
2. How we use it
- To authenticate you and run the service you asked for.
- To find and fix faults, and to monitor performance.
- To prevent fraud and abuse, and to meet legal obligations.
- To send service messages: security alerts, scheduled downtime, and changes to your account.
We do not sell personal data, and we do not use it to train machine learning models.
3. Legal basis
Under UK and EU GDPR we rely on the following:
| Purpose | Basis | Kept for |
|---|---|---|
| Account authentication | Contract | Account active, plus 30 days |
| Replying to enquiries and arranging walkthroughs | Legitimate interest, and steps taken at your request before a contract | 24 months after we last hear from you, unless you become a customer |
| Optional product updates by email | Consent (tick-box on the form; withdraw at any time) | Until you withdraw it |
| Fraud prevention | Legitimate interest | 2 years |
| Legal and audit compliance | Legal obligation | 7 years |
| Error tracking | Legitimate interest | 90 days |
For California residents: we do not sell personal information, and we do not share it for cross-context behavioural advertising. We do not currently respond to Do Not Track signals, because we run no third-party tracking for them to disable.
4. Your rights
You can ask us to give you a copy of your data, correct it, delete it, restrict how we use it, export it in a machine-readable format, or object to a particular use. California residents additionally have the right to know what is collected and the right to correct it.
Because your employer is the controller for risk data, a request about that data may need to go to them. Ask us either way and we will tell you which applies. Email support@kambarisk.com with your account email address and what you want done. We respond within 30 days.
5. Retention
| Data | Kept while | Then |
|---|---|---|
| User account | Membership is active | Purged after 30 days |
| Risk records | Your organisation keeps them | Deleted when they delete them |
| Session tokens | You are signed in | Revoked on sign-out |
| Audit logs | Active, plus 6 months | Purged after 7 years |
| Error reports | Under investigation | Purged after 90 days |
| Sign-in and activity history | Last 90 days | Deleted after 90 days |
| Activity and error log (per account) | Fixing problems and support | Deleted after 90 days |
| Feature usage counts (per organisation, per day) | Product improvement | Kept while the organisation’s account exists |
| Enquiries and walkthrough requests | 24 months after your last contact | Deleted, or when you ask us to erase them |
| IP addresses | Recent activity | Anonymised after 90 days |
On an account deletion request, the account and its sessions go immediately, organisational membership within 24 hours, audit log attribution is anonymised within 7 days, and backups are purged within 90 days. Audit logs, transaction records and anything subject to an active dispute are retained where the law requires it.
6. Sharing and processors
| Who | What they see | Why |
|---|---|---|
| Members of your organisation | Risk records and audit logs, subject to their role | To do their job |
| Google Cloud | All data at rest | Database, file storage and sign-in |
| Vercel | Data in transit while a request is handled | Hosting the website and application |
| Google (Gemini) | Text you submit to an AI feature | To generate the requested assessment |
| Resend | Invitee and inviter email addresses, organisation name; enquirer name and email | Sending invitation and enquiry confirmation emails |
| Stripe (from 3 November 2026) | Billing contact details and card details | Taking subscription payments |
| Sentry | Application errors | Fault diagnosis |
| Law enforcement | Only what a valid legal request compels | Legal obligation |
The current list, with locations, is kept at sub-processors. We have data processing agreements with each of them.
7. International transfers
Some processing takes place outside the UK and EEA, principally in the United States. Where it does, we rely on the UK International Data Transfer Addendum and the EU Standard Contractual Clauses. Contact us if you need the detail for a transfer risk assessment.
8. Security
Data is encrypted at rest and in transit. Access is role-based with per-organisation isolation enforced on the server, not in the browser. Session cookies are HttpOnly, Secure and SameSite. Requests are rate limited, and every change to a risk record is written to an append-only audit log. A fuller description is on the security overview.
If we suffer a breach affecting personal data, we will notify the ICO within 72 hours of becoming aware of it, and notify you without undue delay where the risk to you is high.
9. Cookies
We use two cookies, both strictly necessary. We run no analytics, advertising or third-party tracking cookies, which is why you are not asked to consent to any.
| Cookie | Purpose | Lifetime |
|---|---|---|
cardo_session | Keeps you signed in | 14 days |
cardo_csrf | Protects against cross-site request forgery | 24 hours |
10. Children’s privacy
Kamba Risk is a workplace tool and is not intended for anyone under 16. We do not knowingly collect their data, and will delete any account we find.
11. Changes
We will post any change here and update the effective date. Where a change materially affects your rights we will tell account holders in advance rather than relying on you to check.
12. Contact
Privacy questions and rights requests: support@kambarisk.com. General enquiries: support@kambarisk.com. Post: Kamba Risk Limited, 8-9 New Street, Alfreton, Derbyshire, DE55 7BP.
If you are unhappy with our response you can complain to the Information Commissioner’s Office at ico.org.uk, or to your local supervisory authority in the EEA.