Privacy Center
Privacy Center manages privacy requests, consent records, policy acceptances, retention rules, and a public cookie preference centre.
Check compatibility before using this Beta extension
Beta does not mean production-ready. Review compatibility, support, site impact, and likely upgrade work before enabling it.
Release activity stays visible
These dates come from approved package releases, so you can see the release trail before installing.
- Latest approved release
- v1.1.0-beta.38 Sep 23, 2026
- Recent activity
- 1 approved release in the last 12 months
What Privacy Center helps you do
Marketplace listings can describe install impact and data access.
This installs as a Composer package. Check its removal guidance and retained-data policy before uninstalling it.
This private package is outside the Released and Beta channels, so no public install path is available.
Explore the available extensions on the demo site.
Standard support is included with a paid licence.
composer require capell-app/privacy-center
- Version
- 1.1.0-beta.38
- Runs on
- Capell 1.x, Laravel 12.41.1+ in the 12.x line or Laravel 13.x, PHP 8.4.
- Last release
- Sep 23, 2026
- Support
- Standard support
- Data access
- Reads and writes Capell content structures required by the package; public output receives rendered content only.
- Documentation
- Documentation
Privacy Center manages privacy requests, consent records, policy acceptances, retention rules, and a public cookie preference centre.
Administrators verify and process requests, review consent evidence, and dry-run retention rules before applying them.
Public cookie preferences are included, but public privacy-request intake and access or export delivery need an established operational process.
Use it when privacy work needs a recorded workflow in Capell instead of a separate spreadsheet of requests and consent evidence.
What changes on your site
Review the admin, public, data, scheduled, and command surfaces Privacy Center adds when enabled.
- Privacy Requests
- Consent Records
- Retention Rules
- Cookie Preferences
Before you install
Confirm version compatibility, support, data access, migrations, retained data, and removal steps first. Then install the Composer package from the account that owns access.
- Support
- Standard support
- Data access
- Reads and writes Capell content structures required by the package; public output receives rendered content only.
-
01
Require the package
composer require capell-app/privacy-center -
02
Register the extension
php artisan capell:extension:enable privacy-center -
03
Clear schema cache
php artisan capell:admin:clear-schemas-cache
Release notes and maintenance evidence
- Total downloads
- 0
- Last downloaded
- No downloads yet
Version history
1 release-
v1.1.0-beta.38Sep 23, 2026
Review evidence for this release
Privacy Center handles consent records, policy acceptances, data-subject requests and retention rules. Review found one high-severity defect - a retention rule set to Anonymize an unsupported record type reported success while anonymizing nothing - which was fixed before release: anonymization now fails loudly for any record type it does not implement, and the admin form only offers the supported types.
Review reduces risk, but it is not a permanent security guarantee.
- Reviewed version
- 1.1.0-beta.38
- Approval date
- Sep 19, 2026
Areas reviewed
- Strict, maintainable PHP
- Presentation-only public views
- Actions and typed boundaries
- Clean anonymous public output
- Authorisation and input safety
- Declared package boundaries
- Manifest and migration integrity
- Compatibility and interoperability
- Meaningful behavioural tests
- Security and supply-chain checks
- Performance and operational behaviour
- Theme delivery quality where applicable
- Marketplace claims matched to behaviour
- AI-assisted analysis with human accountability
Accepted limitations
- Export and erasure requests other than Delete rely on the operator or an integration to attach the actual export/erasure work before marking a request fulfilled; the fulfilment action itself only performs erasure for the Delete request type.
Before checkout
Know who owns access and what happens next
Payment, customer account ownership, site activation, and package access are separate steps. The checkout reference lets support trace a problem without moving the licence to another account.
Who processes the payment and taxes?
Lemon Squeezy is the seller and hosts paid marketplace checkout. Any VAT due is calculated and added by Lemon Squeezy at checkout, and Lemon Squeezy issues the tax receipt. Capell does not collect card details; it activates the matching marketplace licence after payment is confirmed.
Which account owns the licence?
The signed-in customer account that completes checkout owns the Capell licence, support history, and future install access. Capell surfaces a link to the tax receipt issued by Lemon Squeezy. Use the intended organisation account before paying.
How does the site receive package access?
The install flow connects the licence to the requesting site. Paid and private packages then use authenticated Composer access from the customer account that owns the licence.
What happens if checkout is cancelled or expires?
No licence is created until Lemon Squeezy confirms payment. After a cancellation or expired quote, return to the same marketplace listing and start a fresh checkout so price and package details are recalculated.
How do I request a refund?
Use the order link on the Lemon Squeezy receipt and request the refund through the Lemon Squeezy order receipt. If the receipt or order link is unavailable, contact Capell support so the payment and access record can be traced.
What should I do if access does not appear?
Keep the checkout reference from the page or receipt and contact support before trying another account. Support can trace the payment, customer account, licence, and connected site from that reference.
No approved reviews yet. Reviews from eligible customers appear here after moderation.