Documentation

Customer data platform (CDP) documentation and access

This customer data platform (CDP) documentation index is for engineers preparing a PrivyCDP evaluation. Public pages describe scope and review questions; implementation requires the API contracts and operating documents for your selected release.

Request an architecture review Review Enterprise TCO Model →

Public contents

Choose the reference for your next decision

These pages are available now without a portal account. They explain evaluation scope and operating questions; they do not establish installer, API or connector availability for a particular release.

Deployment requirements

Compare on-premise, private-cloud and hybrid boundaries. Identify the teams that own networking, keys, backups, releases and incident response before preparing an environment.

Product architecture

Review the proposed ingestion, identity, profile and activation flow. Use the published architecture to prepare questions, then validate the selected release rather than infer production behavior.

Integration workflow

Plan one source-to-destination evaluation with synthetic records. Test authentication, identity changes, consent withdrawal, duplicates, failed delivery and recovery.

API and MCP contract checklist

Identify the schemas, authentication, limits and tool permissions to obtain before implementation. The public reference is a request checklist, not a complete executable API specification.

Security and control ownership

Map access, key custody, audit retention and support responsibilities. Ask for configuration-specific evidence and do not treat a framework label as a certification.

Licensing and operating cost

Separate usage rights, updates and support from hosting and integration work. Use current written terms with the three-year cost model before making a procurement decision.

Material to request for the selected release

Ask for supported environment prerequisites, verified installer artifacts, configuration and upgrade instructions, API descriptions, connector contracts and an operating runbook. Confirm which documents exist for your proposed scope and which require agreed confidentiality terms. Public descriptions of Helm, Terraform or a connector category are not a promise that a supported artifact has been delivered.

Use documentation in a bounded evaluation

Record the release and configuration beside each test result. Assign owners to missing documents and acceptance gaps. Start with synthetic data and an approved source and destination, then verify permissions, retries, reconciliation and recovery. A document being supplied does not establish that the configured workflow works; retain the observed result and unresolved limitations.

For help selecting material, use the evaluation resource index. For implementation access, request an architecture review with engineers. Customer portal access is permissioned and separate from these public references.

Discuss your deployment with engineers.

Bring your data flow, operating owners and evaluation questions.

Request an architecture review Review Enterprise TCO Model →Request permissioned references and release-specific evidence during evaluation.