Privacy Center

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.

Field	Value
Composer package	capell-app/privacy-center
Package slug	privacy-center
Product group	Capell Security & Compliance
Tier	premium
Bundle	security-compliance
Runtime contexts	admin, console, frontend
Capell version	^1.0
Catalogue role	extension
Release channel	Beta
Source repository	capell-app/packages
Source path	packages/privacy-center
Docs source	packages/privacy-center/docs
Manifest	capell.json

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.

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

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.

Screens And Workflow

Screenshot contract: docs/screenshots.json.

• Privacy requests admin queue (admin, required evidence).
• Privacy request workflow actions (admin, required evidence).
• Privacy retention rules admin list (admin, required evidence).
• Privacy public subject request form (frontend, supplementary evidence).
• Privacy requests admin queue with admin sidebar menu open (admin, supplementary evidence).

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
• packages/privacy-center/database/migrations/2026_10_04_000001_remove_implicit_timestamp_updates_from_privacy_center_privacy_consent_records.php
• packages/privacy-center/database/migrations/2026_10_04_000002_remove_implicit_timestamp_updates_from_privacy_center_privacy_policy_acceptances.php
• packages/privacy-center/database/migrations/2026_10_04_000003_remove_implicit_timestamp_updates_from_privacy_center_privacy_requests.php

Models

• ConsentPolicy
• ConsentRecord
• PolicyAcceptance
• PrivacyRequest
• RetentionRule

Filament classes

• ConsentPolicyResource
• CreateConsentPolicy
• EditConsentPolicy
• ListConsentPolicies
• ConsentRecordResource
• ListConsentRecords
• ListPolicyAcceptances
• PolicyAcceptanceResource
• EditPrivacyRequest
• ListPrivacyRequests
• PrivacyRequestResource
• CreateRetentionRule
• EditRetentionRule
• ListRetentionRules
• RetentionRuleResource
• PrivacyCenterOverviewFilamentWidget

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
• RejectPrivacyRequestAction
• SeedPrivacyCenterScreenshotFixtureAction

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; package registered)

Console command classes

• ApplyRetentionRulesCommand
• SeedPrivacyCenterScreenshotFixtureCommand

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
• migration: Capell\PrivacyCenter\Manifest\PrivacyCenterMigrationsContribution
• 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

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

• 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, 2026_10_04_000001_remove_implicit_timestamp_updates_from_privacy_center_privacy_consent_records.php, 2026_10_04_000002_remove_implicit_timestamp_updates_from_privacy_center_privacy_policy_acceptances.php, 2026_10_04_000003_remove_implicit_timestamp_updates_from_privacy_center_privacy_requests.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; registered by the package provider).

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, Delete:RetentionRule; access also governed by package policies: AbstractPrivacyCenterResourcePolicy, ConsentPolicyPolicy, ConsentRecordPolicy, PolicyAcceptancePolicy, PrivacyRequestPolicy, RetentionRulePolicy.
• 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; package registered).
• Cache tags: privacy-center.
• Commands: privacy:apply-retention.

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.
• Keep the host Laravel scheduler running so package-registered schedules can execute: privacy:apply-retention (daily; package registered).
• 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

Symptom	Likely cause	Check	Fix
Package surface is missing after install	Provider or manifest is not loaded	Confirm capell.json, package composer.json, and provider registration	Reinstall the package, refresh Composer autoload, and clear host caches
Admin screen or command fails on missing table	Package migrations have not run	Check the tables listed in Data Model	Run host migrations and rerun the focused package test
Route returns unexpected output	Route cache, middleware, or signed URL setup does not match the package route file	Check the route files listed in Technical Shape	Clear route cache and verify middleware before exposing public routes
Background work does not run	Queue worker or declared schedule is not active	Check the jobs and scheduled commands listed in Technical Shape	Start the queue worker or host scheduler, then run the focused command or package test
Public output leaks unexpected state	Render data, cache variation, or authoring boundary has regressed	Check public Blade, cache tags, and public-output safety tests	Move data loading out of Blade and rerun the package public-output tests

Quick Start

1. Install the package: composer require capell-app/privacy-center.
2. Open the package admin surface at /admin/privacy-center/privacy-requests and confirm Privacy Center is available.

Next Steps

• Package docs
• Overview
• Worked extension examples
• Admin guide
• Configuration files: config/capell-privacy-center.php.
• Troubleshooting
• Screenshot contract
• Marketplace assets
• Capell content language plan
• Capell documentation design system
• Capell and package ERD notes
• Related packages: Access Gate, Contacts, Insights, Newsletter.