Admin Tools' Delete Inactive Users predates EU GDPR by eight years. It was never designed for this use case, nor should it ever be used for EU GDPR compliance.
Admin Tools' Delete Inactive Users was designed with exactly one use case in mind: deleting junk signups. This is why the triggers are account activation and whether the user has ever logged into the site.
For EU GDPR compliance, you should be looking at our free extension Akeeba DataCompliance. It does everything you described regarding account deletion. You can specify a time limit since the last login of the account which will result in the account being deleted. This is different to how Admin Tools works in three important ways:
- Accounts are not deleted if they belong in one of the user groups you have chosen to be exempt from deletion, or if a
privacy or datacompliance plugin indicates this account should not be deleted.
- An email is sent a set amount of time before the account deletion. The user has the chance to log into the site to "reset the timer", preventing their account from being deleted.
- The account deletion is identical to the user exercising their Right To Be Forgotten under the EU GDPR. It does not just delete the user account from the database, it wipes out all data held in your site about that user (as long as there is a compatible
privacy or datacompliance plugin telling it how to do it).
The first difference is essentially what you were asking for.
The latter two differences are MANDATORY for GDPR compliance and completely outside the use case Admin Tools' Delete Inactive Users was designed for. This is exactly why Admin Tools' Delete Inactive Users MUST NOT be used for GDPR compliance. You'd be non-compliant if you abused this feature for this use case.
Now you probably see why I insist on not adding the features you want in Admin Tools' Delete Inactive Users. If I did, you'd be even more tempted to abuse it for what you'd think is GDPR compliance, but it's actually not. I'd very much prefer that we have this discussion than you ending up in a situation you get fined for using the wrong tool for the task at hand.
I will close this by saying that having DataCompliance is not enough. You must make sure that you have privacy or datacompliance plugins for all extensions storing PII on your site, so that this data gets deleted when a user exercises their Right To Be Forgotten or get automatically wiped. You will most definitely need to talk to a lawyer specializing in GDPR compliance to determine what data on your site constitutes PII, a developer to ensure all plugins exist, are enabled, and configured properly, and possibly create a custom bridge with any business systems outside your site to correlate and remove client data from there as well. GDPR compliance is nowhere near as easy as just setting up a Scheduled Task in Joomla and calling it a day. You are looking at a multi-month project, as I am sure you're aware. I know you most likely know all of that, but I have to state the obvious because it's a public ticket which will be read by people who might have no idea.
Nicholas K. Dionysopoulos
Lead Developer and Director
🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!