Security and oversight
Security and oversight, on by default.
A digital worker reads your records and takes actions in your systems. So the controls come first: what it can reach, what it may do alone, and how every step is recorded.
Our commitment
Your data never trains our models.
Customer data is used for one thing: doing the work you assign. It never trains our models. That is a KCorp-wide commitment, not a setting you have to switch on.
Used only to do the work you assign
Never used to train our models
The same rule in every KCorp company
Platform
Built on FusionK, the platform behind every KCorp company.
FusionK is KCorp's shared, multi-tenant, configuration-driven platform. KAgents runs on it, and so does our sister company KDoctor. Each new company starts from the same agent architecture, security framework and oversight model instead of building them from scratch.
About KAgents and KCorpTenant isolation
Each customer's data is kept separate from every other customer's on the platform.
Configured on the platform
Workers, rules, approvals and roles are set up through configuration on the platform. The same controls apply to every worker you hire.
A shared security framework
KAgents starts from the security framework and oversight model already in use at KDoctor, a sister company that is live with physicians.
Access
People sign in with SSO. Workers get only what you grant.
Access is set per person and per worker. Nothing is open by default.
For your team
Single sign-on
Your team signs in through your own identity provider with SSO.
Role-based access
Roles control who can assign work, approve actions, change rules and see results.
For digital workers
Scoped to the job
Each worker reaches only the systems, records and actions its tasks need, and only the ones you grant.
Read-only where the job allows
Data connections, such as your warehouse, start read-only. A worker gets write access only where a task needs it and you approve it.
Yours to revoke
You can change or revoke a worker's access at any time. Everything it did stays in the audit trail.
Encryption
Encrypted in transit and at rest.
Data is encrypted while it moves between your systems and the platform, and while it is stored.
Need technical detail for your review? Ask us, and we'll tell you plainly what we can share.
Human oversight
Every action has a record and an owner.
Digital workers act on your behalf. So you can always see what they did, why they did it, and who approved it.
Approvals
Mark any action as sensitive, such as payments, refunds, offers or emails to new contacts, and it waits for a named person to approve it.
Audit trail
Every step is logged: what the worker read, what it changed, which rule applied, and who signed off.
Escalation
When a case is unclear, out of policy or emotionally charged, the worker stops and hands it to a person with a summary of what happened so far.
Roles and permissions
Role-based access controls who can assign work, approve actions, change rules and see results. Workers reach only the systems and records you grant.
Audit trail
Illustrative exampleCopilot first, autopilot when you're ready
Every task starts in copilot: the worker prepares, and a person approves. You move a task to autopilot only when your team is confident, and you can move it back anytime.
Always needs a named approver
These actions always wait for a named person on your team. They can't be moved to autopilot.
What this looks like on each desk
Sends only from approved mailboxes, with messaging your team has signed off. Pricing, discounts and contract terms go straight to a rep.
Vanessa's guardrails
Refunds, credits and account changes above your limit wait for a named approver. Angry, legal or safety-related conversations go to a person right away.
Caleb's guardrails
Never releases a payment. Every payment run waits for a named approver, and every adjustment is logged with a reason.
Hannah's guardrails
Never makes a hiring decision. Applies the same criteria to every applicant, and a person decides who moves forward.
Spencer's guardrails
Connects read-only by default and changes nothing in your warehouse. Shows the SQL and sources behind every number.
Luke's guardrailsData handling
How your data is used, kept and removed.
Plain answers to the questions a data owner asks first. Where your requirements are specific, we confirm them with you before you commit.
Used only for your work
Workers read and write customer data only to do the tasks you assign. It never trains our models.
Results land in your systems
Workers act inside your CRM, helpdesk, ERP, ATS or warehouse, so results land in your systems of record. The platform keeps the audit trail of what each worker read, changed and sent.
Retention and deletion
Tell us how long records and audit logs must be kept, and how data should be removed when a worker or contract ends. We confirm what we can support before you commit.
Data residency
Need data kept in a specific region? Share your requirements and we'll confirm what we can support.
Security reviews
Running a security review?
Bring your questionnaire. Tell us what your review needs, and we'll walk through it with your security team and tell you plainly what we can provide today.
If your review requires a specific certification or report, ask us. You'll get a straight answer.
Bring us the work that keeps piling up.
Tell us which tasks eat your team's week. We'll show you how a KAgents worker would handle them, in your tools and under your rules.
Early access is open. No commitment.