Weave Code
Gdpr Bundle Laravel Package
fluffy-factory/gdpr-bundle
Fluffy Factory GDPR Bundle gives Symfony apps practical GDPR compliance tools, including consent management, personal data export and deletion, and anonymization helpers, helping teams handle privacy requests and data protection requirements more easily.
GDPR Bundle
Frequently asked questions about Gdpr Bundle
- Is fluffy-factory/gdpr-bundle a Laravel package or a Symfony bundle?
- It is a Symfony bundle, not a Laravel package. Its integration contract is a Bundle subclass registered in bundles.php, a DependencyInjection extension, Twig templates, and Symfony-style YAML configuration. Laravel expects a ServiceProvider, Facade, publishable config, and Blade views, so there is no auto-discovery or container handoff.
- Can I use fluffy-factory/gdpr-bundle in a Laravel 10 or Laravel 11 application?
- Not directly. The technical evaluation rates architecture fit as poor for a Laravel stack because the package is packaged as a Symfony bundle and has no Laravel service provider or auto-discovery. You would need a shim or fork, and the cheaper path is usually to use it as a reference implementation rather than a dependency.
- What PHP and Symfony versions does this GDPR bundle support?
- The last release was April 2021, which places it in the PHP 7.4/8.0 and Symfony 4/5 era according to the evaluation. Laravel 10 and 11 require PHP 8.1/8.2+, so expect Composer resolution to fail or force downgrades. Always verify the exact constraints in composer.json and run composer why-not against your lock file.
- How do I install and configure the bundle in a Symfony application?
- In Symfony you would install it with Composer, register the bundle in bundles.php, and provide configuration through Symfony-style YAML plus the bundle's DependencyInjection extension. The bundle may also ship Twig templates and assets that need publishing or overriding. In Laravel none of that wiring is reused, so installation is not a simple composer require.
- Does the bundle create a consent record with a timestamp, policy version, and granted purposes?
- The overview describes consent management and consent-state persistence, but the evaluation flags proof-of-consent logging as a key question to verify. A 2021 consent banner often encodes older patterns and may not store timestamp, policy version, and granular purposes in an audit-ready form. Inspect the code and schema before relying on it for GDPR evidence.
- Does it support right-to-be-forgotten and personal data deletion workflows?
- The package overview advertises right-to-be-forgotten support for user data deletion workflows. However, the technical evaluation treats the functional scope as narrow, primarily a cookie consent banner and consent-state persistence, not a full GDPR platform. Verify the actual deletion orchestration and whether it covers your DSAR process before depending on it.
- What do the anonymization helpers do for personally identifiable information?
- The overview lists anonymization helpers for removing personally identifiable information, but it does not document the exact strategies or covered fields. You should review the source to confirm whether it anonymizes database columns, exports, logs, or only specific consent-related data. For Laravel apps, anonymization is usually better implemented in application services and jobs where you control the data model.
- Is the package maintained and tested enough for production GDPR compliance?
- The evaluation notes a last release in April 2021, 2 stars, 0 dependents, and no visible triage, which is a maintenance risk. Consent code is legally load-bearing, so a component without a clear CVE response path and test suite is a liability. Confirm the license, test coverage, and upstream activity before using it in production.
- What are better alternatives for GDPR consent management in Laravel?
- The recommended approach is to adopt a maintained consent layer, such as a JavaScript consent manager like Klaro or CookieConsent, or a commercial CMP, behind a thin Laravel service. Use this bundle only as a schema reference for consent state and cookie naming. That gives lower total cost and a better compliance posture than porting a stale Symfony bundle.
- How hard is it to fork and port this bundle to Laravel?
- The evaluation estimates roughly 3 to 5 engineering days to rewrite the DI wiring into a service provider, translate Twig markup to Blade, republish assets under public/vendor, and remap configuration. You also take on permanent ownership of the fork and its PHP/Laravel upgrade cycles. Only do this if a specific behavior in the bundle is uniquely required.
Weaver
How can I help you explore Laravel packages today?