Logstore xAPI

Privacy (GDPR) requests now include this plugin's data
The privacy provider previously declared that logstore_xapi_log and
logstore_xapi_failed_log hold personal data, but every export and deletion
method was an empty stub. In practice this meant:

a subject access (export) request returned nothing from these tables, and
a right-to-erasure request, or an ordinary user deletion, did not remove
the user's rows.
Both are now implemented. Export and deletion cover both tables and run
through Moodle's standard log privacy handling in tool_log, the same path
logstore_standard uses.

If your site has processed erasure requests while running an earlier
version, rows for those users may still be present in these two tables.
They are not removed retroactively by upgrading. Re-running the deletion for
the affected users, or clearing the tables, is the way to reconcile that.

The declared metadata has also been corrected: it now lists the fields that
actually exist (userid, relateduserid, realuserid, ip, other) and
no longer names a moodleuserid field, which was never a column in either
table.
https://github.com/davidpesce/moodle-logstore_xapi/releases/tag/v5.1.0