PlumePilot Privacy Policy

Versione italiana

Last updated: 3 September 2026.

1. Controller and contact details

PlumePilot is created and maintained by Fabio Floris.

Privacy contact: plumepilot@gmail.com.

2. Purpose of PlumePilot

PlumePilot is an independent extension that adds local tools for accessing, organising and studying Pegaso courses that the user is already authorised to access.

PlumePilot is not affiliated with, endorsed by or distributed by Università Telematica Pegaso or Multiversity.

3. Information processed

When required by features selected by the user, PlumePilot may read and process:

• course structure, lessons, chapters, percentages and activity status;
• questions, answers and the status of self-assessment Tests and Objectives;
• links to course materials, images and other resources already available to the user;
• information displayed in the online exams section, such as course, date, grade, result, examination-board status and any reason communicated by the platform;
• preferences and interactions with the extension’s controls;
• local data relating to Achievements, EXP and cosmetic rewards.

PlumePilot does not directly request the user’s name, email address, student ID or payment information. Any personal information contained in Pegaso content is processed only within the browser to provide the requested features.

4. Authentication and requests to Pegaso

The Pegaso platform uses a session token to authorise its requests. PlumePilot may temporarily detect in memory the authorisation header already used by the page and use it exclusively to communicate over HTTPS with the Pegaso services required by its features.

The token:

• is not saved in the extension’s storage;
• is not recorded in logs;
• is not sent to the developer;
• is lost when the page context is closed or reloaded.

Requests may include reading course structure, activities and test sources, as well as completing Tests or Objectives when expressly enabled by the user.

5. Examination-board monitoring

When examination-board monitoring is enabled, PlumePilot may:

1. observe and reuse a recent exam response already received by the Pegaso page;
2. if necessary, make an additional HTTPS request to the same Pegaso service using the current session authorisation temporarily;
3. store locally the fields required to display exam status and recognise changes.

PlumePilot does not modify exam information held by Pegaso or send it to the developer.

6. PDF, EPUB and HTML materials

When the user starts an export, PlumePilot downloads only materials and images already accessible through the Pegaso account currently in use. Processing and file generation take place locally in the browser.

PlumePilot does not upload generated documents to its own servers or to third-party servers.

7. Data stored locally

The browser’s local storage may contain:

• extension preferences;
• temporary operation state;
• caches required to avoid duplicate requests or completions;
• Autoplay limit settings and state;
• normalised exam information and examination-board notification history;
• Achievement, EXP and reward state, together with records required to prevent duplicate rewards.

This data remains in the browser profile until the user deletes it or uninstalls PlumePilot.

While exports are being prepared, data relating to materials or tests may be stored temporarily in the extension’s local storage. This temporary data is removed when the operation is completed or cancelled.

8. Recipients and external services

PlumePilot communicates only with services required by its declared features:

• Pegaso and Multiversity services hosted on *.pegaso.multiversity.click, used for courses, activities and exams;
• CloudFront and Amazon S3 resources authorised in the extension package and used by the platform to provide course materials and images.

PlumePilot has no developer-operated servers. The developer does not receive data processed by the extension.

9. No tracking or data monetisation

PlumePilot does not use:

• remote analytics or telemetry;
• advertising;
• profiling;
• fingerprinting;
• the sale or commercial sharing of data;
• affiliate systems inserted into visited pages.

Donations to the project are voluntary and do not unlock features or result in different data processing.

10. Deletion

The user can:

• use Delete exam data to remove examination-board information and caches;
• reset Achievements to remove Achievements, EXP and rewards;
• uninstall PlumePilot to request that the browser remove the local storage associated with the extension.

Local deletion does not modify data stored by Pegaso.

11. Security

PlumePilot limits permissions and accessible domains to those required, uses HTTPS connections and does not execute remote code. No system can guarantee absolute security; vulnerabilities can be reported privately to plumepilot@gmail.com.

12. Changes to this policy

This policy will be updated when the extension’s features or data-processing practices change substantially. The latest update date will always be shown at the beginning of this page.

For questions about this policy or local data processing, contact plumepilot@gmail.com.

Documentation hosting

PlumePilot’s documentation and privacy policy are hosted through GitHub Pages. When these pages are visited, GitHub may process technical information such as the visitor’s IP address under its own privacy policy and for security purposes. This processing is separate from the operation of the PlumePilot extension.

Limited Use compliance

PlumePilot uses processed information exclusively to provide visible, user-requested features, in accordance with the Chrome Web Store User Data Policy, including its Limited Use requirements.

Data is not used or transferred for personalised advertising, profiling, credit assessment or sale to third parties. The developer does not receive and cannot read data processed by the extension. PlumePilot does not transfer it to parties other than the services technically required to provide the requested features.