зеркало из https://github.com/mozilla/hubs.git
5.0 KiB
5.0 KiB
Privacy Notice for Hubs and Spoke
Version 3.0, October 16, 2018
At Mozilla (that’s us), we believe that privacy is fundamental to a healthy internet.
In this Privacy Notice, we explain what data may be accessible to Mozilla or others when you use Hubs or Spoke. We also adhere to the practices outlined in the Mozilla privacy policy for how we receive, handle, and share information we collect from Hubs.
Things you should know:
Your presence and communications are sent to Mozilla and other Room participants.
- Avatar data: We receive and send to others in the Room the name of your Avatar, its position in the Room, and your interactions with objects in the Room. Mozilla does not record or store this data. You can optionally store information about your Avatar in your browser’s local storage.
- Room data: Rooms are publicly accessible to anyone with the URL. Mozilla receives data about the virtual objects and Avatars in a Room and shares that data with others in the Room.
- Voice data: If your microphone is on, Mozilla receives and sends audio to other users in the Room. Mozilla does not record or store the audio. Be aware that once you agree to let Hubs use your microphone, it will stay on as long as you remain in a Hubs room, unless you turn it off.
- You can learn more by looking at the code itself for Hubs. Janus SFU, Reticulum, Hubs, Hubs-Ops
Mozilla receives data you create and share with Spoke and Hubs.
- Images and Video: Mozilla receives video and image file links to process and display them in the Hubs Room. Mozilla stores this data as long as you remain in the Room.
- Scenes You Share: Mozilla receives 3D Room model links and the name of the Room in order to process and display the Room. Mozilla stores the name and the URL for the link you share so you and others with the link to the Room can use it again.
Mozilla receives data when you create and publish Scenes with Spoke.
- Scenes You Create: When you create a scene with Spoke, Mozilla receives a copy of that scene. Mozilla stores that data in order to be able to process and display the scene through Hubs.
- Publishing Your Scene: When you publish a scene to Hubs using Spoke, Mozilla will ask for your email address to send you a link to verify your scene. Mozilla will receive and store your email address to allow you to log in and view your 3D Room models. Mozilla stores a hashed version of email addresses you use to publish a scene, so the stored versions are not available in readable form.
- Remixing and Promotion: When you use Spoke to publish a scene to Hubs, you have the option to “Allow Remixing with Creative Commons CC-BY 3.0” or “allow Mozilla to promote my scene.” If you choose one or both of these options, Mozilla will share your scene publicly and you will have the option of including attribution information, which will also be publicly available.
- You can learn more by looking at the code itself for Spoke.
Mozilla receives technical and interaction data to improve performance and stability.
- Technical data: We receive and store data about Room URLs and names; the type of device you use to interact with Hubs, as well as its operating system, language, the name and version of browser; and other data to load and operate the Room.
- Interaction data: We receive data about your interactions with the Hubs service itself such as the number of Rooms created, the maximum number of users in a particular room at one same time, the start and end time of a user’s interaction with Hubs, the amount of time a user interacts with Hubs through Virtual Reality, the first time in a particular month or day that a user begins to use Hubs. Mozilla uses third party services to store and analyze these operational messages.
- Error Data: In order to diagnose problems, Hubs sends Mozilla logs of error messages (which include the Room URL, response time for requests, the page you were on when you encountered the error, your operating system, browser information, and may include your IP address).
- You can learn more by looking at the code itself for Hubs. Janus SFU, Reticulum, Hubs, Hubs-Ops