Overview
Privacy Center is the package-owned compliance foundation for Capell consent and privacy workflows.
It intentionally does not replace package-specific consent capture in packages such as Insights or Newsletter. Those packages can continue to record their own operational evidence and later call Privacy Center Actions when they need a shared compliance ledger.
Foundation Scope
Section titled “Foundation Scope”- Consent policies and version metadata.
- Cookie/category consent decisions with hashed request evidence.
- Policy version acceptance records.
- Privacy subject requests for access, export, deletion, correction, restriction, and objection workflows.
- Retention rules for package-owned or integration-owned data domains.
- Retention execution Actions for delete, anonymize, and review workflows.
- Export and anonymization Actions that operate on Privacy Center records first.
- A retention schedule contribution so installers can discover the package-owned retention execution hook.
Integration Contract
Section titled “Integration Contract”Integrating packages should call Actions instead of writing Privacy Center tables directly:
RecordConsentActionRecordPolicyAcceptanceActionOpenPrivacyRequestActionCreateRetentionRuleActionApplyRetentionRuleActionApplyRetentionRulesActionBuildPrivacyExportActionAnonymizePrivacySubjectAction
Public frontend output must not expose Privacy Center internals, package names, model identifiers, admin URLs, or editor state.
Remaining Admin Surfaces
Section titled “Remaining Admin Surfaces”The current package owns the compliance records and workflows. Admin resources and dashboard widgets remain as explicit manifest deferrals until there is an operator UI for policy review, request queues, and retention health.