Weave Code
Privacy Settings Bundle Laravel Package
symfinity/privacy-settings-bundle
A Symfony bundle for managing user privacy settings and consent preferences. Configure privacy options, persist choices, and integrate GDPR-style consent handling into forms, templates, and services with a simple, extensible API.
Privacy Settings Bundle
symfinity/privacy-settings-bundle provides a flexible foundation for managing user privacy preferences and consent in Symfony applications. It helps teams implement GDPR-friendly privacy controls with configurable categories, clear opt-in/opt-out flows, and persistent settings for each user.
- Configurable privacy categories and consent options
- User-level preference storage via Doctrine
- GDPR-ready consent tracking and audit-friendly records
- Twig components for building privacy settings forms
- Extensible services for custom consent policies
Frequently asked questions about Privacy Settings Bundle
- Is symfinity/privacy-settings-bundle a Laravel package or a Symfony bundle?
- It is a Symfony bundle, as indicated by both the -bundle naming convention and the package description, which targets Symfony apps with configurable privacy settings, consent capture, and Twig helpers. The provided materials do not show any illuminate/* dependencies or Laravel service provider wiring. Treat it as Symfony-first until composer.json proves otherwise, because that framework identity determines whether Laravel adoption is cheap or requires an adapter you own.
- Can I use this privacy settings bundle in a Laravel application, or do I need an adapter?
- A Laravel integration is not documented, and the technical assessment warns that feasibility drops sharply if the distribution is a Symfony bundle. You would likely need to own an adapter layer for container bindings, request lifecycle hooks, storage, and UI. Before committing, compare the total 24-month cost of that adapter against a Laravel-native consent package.
- How do I install symfinity/privacy-settings-bundle with Composer?
- The mechanical install is composer require symfinity/privacy-settings-bundle, but verify it resolves from Packagist rather than a VCS-only source, since VCS-only installs break artifact mirroring. In Symfony you would register the bundle in bundles.php and configure it. In Laravel, assume no package auto-discovery and plan explicit wiring. Also confirm license compatibility before adding it to your dependency graph.
- Does it support Laravel package auto-discovery, publishable config, and migrations?
- No Laravel auto-discovery, publishable config, or publishable migrations are documented; those are Laravel package conventions, while this is a Symfony bundle. Symfony bundles typically expose configuration through the bundle extension and services via the container. For Laravel you would have to build equivalent registration, configuration publishing, and schema ownership yourself. Verify whether the bundle ships reversible migrations or Doctrine entities before deciding.
- Which PHP and Laravel versions does it support?
- The package is at v0.2.3 and the provided assessment does not list a supported PHP or Laravel range; it explicitly asks you to confirm the composer.json constraints against your current LTS and next-hop target. Laravel support is not declared, so do not assume compatibility with any Laravel version. Check the package metadata and test against your matrix in a scratch app before planning an upgrade runway.
- What does the bundle actually do for privacy categories and consent capture?
- Per the overview, it adds configurable privacy settings and consent management to Symfony apps. You can define privacy policies, collect and track user consent, and expose settings through forms and Twig helpers. That covers cookie categories, marketing opt-in, and data-subject choices at the UI tier. Enforcement and storage details still need verification in the code.
- Is v0.2.3 safe for production GDPR consent management?
- Treat it as a candidate, not a decision. It is pre-1.0, so semver permits breaking changes on minor bumps, and the v0.2.3 release notes are only a link to CHANGELOG.md with no inline summary. For a package that gates regulatory behaviour, review the diff and changelog, pin to ~0.2.3, and review every minor. The regulatory blast radius means a defect could be an unlawful-processing event, not just a UI bug.
- How should I test consent enforcement and failure modes in a Laravel app?
- First determine the default behaviour when the package errors: fail-open means treatment as consent granted, which is disqualifying in a strict privacy context, while fail-closed is the safe default. Write tests for granted, denied, withdrawn, and unknown legacy states, plus error paths. If you build an adapter, test the adapter contract independently of the bundle. The provided materials do not document test coverage or CI posture, so ask for it.
- Can I join stored consent records to my users and export them for DSAR audits?
- This is unverified and is one of the highest-value questions to resolve. Confirm whether consent records are keyed to your user model or an anonymous subject identifier, whether migrations are publishable and reversible, and whether storage can target your existing database with joinable tables. Audit and DSAR fulfilment depend on exportable, queryable records. If the bundle owns an opaque table you cannot join, plan a backfill and dual-write period rather than a cutover.
- Who maintains this package, and what are the security and upgrade risks?
- The symfinity/* namespace suggests an individual or small organisation, so assume no vendor SLA, no LTS branch, and no security disclosure policy unless one is documented. Ask for a security contact and check release transparency, because opaque patch notes are a supply-chain weakness. Because consent data is stateful and audited, plan coexistence and a documented unknown/legacy state so historical users are not silently reclassified as opted in. If those risks are unacceptable, evaluate a Laravel-native alternative.
Weaver
How can I help you explore Laravel packages today?