Browser extensions privacy policy

VISIO Multimedia has built and published two browser extensions, Wide GitHub and Calendar Liberator, and this page is their privacy policy. Each has a section of its own below, because each asks for different permissions and does different things. What they have in common: neither sends anything to a server of mine, neither hands your data to a third party, and both are open source, so none of this has to be taken on trust. The one thing that can leave your device is a calendar Calendar Liberator publishes, and only to an address you set up yourself.

Wide GitHub

Wide GitHub is a browser extension that enhances the GitHub interface by making it wide and more readable.

What data it collects

Wide GitHub does not collect, transmit, or store any personal data or browsing history outside of your own browser.

The extension only stores the following information locally in your browser, or synchronises it via your browser's built-in sync features (such as Chrome Sync, Edge Sync or Firefox Sync):

• Whether the wide layout is enabled or disabled
• The list of custom domains you have added

No other data is collected, accessed, or transmitted by the extension.

How the data is used

The data stored by Wide GitHub is used solely to provide the extension's intended functionality, specifically:

• Remembering your preference for enabling or disabling the wide layout
• Applying the wide layout to GitHub, Gist, GitHub Pages, and any custom domains you specify

This data is never transmitted to any external server or third party.

Data sharing

Wide GitHub does not share any user data with any third parties.

All settings and preferences are stored locally in your browser or synchronised using your browser's built-in sync service, if you have it enabled. No data is ever sold, transferred, or used for advertising or analytics.

Permissions

Wide GitHub requests the following permissions:

• Storage: to save your extension preferences and custom domains.
• Scripting: to register the wide layout on custom domains you add.
• activeTab: to detect the domain of the current tab when you open the extension popup, so it can show whether that site is supported and offer to add it.
• Host permissions: by default the extension runs only on GitHub, Gist, and GitHub Pages. Access to any other website is optional and is requested only when you add a custom domain in the popup; it can be revoked at any time by removing the domain from the list.

These permissions are used only to provide the extension's intended functionality, and never for tracking, profiling, or collecting personal information.

Data retention and deletion

The preferences described above are kept only in your browser's local storage — or in your browser account, if you use its sync feature — for as long as the extension is installed. You can delete them at any time by removing the custom domains from the extension popup, or by uninstalling the extension, which removes all locally stored data. Data synchronised via Chrome Sync, Edge Sync or Firefox Sync is managed by your browser vendor under their respective privacy policies, and can be cleared from your browser account settings.

Open source transparency

Wide GitHub is open source: its entire codebase is publicly available at github.com/fabiocchetti/wide-github, so anyone can verify that it behaves exactly as described in this policy.

Calendar Liberator

Calendar Liberator is a browser extension that exports your Outlook Web calendar to a standard ICS file, ready to import into any calendar application. Optionally, it can upload that file to an address you set up and control, so your calendar apps can subscribe to it.

What data it collects

Calendar Liberator does not collect or store any personal data or browsing history, and it never sends anything to a server of mine.

To perform the export — and only when you explicitly start one by clicking "Export calendar" in the extension popup — the extension reads, locally in your browser:

• The calendar events Outlook Web shows for a 28-day window, from 7 days before the export to 21 days after: to cover it, the extension switches the tab to the weekly view, steps through the weeks, then returns to the page you were on. For each event it reads the title, date, start and end times, organizer, location or room, free/busy status, and whether it is a recurring occurrence. Declined and out-of-office events are skipped unless you choose to include them.
• Your account email address as shown in the Outlook interface, used solely to name the exported calendar when you do not give it a name yourself. When used, it appears in the calendar name inside the ICS file.

The extension does not read attendees, invitation text, meeting notes, or attachments, and it does not access your mailbox, files, or contacts. No other data is collected or accessed by the extension.

How the data is used

The information described above is used solely to provide the extension's intended functionality, specifically:

• Converting the events in your Outlook calendar into a standard ICS file
• Naming the exported calendar, so it is easy to recognise when importing or subscribing
• Delivering the file where you asked: to your device, or to the destination you configured

All processing happens locally in your browser.

Downloading or publishing the file

Download a file is the default. The ICS file is saved directly to your device, and in this mode the extension makes no network requests at all.

Publish to a URL is optional and off until you set it up. If you enter a destination URL, each export uploads the ICS file to that address with an HTTP PUT request, together with the authentication header you entered, if any. In that case:

• Your calendar data leaves your device and goes to the server you chose.
• I do not operate, host, or have access to that destination, and I receive no copy of your data.
• What happens to the file afterwards is governed by whoever runs that server: your own hosting, your employer's, or a provider you signed up with, under their own terms and privacy policy.
• Calendar apps cannot log in when they fetch a subscribed calendar, so anyone who knows the address the file is served from can read it. Treat that address as a secret.

You can stop publishing at any time by choosing Download a file or clearing the destination field: the extension then transmits nothing again.

Data sharing

Calendar Liberator does not share any user data with any third parties.

The extension has no backend, no accounts, no analytics, and no third-party services. The only outbound request it can ever make is the upload to the destination you configured yourself. No data is ever sold, transferred, or used for advertising, analytics, or tracking.

Permissions

Calendar Liberator requests the following permissions:

• activeTab: to interact with the Outlook tab you are currently viewing, only after you click the extension icon.
• Storage: to save the publishing settings described below, on your device only.
• Host permissions for Outlook and Office 365 domains: required for the content script that reads the calendar view on those pages.
• Optional host access: requested the first time you publish, and only for the destination you entered. If you never publish, it is never granted, and you can revoke it at any time from your browser's extension settings.

The extension does not request cookies, tabs, history, or any other permission. Its background script exists only to send the upload, because a request made from the Outlook page itself would be blocked by the browser. These permissions are used only to provide the extension's intended functionality, and never for tracking, profiling, or collecting personal information.

Data retention and deletion

Calendar Liberator keeps no calendar data: events exist only in your browser's memory for the few seconds the export takes, and nothing is kept afterwards.

If you use publishing, the extension stores in your browser's local storage the destination URL, the authentication header you entered, and the outcome and time of the last publish, so the popup can report it. This is deliberately local storage and not synced storage, so your destination and its credentials are never copied to your browser vendor's servers. You can remove them by clearing the destination field, and uninstalling the extension deletes them completely.

The output stays under your control: a downloaded ICS file lives on your device until you delete it, and a published one on your destination until you replace or remove it there.

Open source transparency

Calendar Liberator is open source: its entire codebase is publicly available at github.com/fabiocchetti/calendar-liberator, so anyone can verify that it behaves exactly as described in this policy.

Changes to this policy

If this policy changes, the updated version is posted here and the "Last updated" date at the bottom of the page is revised. The version published on this page is the one that applies.

Contact

These extensions are published by Fabio Biocchetti, who works under the name VISIO Multimedia. For a question or a problem with an extension, the fastest route is its issue tracker: Wide GitHub issues or Calendar Liberator issues.

For anything about this policy or your data — including the rights the GDPR gives you over personal data — write to privacy (at) visiomultimedia (dot) com. I read that address myself and reply within a month, as the regulation requires. There is also a contact form if you prefer.