Rights Orchestration
Right to Access retrieves information about the data subject from Candu's system, and Right to Delete removes it.
Ketch and Candu
Fulfill rights requests against in-app experience data, using an identifier that's managed automatically.
About Candu
Candu helps software teams design and personalize their application's user interface, which means the data it holds is tied to how individual users actually experience a product's interface. Reaching that data for a rights request needs a reliable identifier, and Candu's own User ID is managed by Ketch automatically rather than requiring manual setup.
Ketch connects to Candu to fulfill both access and deletion requests against that data.
Capabilities
How Ketch works with Candu
The Ketch Candu integration covers Rights Orchestration. Connection uses an API Key, and identifier mapping uses a managed User ID requiring no manual configuration.
With Ketch, teams can
- Fulfill access and deletion requests against Candu product experience data through the same workflow used for every other connected system
- Skip manual identifier configuration, since the User ID is managed automatically
- Connect using a single API Key
The gap
The problem this integration solves
Product experience platforms tied to in-app personalization still hold real personal data, and rights requests need a reliable way to reach it:
01. Manually locating and removing a specific person's product experience data doesn't scale to real request volume
02. An identifier that requires manual setup adds friction and risk of misconfiguration
03. In-app experience tools are sometimes deprioritized in privacy programs focused on core customer systems
Ketch resolves this by giving Candu a structured rights workflow, using a managed identifier that removes manual configuration risk.
Why Ketch
Why teams choose Ketch for Candu privacy compliance
Permissioning infrastructure that governs Candu the same way it governs every other system in your stack — not a one-off connector bolted onto a banner.
Managed identifier, no manual setup
The User ID requires no configuration action, reducing setup risk.
One rights workflow, not a manual process
Candu requests move through the same Data Subject Rights Automation used for every other connected system.
Backed by enforcement precedent
The California Attorney General reached a $1.55 million settlement with Healthline Media over sharing sensitive data with advertisers without valid consent, a reminder that any platform holding personal data, in-app experience tools included, carries real exposure when rights requests aren't fulfilled completely.
Questions about the Candu integration
Related reading
Expert insights for teams connecting Candu
Integrations
Pre-built APIs with 1,000+ systems, apps, and models
Ketch ships connectors and SDKs so consent, rights, and policy flow into your CDPs, warehouses, ad platforms, and AI stack — without a custom data pipeline.
See Candu permissioning running end to end
Book a demo to walk through rights, consent, and preference orchestration on your stack — or start free and connect Candu yourself.
Get Started Free
Get started in less than 5 min