Account and access
Access is managed through account roles, permissions, and internal need-to-know controls. Customers remain responsible for inviting the right users and protecting credentials.
How Kuga handles access and client data, and what your agency needs to manage.
Access is managed through account roles, permissions, and internal need-to-know controls. Customers remain responsible for inviting the right users and protecting credentials.
Each client has a separate workspace for their knowledge, conversations and access. Your agency manages them from one account.
Kuga uses appropriate protections for service communications, account operations, support workflows, and customer data handling.
Logs and telemetry may be used to monitor reliability, detect misuse, investigate incidents, and support platform operations.
Policies, monitoring, and enforcement help prevent spam, unlawful content, security abuse, data misuse, and unsafe deployments.
Security reports go to security@kuga.ai. Reports should be lawful, safe, non-destructive, and limited to the issue being reported.
Yes. Review the Data Processing Addendum, then send remaining procurement questions to legal@kuga.ai or use the contact form.
security@kuga.ai. Keep the first message limited to the issue. Do not send secrets, live credentials, or customer databases.
Yes. Each client has their own knowledge, conversations, channels and access within a separate workspace.
The agency or client. Kuga provides platform privacy, terms, and the DPA. The live agent still needs notices in the deployment context.
This page does not publish internal architecture. For procurement, start with the DPA and privacy policy, then ask legal@kuga.ai for what you still need.
Who they invite, what the agent is allowed to say, lawful collection on the client site, and the third-party tools they connect. Kuga protects the platform.
For procurement and privacy questions.
Show them their AI.
Use their website to build a demo. Put your name on it and let them try it.