Moodle uses a privacy API for GDPR compliance to allow plugins to specify how they deal with user data. Your plugin doesn't appear to store any user data so I suspect you shoudl be able to implement the simple null provider class.
Sites that use continuous integration processes will not be able to use your plugin because Moodle runs unit tests which check to see if all extra plugins include the privacy class.
Moodle uses a privacy API for GDPR compliance to allow plugins to specify how they deal with user data. Your plugin doesn't appear to store any user data so I suspect you shoudl be able to implement the simple null provider class.
Sites that use continuous integration processes will not be able to use your plugin because Moodle runs unit tests which check to see if all extra plugins include the privacy class.
More information on the privacy class is here: https://moodledev.io/docs/apis/subsystems/privacy
This is a plguins db approval blocker for plugins that integrate with an external tool (including SSO)