Old ACF entries in database cannot be removed.. why?

Why cant old UNUSED ACF entries in the database be removed?
This has been an issue brought up 7 YEARS ago.

https://support.advancedcustomfields.com/forums/topic/flush-unused-custom-fields/

Developer said it would be addressed
https://support.advancedcustomfields.com/forums/topic/flush-unused-custom-fields/#post-10035

But yet 7 YEARS LATER, the DB is still bloated with unused ACF entries and no way of ‘safely’ without some hack, to remove them.
How can I pass this on to a client?
How do I explain all of these database entries that came from creating during development and testing phase to a client?
What do I say when they ask for them to be removed?

How does a plugin of this level not ‘clean up’ after itself during deletion or even while still in use?

* Create some fields, and then delete those fields or even rename them in the admin.
Then use phpmyadmin / navicat, and see the entries still in the DB..

Deactivate the plugin, delete it.. and the entries are STILL in the DB.

Imagine developing a site using ACF for many fields, test fields, etc. How are these entries deleted?

• This topic was modified 2 years, 11 months ago by bernardberry646. Reason: urls