Scope and contact
This policy covers the Moodle plugin Question Hub (qbank_questionhub). The plugin runs inside a Moodle site operated by your school or organisation and connects it to the Question Hub at hub.cblum.ch. The Hub is a separate service, also run by Cyril Blum, with its own accounts and data processing; this policy describes only what the plugin stores and sends.
For questions about the plugin, contact Cyril Blum at apps@cblum.ch. The operator of your Moodle site decides how Moodle data is kept and is your first contact for data stored there. This policy describes the reviewed source of version 1.0.43; other versions may behave differently. The privacy notice for the cblum.ch website applies when you visit its pages.
What the plugin stores in Moodle
When a person links a Hub account, the plugin stores in the Moodle database: the Moodle user ID, the access token (an OAuth token or a personal access token), the Hub user ID, the email address and display name of the Hub account, and when the link was created.
It also keeps an audit log of import and publish actions with the Moodle user ID, package ID, package version, action and time. The log entries also hold the package title, course, question category and number of questions. To recognise questions on later imports and to show local changes, the plugin stores which question versions belong to which package version; these records are tied to questions, not to people.
Moodle’s privacy API (Privacy and policies) can export the linked Hub profile and delete the stored tokens and log entries of a person. Disconnecting the account deletes the stored token. Whatever else is retained depends on the Moodle site’s own backups and settings.
What the plugin sends to the Hub
Requests go from the Moodle server to the Hub. With a linked account, every request carries the access token, which identifies the Hub account. The plugin does not send the Moodle username, name or email address. Browsing and importing public packages also works without a token.
Question content and package details are sent only when someone publishes, pushes, forks or edits a package. Questions are sent as Moodle XML: question texts, answers, feedback, hints, tags and embedded files such as images. Package details are title, summary, release notes, tags, licence, visibility, subject classification and, optionally, a GitHub repository. These contain personal data only if the person includes it, for example a name in a question text, an image or feedback. The plugin asks users not to include any personal data, in particular no student names or grades.
When an account is linked with OAuth, the browser of the teacher opens hub.cblum.ch to sign in, and the Hub receives the address of the Moodle site as the return address. On disconnect, the plugin asks the Hub to revoke an OAuth token.
The Hub and published content
Packages published as public are open educational resources: anyone can see them on the Hub, download them and, depending on the licence, change and share them. Private packages are visible to the people you approve. The author details shown with a package come from the Hub account. Withdrawing a package removes it from the Hub, but copies already imported into other Moodle sites stay there.
Accounts, packages and access requests on the Hub are handled by the Hub service. For questions about Hub data, contact the same address.
No tracking
The reviewed plugin source contains no analytics, advertising or tracking code. It contacts no other service than the Hub. When a package is linked to a GitHub repository, the Hub commits the versions there, not the plugin.
Your choices and rights
You can use the plugin without linking a Hub account, disconnect a linked account at any time and withdraw packages you published. For data in Moodle, contact the operator of your Moodle site; for data held by the developer, write to the address above. Mandatory privacy rights under applicable law remain unaffected.
Use and liability notice
Use is at your own risk. To the extent permitted by law, the plugin is provided without warranty of accuracy, completeness, availability or fitness for a particular purpose, and liability for damage from use or unavailability, including data loss, lost profit and consequential damage, is excluded. Mandatory statutory rights and liability remain unaffected, including intent, gross negligence and personal injury where exclusion is not permitted.