Scoped per deployment
Each project defines what content, interaction data, system access, and operational records are needed for the approved use case.
Security & Compliance
CX Hero deployments are scoped around approved content, agreed integrations, defined permissions, GDPR-aware data handling, and client-specific access controls before launch.
Each project defines what content, interaction data, system access, and operational records are needed for the approved use case.
CX Hero is designed for secure, scalable deployment with encrypted communications, managed access, and client-specific configuration.
Security, privacy, permissions, integrations, and escalation paths are reviewed as part of onboarding.
GDPR-aware deployment
CX Hero can support UK and EU GDPR-aware deployment planning, including defined purposes for processing, access controls, data handling review, and client-specific documentation where required.

Controls
Where CX Hero Actions connect to business systems, the workflow is scoped around available APIs, permissions, review, and operational approval.
Administrative access and connected systems are configured around the deployment's approved roles and responsibilities.
CX Hero Actions depend on authorised access, defined workflows, data handling review, and reliable system connection points.
Procurement and compliance teams can request deployment scope, data handling, support, and integration information before launch.
Digital Human identity
Face cloning and voice cloning are paid one-off add-ons. They should only be used with approved source material, documented permission, and a clear commercial use case.
Created from approved source material for a defined deployment, subject to client sign-off.
Created from approved source material for commercial deployment use, subject to client sign-off.
Custom attire is scoped separately because design, approvals, and deployment context vary.
Procurement support
For enterprise deployments, CX Hero can support procurement and security review with the information needed to scope risk properly.
Data processing terms can be reviewed during procurement where required.
Security and supplier questionnaires can be supported as part of the sales process.
Retention needs are reviewed around the specific interaction, analytics, and integration model.
Security requirements are easiest to review once the location, data, systems, and workflows are known.
Share the deployment context, systems involved, data handling needs, and procurement requirements so CX Hero can respond with relevant information.