Privacy Center
Keep consent evidence and privacy requests in one record.
- Version
- 1.1.9
- Released
- 10 November 2026
- Licence
- Commercial
Price £29.00
Check access and installationCheck your application before checkout
What it solves
The problem
Our operators need a record of consent and a way to work through privacy requests.
What your site gets
Our operators have consent evidence and an admin workflow for privacy requests.
Questions buyers ask
- Can visitors submit privacy requests through a public form?
- Public privacy-request intake is not included; requests can be opened through admin workflows or an action.
- How can visitors change cookie preferences?
- Visitors can update their preferences through the public consent centre.
- Who can review held privacy requests?
- Operators with request view and update permission can inspect held subjects and record independently verified outcomes.
Use it in your project
Let visitors manage cookie preferences and give staff a defined process for privacy work. Privacy requests are managed in the admin; a public request form is not included.
Picture it on your site
For a public site, decide which optional services depend on visitor preferences and how staff will handle privacy requests received through your chosen channel. Test both consent and refusal before launch. The package provides supported preference and admin workflows; it does not supply a public request form or make legal decisions for your organisation.
4 captures
Manage access and accountability
- Manage policies, acceptances and consent records.
- Process subject exports, erasure and retention rules.
Is this right for your project?
Decide what is being protected
Write down the protected resource, the people who should reach it and the decision that grants or removes access. That makes the extension part of a clear application policy instead of an isolated setting. Check the supported controls against your actual routes and records. The package does not decide your organisation's policy, and it should not be treated as a substitute for the rest of your security review.
Check refusal as well as access
Test an authorised person, an unauthorised person and a changed or revoked permission. Inspect both the response and the recorded activity where the package supplies it. Your application still owns authentication, role assignment and any routes outside the package's protection boundary. A visible admin control is not enough to establish that every public path is covered.
One customer organisation; up to 5 named users. Each entitlement covers one production website or application and up to two non-production environments, with a maximum of three active installations.
12 months of protected downloads, updates and included standard support.
You may ask Capell for a full refund within 14 days of purchase. Requests are assessed case by case against the recorded order, access and support history. This applies to live paid first-party packages; third-party author sales have separate terms. Read the Refund Policy
Renewal is charged at the price current when you renew. The price is shown before you pay.
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.
Paid checkout adds access to the purchasing account after payment. Review compatibility and site impact, then follow the installation steps for this package.
This listing has no page of its own in the demo. Open the demo to see Capell running.
Before you install
Review the impact below before running the commands in a covered Capell application, starting with a non-production environment. Required dependencies are listed above.
- Admin and public surfaces
- The package declares: administration screens, frontend integration, command-line operations, public routes. Review the release documentation for configuration and exposure in your application.
- Data and migrations
- Database migrations are declared. The installation flow can change your database; back up data and review the release migrations before installing. Reads and writes Capell content structures required by the package; public output receives rendered content only.
- Background work
- Scheduled background work is declared. Keep the host scheduler running and check the release documentation for queue workers, frequencies and pruning configuration.
- Access controls
- Package access controls are declared. Review role grants and the host authorisation configuration before allowing users into the new workflow.
- Removal and retained data
- A verified uninstall and retained-data assessment is not available here. Removing the Composer package does not establish that its data is deleted. Confirm cleanup, retention and dependencies with the publisher before removal.
-
01
Prepare protected Composer access
Sign in to the account with active package access. Open its generated installation instructions and configure the protected Composer repository before running the commands below. Keep access credentials private. Open my package installation instructions
-
02
Require the package
composer require capell-app/privacy-center -
03
Install the extension
php artisan capell:extension-install capell-app/privacy-center -
04
Activate the package licence
In this site’s Admin, open Marketplace, find Privacy Center (capell-app/privacy-center), and activate its licence using the purchase licence key if requested. This activates the package you have already installed. Wait for the Marketplace operation to succeed before continuing; keep its queue worker running.
-
05
Report the installed package
php artisan capell:marketplace:heartbeat
Release and review evidence
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.9 Nov 10, 2026
- Recent activity
- 13 approved releases in the last 12 months
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.9
- Approval date
- Nov 9, 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.
Access follows the account that owns the extension. Review the release trail and verification evidence here before installing.
Release notes and maintenance evidence
Version history
Showing the 10 most recent of 13 approved releases-
v1.1.9Nov 10, 2026 -
v1.1.8Nov 2, 2026 -
v1.1.7Oct 28, 2026 -
v1.1.6Oct 20, 2026 -
v1.1.5Oct 17, 2026 -
v1.1.3Oct 9, 2026 -
v1.1.2Oct 8, 2026 -
v1.1.1Oct 8, 2026 -
v1.1.0Oct 7, 2026 -
v1.1.0-beta.41Oct 4, 2026
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?
There is no self-service refund button. Email [email protected] within 14 days of purchase with the account email, the order or receipt reference, the package and your reason. Capell reviews the recorded purchase and, where approved, submits the refund through Lemon Squeezy. Read the Refund Policy
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.