A Filament panel for subject access and erasure requests in Laravel apps. Intake with deadlines, a preview of exactly what will be touched, and an evidence pack when it is done.
Someone emails asking for a copy of their data and their account deleted. The clock starts: one calendar month from receipt, extendable to three only if the request is genuinely complex, and only if you tell them inside the first month.
What happens now: a developer opens Tinker and starts hunting. Users, orders, tickets, an ID document in S3, a mailing list in a third-party tool, and the legacy table nobody remembered. Then $user->delete() either throws a foreign key error or wipes invoices the business is required to keep for years. Six months later an audit asks what you did, and the answer is a Slack thread.
Requests as a resource: type, subject, status, due date, countdown
A preview before anything is touched: every record, every file, every external system, plus unmapped tables that match the subject
Erasure that follows what should be followed and keeps what must be kept, with the reason recorded
Access exports as a readable zip delivered by a signed, expiring link
An evidence pack PDF: what was asked, who verified, what was erased, what was retained and why
Not legal advice, and it does not make anyone compliant. It gives you the machinery and the record.
Planned at $99 per project. First 50 on the list get it at $59, plus a year of updates.