Skip to content
Capell CMS

Privacy Center

Package docs status

Section titled “Package docs status”

This page is generated from package source documentation in the Capell packages repository and the checked-in manifest. Source documentation is not distribution status. Before running a Composer command, verify that the exact package and compatible 1.x release are available through public Packagist or the authenticated marketplace account.

FieldValue
Composer packagecapell-app/privacy-center
Package slugprivacy-center
Product groupCapell Security & Compliance
Tierpremium
Bundlesecurity-compliance
Runtime contextsadmin, console, frontend
Capell version^1.0
Source repositorycapell-app/packages
Source pathpackages/privacy-center
Docs sourcepackages/privacy-center/docs
Manifestcapell.json

What This Plugin Adds

Section titled “What This Plugin Adds”

Privacy Center is an Available, Schema-owning Capell package in the Capell Security & Compliance product group. It ships as capell-app/privacy-center and extends these surfaces: admin, console, frontend.

Privacy Center adds consent policies and records, policy acceptances, privacy requests, subject export and erasure, and configurable retention rules.

Visitors can update cookie preferences through the public consent centre. Admins manage policies, requests, consent evidence, and retention rules; public privacy-request intake is not included.

Evidence: src/Actions/RecordConsentAction.php, src/Actions/OpenPrivacyRequestAction.php, src/Actions/BuildPrivacyExportAction.php, src/Actions/ApplyRetentionRulesAction.php, routes/web.php, tests/Feature/PublicConsentPreferenceCenterTest.php, tests/Unit/PrivacyCenterAdminSurfaceTest.php, docs/overview.admin.md.

Status details:

  • Status: Available
  • Tier: premium
  • Bundle: security-compliance
  • Composer package: capell-app/privacy-center
  • Namespace: Capell\PrivacyCenter
  • Theme key: not applicable

Why It Matters

Section titled “Why It Matters”

For developers: Exporter and eraser registries let packages contribute subject data, while Actions own consent, verification, fulfillment, anonymization, and retention.

For teams: Operators can keep consent evidence and work privacy requests through a defined admin process instead of tracking them in separate spreadsheets.

Evidence: src/Support/PrivacySubjectExporterRegistry.php, src/Support/PrivacySubjectEraserRegistry.php, src/Actions/AnonymizePrivacySubjectAction.php, tests/Feature/PrivacyCenterFoundationTest.php, src/Actions/MarkPrivacyRequestVerifiedAction.php, src/Actions/MarkPrivacyRequestFulfilledAction.php, src/Actions/RejectPrivacyRequestAction.php.

Screens And Workflow

Section titled “Screens And Workflow”

Screenshot contract: docs/screenshots.json.

Privacy requests admin queue

Privacy request workflow actions

  • Privacy requests admin queue (admin, required).
  • Privacy request workflow actions (admin, required).
  • Privacy retention rules admin list (admin, required).
  • Privacy consent dashboard widget (admin, optional).
  • Privacy retention run review (admin, optional).
  • Privacy public subject request form (frontend, optional).

Technical Shape

Section titled “Technical Shape”
  • Service providers: Capell\PrivacyCenter\Providers\PrivacyCenterServiceProvider, Capell\PrivacyCenter\Providers\AdminServiceProvider.
  • Config files: packages/privacy-center/config/capell-privacy-center.php.
  • Migrations: packages/privacy-center/database/migrations/2026_05_31_000001_create_privacy_consent_policies_table.php, packages/privacy-center/database/migrations/2026_05_31_000002_create_privacy_consent_records_table.php, packages/privacy-center/database/migrations/2026_05_31_000003_create_privacy_policy_acceptances_table.php, packages/privacy-center/database/migrations/2026_05_31_000004_create_privacy_retention_rules_table.php, packages/privacy-center/database/migrations/2026_05_31_000005_create_privacy_requests_table.php.
  • Models: ConsentPolicy, ConsentRecord, PolicyAcceptance, PrivacyRequest, RetentionRule.
  • Filament classes: ConsentPolicyResource, CreateConsentPolicy, EditConsentPolicy, ListConsentPolicies, ConsentRecordResource, ListConsentRecords, ListPolicyAcceptances, PolicyAcceptanceResource, EditPrivacyRequest, ListPrivacyRequests, PrivacyRequestResource, CreateRetentionRule, and 4 more.
  • Route files: packages/privacy-center/routes/web.php.
  • Policies: AbstractPrivacyCenterResourcePolicy, ConsentPolicyPolicy, ConsentRecordPolicy, PolicyAcceptancePolicy, PrivacyRequestPolicy, RetentionRulePolicy.
  • Actions: AnonymizePrivacySubjectAction, ApplyRetentionRuleAction, ApplyRetentionRulesAction, BuildPrivacyCenterOverviewStatsAction, BuildPrivacyExportAction, CreateRetentionRuleAction, MarkPrivacyRequestFulfilledAction, MarkPrivacyRequestVerifiedAction, OpenPrivacyRequestAction, RecordConsentAction, RecordPolicyAcceptanceAction, RegisterConsentPolicyAction, and 1 more.
  • Data objects: ConsentPolicyData, ConsentPreferencesData, ConsentRecordData, PolicyAcceptanceData, PrivacyExportData, PrivacyRequestData, RetentionExecutionResultData, RetentionRuleData.
  • Command signatures: privacy:apply-retention.
  • Manifest action API: anonymizePrivacySubject: Capell\PrivacyCenter\Actions\AnonymizePrivacySubjectAction, applyRetentionRule: Capell\PrivacyCenter\Actions\ApplyRetentionRuleAction, applyRetentionRules: Capell\PrivacyCenter\Actions\ApplyRetentionRulesAction, buildPrivacyCenterOverviewStats: Capell\PrivacyCenter\Actions\BuildPrivacyCenterOverviewStatsAction, buildPrivacyExport: Capell\PrivacyCenter\Actions\BuildPrivacyExportAction, createRetentionRule: Capell\PrivacyCenter\Actions\CreateRetentionRuleAction, markPrivacyRequestFulfilled: Capell\PrivacyCenter\Actions\MarkPrivacyRequestFulfilledAction, openPrivacyRequest: Capell\PrivacyCenter\Actions\OpenPrivacyRequestAction, recordConsent: Capell\PrivacyCenter\Actions\RecordConsentAction, recordPolicyAcceptance: Capell\PrivacyCenter\Actions\RecordPolicyAcceptanceAction, registerConsentPolicy: Capell\PrivacyCenter\Actions\RegisterConsentPolicyAction.
  • Scheduled commands: privacy:apply-retention (daily).
  • Console command classes: ApplyRetentionRulesCommand.
  • Manifest contributions: admin-resource: Capell\PrivacyCenter\Manifest\ConsentPolicyResourceContribution, admin-resource: Capell\PrivacyCenter\Manifest\ConsentRecordResourceContribution, admin-resource: Capell\PrivacyCenter\Manifest\PolicyAcceptanceResourceContribution, admin-resource: Capell\PrivacyCenter\Manifest\PrivacyRequestResourceContribution, admin-resource: Capell\PrivacyCenter\Manifest\RetentionRuleResourceContribution, console-command: Capell\PrivacyCenter\Manifest\PrivacyCenterConsoleCommandsContribution, dashboard-widget: Capell\PrivacyCenter\Manifest\PrivacyCenterOverviewFilamentWidgetContribution, health-check: Capell\PrivacyCenter\Manifest\PrivacyCenterHealthContribution, model: Capell\PrivacyCenter\Manifest\PrivacyCenterModelsContribution, route: Capell\PrivacyCenter\Manifest\PrivacyCenterRoutesContribution, scheduled-job: Capell\PrivacyCenter\Manifest\PrivacyRetentionScheduleContribution.
  • Health checks: Capell\PrivacyCenter\Health\PrivacyCenterHealthCheck.
  • Blade views: packages/privacy-center/resources/views/consent/banner.blade.php, packages/privacy-center/resources/views/consent/preferences.blade.php.
  • Cache tags: privacy-center.

Shipped And Deferred Privacy Surfaces

Section titled “Shipped And Deferred Privacy Surfaces”

Privacy Center currently ships admin and console surfaces for consent policy records, privacy requests, retention rules, policy acceptances, retention execution, and audited DSAR handling. It also ships a cache-safe public preference center for cookie consent preferences, but it does not ship a public DSAR intake form.

Current boundaries:

  • Public consent: use the public cookie consent preference center and RecordConsentAction; RecordConsentAction can infer a subject from a source model when another package mirrors consent.
  • Subject data: the cross-package subject-data export/erasure registry is Action-backed through BuildPrivacyExportAction and AnonymizePrivacySubjectAction.
  • Request intake: open requests through OpenPrivacyRequestAction or admin workflows until a public DSAR intake route is shipped.
  • Evidence hashing: configure CAPELL_PRIVACY_CENTER_HASH_SECRET before relying on request or consent evidence hashes.
  • Admin surface: The admin provider contributes these Filament surfaces: consent policies, consent records, policy acceptances, privacy requests, retention rules, and the overview widget.

Data Model

Section titled “Data Model”
  • Required tables: privacy_consent_policies, privacy_consent_records, privacy_policy_acceptances, privacy_retention_rules, privacy_requests.
  • Models: ConsentPolicy, ConsentRecord, PolicyAcceptance, PrivacyRequest, RetentionRule.
  • Core record references in migrations: sites via site_id.
  • Migration files: 2026_05_31_000001_create_privacy_consent_policies_table.php, 2026_05_31_000002_create_privacy_consent_records_table.php, 2026_05_31_000003_create_privacy_policy_acceptances_table.php, 2026_05_31_000004_create_privacy_retention_rules_table.php, 2026_05_31_000005_create_privacy_requests_table.php.
  • Migration impact: run host migrations through the package install flow before opening package surfaces.
  • Deletion/retention behaviour: migrations declare cascade-on-delete relationships and null-on-delete relationships; retention is scheduled through privacy:apply-retention (daily).

Install Impact

Section titled “Install Impact”
  • Required packages: capell-app/admin, capell-app/core.
  • Admin navigation: declares admin-resource: ConsentPolicyResourceContribution, admin-resource: ConsentRecordResourceContribution, admin-resource: PolicyAcceptanceResourceContribution, admin-resource: PrivacyRequestResourceContribution, admin-resource: RetentionRuleResourceContribution; each Filament page or resource controls its own navigation visibility.
  • Admin/editor extensions: dashboard-widget: PrivacyCenterOverviewFilamentWidgetContribution.
  • Permissions: ViewAny:ConsentPolicy, View:ConsentPolicy, Create:ConsentPolicy, Update:ConsentPolicy, Delete:ConsentPolicy, ViewAny:ConsentRecord, View:ConsentRecord, ViewAny:PolicyAcceptance, View:PolicyAcceptance, ViewAny:PrivacyRequest, View:PrivacyRequest, Update:PrivacyRequest, ViewAny:RetentionRule, View:RetentionRule, Create:RetentionRule, Update:RetentionRule, and 1 more.
  • Public routes: loads routes/web.php; registers PrivacyCenterRoutesContribution.
  • Database changes: package migrations are declared.
  • Config: config/capell-privacy-center.php.
  • Settings: no package settings declared.
  • Queues or schedules: scheduled commands privacy:apply-retention (daily).
  • Cache tags: privacy-center.
  • Commands: privacy:apply-retention.

Common Pitfalls

Section titled “Common Pitfalls”
  • Keep required Capell packages on compatible v4 releases: capell-app/admin, capell-app/core.
  • Run migrations before opening package resources or public routes.
  • Review package configuration before production-like verification: config/capell-privacy-center.php.
  • Review middleware, throttling, signatures, and public-output safety in routes/web.php before exposing routes.
  • Register the host scheduler so these declared commands run at their documented frequencies: privacy:apply-retention (daily).
  • Keep public Blade and cached HTML free of authoring markers, model IDs, permissions, signed editor URLs, and lazy database queries.
  • Custom write integrations must preserve invalidation for privacy-center cache tags.

Troubleshooting

Section titled “Troubleshooting”
SymptomLikely causeCheckFix
Package surface is missing after installProvider or manifest is not loadedConfirm capell.json, package composer.json, and provider registrationReinstall the package, refresh Composer autoload, and clear host caches
Admin screen or command fails on missing tablePackage migrations have not runCheck the tables listed in Data ModelRun host migrations and rerun the focused package test
Route returns unexpected outputRoute cache, middleware, or signed URL setup does not match the package route fileCheck the route files listed in Technical ShapeClear route cache and verify middleware before exposing public routes
Background work does not runQueue worker or declared schedule is not activeCheck the jobs and scheduled commands listed in Technical ShapeStart the queue worker or host scheduler, then run the focused command or package test
Public output leaks unexpected stateRender data, cache variation, or authoring boundary has regressedCheck public Blade, cache tags, and public-output safety testsMove data loading out of Blade and rerun the package public-output tests

Quick Start

Section titled “Quick Start”
  1. Install the package: composer require capell-app/privacy-center.
  2. Run the required setup: php artisan migrate.
  3. Open the Privacy requests admin queue and confirm the admin workflow loads.

Next Steps

Section titled “Next Steps”