Privacy Policy

From LibreELEC
Jump to: navigation, search
LibreELEC FAQs

The LibreELEC project staff are strong advocates of privacy. This page aims to disclose personal or system identifiable information that may be captured or retained by LibreELEC systems. It is a working document completed to the best of our current knowledge.

1 Update System

At startup and at periodic intervals your LibreELEC install contacts update.libreelec.tv and performs an update check to see if an updated LibreELEC release is available. The update check passes basic information about the running version of LibreELEC in order for the update server to respond back with the correct information. The information passed in the update check provides basic statistics on the number of active installations and projects/versions that can be filtered and charted to support development and scheduling decisions.

The complete list of information passed to the update system is:

  • SYSTEMID: An MD5 hash of the primary MAC address, e.g. eth0
  • DISTRIBUTION: The distribution name, e.g LibreELEC
  • PROJECT: The build-system project name, e.g. Generic or RPi2
  • ARCH: The CPU architecture, e.g. x86_64 or arm
  • VERSION: The LibreELEC release you are running, e.g. 6.90.005 or a development build number
  • x64_CPU: 1 or 0 (true or false) to indicate if the system has a 64-bit capable CPU

As SYSTEMID is a unique value it allows us to distinguish active systems. This is useful for the project because web download statistics and page hits do not give a clear picture on the size of our active user-base. It also allows us to create system groups. Group functionality allows us to restrict an update to a specific group of known test volunteers or boxes without forcing change to all systems. As the project grows in size it becomes more important to have this kind of selective testing capability.

The back-end database also tracks the date/time of last check (only one entry, there is no history) which allows us to determine the number of active systems in a given time range, e.g. active in the last 30 days. The update system also records the public IP address the update check was performed from. This is not visible to normal staff (only to the database admin) but can be dumped for periodic analysis (mapping) so we understand where we have geographic concentrations of users. This guides decisions on language support and where we need to recruit additional download mirrors.

The update process does not capture any information related to add-ons, plugins, usernames or passwords that you use.

The screen shot below shows what project staff can see about your system:

Privacy faq medium.png

The code for the settings addon can be reviewed on GitHub here: https://github.com/LibreELEC/service.LibreELEC.settings

Please raise any privacy related questions with the project team via the forums.

Stored personal identifiers

What is stored?

  • Public IP address and MD5 hash of primary MAC address

Why is it stored?

  • MAC is used as a unique system identifier, IP for understanding the geography of our user base

Where it is stored?

  • Update statstics database

How long it is stored for?

  • 30 days

Who has access?

  • A limited number of project staff have access to the update server admin client. IP data is only accessible to server administrators.

Will this change?

  • No changes are planned.

2 Web servers

Stored personal identifiers

What is stored?

  • Apache2 and Nginx web server logs. This include your public IP address and URIs requested.

Why is it stored?

  • For debugging issues with the servers.

Where it is stored?

  • In log files on the web servers.

How long it is stored for?

  • Typically for 7-30 days.

Who has access?

  • Server administrators only.

Will this change?

  • No changes are planned.

3 Wiki

Stored personal identifiers

What is stored?

  • Email and IP address used for login, and when editing any pages.

Why is it stored?

  • Storage of this information is native to mediawiki.

Where it is stored?

  • Wiki database.

How long it is stored for?

  • Indefinitely.

Who has access?

  • Server and wiki administrators.

Will this change?

  • No changes are planned.

4 Forum

Stored personal identifiers

What is stored?

  • Email and last signed in IP address

Why is it stored?

  • Storage of this information is native to mybb software.

Where it is stored?

  • Forum database.

How long it is stored for?

  • Indefinitely.

Who has access?

  • Server and forum administrators and forum moderators.

Will this change?

  • No changes are planned.

5 IRC

Stored personal identifiers

What is stored?

  • No personal information is intentionally stored.