Download the PHP package elvinqulizade/filament-gdpr without Composer

Filament GDPR

Data retention & personal data management for Filament v5.

Filament GDPR gives you a retention policy engine and data-subject tooling on top of Eloquent:

• Retention policies — per model, define a retention period and what happens when it expires (delete or anonymize).
• Automatic privacy runs — scheduled (or manual) sweeps that anonymize or delete records past their cutoff.
• Run history — a log of every privacy run with processed/deleted/anonymized counts.
• Data subject exports — generate a ZIP archive (JSON + readable HTML) of all a subject's records for DSAR responses.
• A Filament panel — manage policies, trigger runs, view stats, and export a subject's data from the UI.

Installation

You can install the package via composer:

[!IMPORTANT] If you have not set up a custom theme and are using Filament Panels follow the instructions in the Filament Docs first.

After setting up a custom theme add the plugin's views to your theme css file or your app's css file if using the standalone packages.

Publish and run the migrations:

Publish the config file:

This is the contents of the published config file:

Registering the plugin

Usage

Retention policies

Retention policies are stored in the database and managed from the Filament panel (Privacy -> Retention policies) or via the facade:

Running the privacy sweep

Manually, or via the scheduler:

Scheduled runs are enabled by default (config('filament-gdpr.schedule'));

Exporting a data subject's data

Or from the Filament panel (Privacy -> Data subject request). Every export is stored in filament_gdpr_exports and written to the configured disk.

Using the facade

How anonymization works

Configured columns are masked with the chosen strategy:

• mask — keeps the first 2 characters, masks the rest (jo***); emails keep their domain (j***@example.com).
• static — replaces the value with the static value configured on the policy.
• null — sets the column to null.

Primary keys, timestamps, and password-like columns are never touched. Columns covered by a unique index are skipped unless allow_unique_overwrite is enabled.

Testing

Changelog

Please see CHANGELOG for more information on what has changed recently.

Contributing

Please see CONTRIBUTING for details.

Security Vulnerabilities

Please review our security policy on how to report security vulnerabilities.

Credits

• Elvin-Qulizade
• All Contributors

License

The MIT License (MIT). Please see License File for more information.