Security and confidentiality
Our approach
Confidentiality is a design requirement, not an add-on. Before we decide how to build something, we decide what it must protect.
This page describes our approach and practices. It is not a certification, and it does not promise any legal outcome.
How we handle confidentiality
Collect the minimum
We ask only for the data a task needs. When we can build or test with sample data, we do. Real client information stays out of a project unless it is needed.
Access limited by role
People get access only to what their role requires. Access is given for a purpose and removed when it is no longer needed. This applies to our team and to people at your firm.
Human review of anything that uses AI
AI never makes a final decision on its own. A person reviews every result before it is used, and your team stays in control. We use AI only where it clearly helps.
Separate environments
Development, testing and live use are kept apart. Work in progress does not touch live data, and live data is not used for experiments.
Providers and data location
The providers we use depend on the project.
What we ask of your firm
Confidentiality works best when both sides take part. We ask your firm to:
- Share only the information a task needs
- Tell us who at your firm may see which information
- Tell us about any obligations your firm has toward its clients
- Let us know when people join or leave the project team
What is agreed by contract
Confidentiality is also a matter of agreement between your firm and us. Your firm's own duties to its clients still apply, and we build with them in mind.
Kalla Connect provides technology services and does not provide legal advice.
Questions about confidentiality
If your firm has specific requirements, tell us when you book a consultation. We will discuss them from the start.