Security and data responsibility.

How Kuga handles access and client data, and what your agency needs to manage.

How we protect the platform.

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.

Client separation

Each client has a separate workspace for their knowledge, conversations and access. Your agency manages them from one account.

Communications

Kuga uses appropriate protections for service communications, account operations, support workflows, and customer data handling.

Operational logging

Logs and telemetry may be used to monitor reliability, detect misuse, investigate incidents, and support platform operations.

Abuse prevention

Policies, monitoring, and enforcement help prevent spam, unlawful content, security abuse, data misuse, and unsafe deployments.

Responsible disclosure

Security reports go to security@kuga.ai. Reports should be lawful, safe, non-destructive, and limited to the issue being reported.

Shared responsibility.

What Kuga handles

  • Platform-level security controls and monitoring
  • Access controls for internal operations
  • Data processing terms and public policy documentation
  • Incident response and abuse investigation where appropriate

What customers handle

  • Accurate client content, lawful collection, and privacy notices
  • Correct account users, roles, and credential protection
  • Safe agent instructions, testing, and human escalation routes
  • Secure third-party systems and integration destinations

Security questions.

Do you have a DPA?

Yes. Review the Data Processing Addendum, then send remaining procurement questions to legal@kuga.ai or use the contact form.

Where do security reports go?

security@kuga.ai. Keep the first message limited to the issue. Do not send secrets, live credentials, or customer databases.

Are client workspaces separate?

Yes. Each client has their own knowledge, conversations, channels and access within a separate workspace.

Who writes the end-user privacy notice?

The agency or client. Kuga provides platform privacy, terms, and the DPA. The live agent still needs notices in the deployment context.

Can we get infrastructure diagrams?

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.

What should customers still own?

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.

Trust documents.

For procurement and privacy questions.

Pick a client you know.

Show them their AI.

Use their website to build a demo. Put your name on it and let them try it.

Start with a client