Privacy and data
This page sets out what data moves between your Moodle site and LearnBoard, for the Moodle administrator and for whoever answers privacy questions about it. It matches the plugin’s privacy declaration in Moodle (classes/privacy/provider.php).
At a glance
Section titled “At a glance”- The plugin stores no personal data of its own in Moodle.
- It sends personal data to LearnBoard in three ways, each declared in Moodle’s privacy registry.
- Everything LearnBoard does to Moodle is read-only.
- Passwords, tokens, keys and site configuration are never read.
- Keys are never shown to the browser.
What the plugin sends to LearnBoard
Section titled “What the plugin sends to LearnBoard”1. Who is signed in (per-user sign-in)
Section titled “1. Who is signed in (per-user sign-in)”When per-user sign-in is on, the identity of the signed-in person is sent so that charts and the full app run as that person:
- the Moodle user id,
- their full name,
- the Moodle roles they hold, and the LearnBoard roles they map to,
- the address of your Moodle site.
It is sent from your Moodle server to LearnBoard, never from the browser.
2. Reporting data (the data connector)
Section titled “2. Reporting data (the data connector)”When the data connector is on, LearnBoard reads reporting data from your site’s database through the plugin: user profiles, enrolments, course activity, grades, completions and logs. The data is shown in LearnBoard dashboards for your organisation.
- User profile fields such as name, email, department and last access.
- Learning records: enrolments, activity logs, grades, completions and certificates.
Tables holding site secrets, and password, token and key columns, are never sent.
3. What any website receives (the charts)
Section titled “3. What any website receives (the charts)”To draw the charts, the viewer’s browser loads LearnBoard’s chart script and the figures straight from LearnBoard. So LearnBoard receives what any website receives from a visitor:
- the IP address of the browser,
- the browser and device the viewer uses.
The read-only guarantee
Section titled “The read-only guarantee”Everything LearnBoard does to your Moodle is read-only, enforced on your own server:
- Every statement is checked by the plugin before it reaches the database: reads only, this site’s reporting tables only, no secrets. See The data connector.
- The database session is set to read-only before any statement runs.
- You can go further and give LearnBoard a database account with SELECT rights only, in Read-only database user (optional).
- Every request is logged in
{dataroot}/block_learnboard/query-audit.log.
The charts in Moodle are read-only too. The only thing a block writes is its own layout, saved in Moodle when someone with block/learnboard:addinstance arranges it.
Keys and passes
Section titled “Keys and passes”| Item | Where it lives | Seen by the browser? |
|---|---|---|
| Embed API key | Plugin settings in Moodle; LearnBoard keeps only a fingerprint of it | No. Sent from your server only. |
| Connector key | Plugin settings in Moodle and in LearnBoard | No. |
| Connection code | Not stored anywhere after saving | No. |
| A chart pass | Made per page view, short-lived and read-only | Yes, so the charts can load. It is renewed while the page is open. |
Your data in Moodle’s privacy tools
Section titled “Your data in Moodle’s privacy tools”Because the plugin stores no personal data in Moodle, there is nothing for Moodle’s data requests to export or delete in the plugin itself. The privacy registry lists the three external locations above, so they appear in your site’s data registry and privacy summaries.