Hubs and Spoke Privacy Notice by Mozilla
Updated 10 December 2025
The Hubs and Spoke Privacy Notice explains how Mozilla collects and shares data for its real-time, browser-based collaboration tools, including account details, avatar and media uploads, technical analytics, and temporary voice and chat transmission. As an official Mozilla policy tied to the Mozilla Privacy Policy and backed by open-source codebases, it provides trusted transparency for users creating virtual rooms, scenes, and avatars.
[product/service name] Privacy Notice
[last updated date]
In this Privacy Notice, we explain what data [product/service name] collect and share, and why. We also adhere to the practices outlined in the [company name] Privacy Policy for how we receive, handle, and share information.
Information We Collect and Share When You’re In a Room
Information You Share With Us and Other Participants
We need certain information to operate [product/service name]. For example, we need information about your account in order to save your avatar. Here’s the information we may receive from you:
Account information: You don’t need an account to use [product/service name]. However, certain features (like storing your avatar), require an account. You can create an account through [company name] or through Discord. If you create an account with your email address, we store a hashed version of your email address. If you create an account through Discord, we receive the email address associated with your Discord account and your Discord avatar.
Room Name and URL: Rooms and room names are publicly accessible to anyone with the URL. [company name] 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.
Avatar data: Your selected avatar and name will be shared with other participants in your room. If you’re logged in to your account, we will store your avatar. If you’re not logged into your account, we will not store your avatar.
Voice data: If your microphone is on, [product/service name] sends the audio to other users in the room. [company name] does not store the audio; we only receive it temporarily to transmit it to others in the room.
Chat: If you send messages in [product/service name], [product/service name] shares it with the other users in the room. [company name] does not store chats; we only receive it temporarily to transmit it to others in the room.
Photos and Videos You Take, and Photos, Videos, and Objects You Upload: If you take photos and video in a [product/service name] room or upload photos, videos, or objects to a room, [company name] stores them so you can share them within the room. They are deleted within 72 hours unless you pin them. If you pin them they will be stored until you remove them from the room and they will be viewable by anyone who can access the room.
You can learn more by looking at the code itself: [product/service name] (the front-end) Dialog (the webRTC server), Reticulum (the backend web server), [product/service name]-Ops (the infrastructure code), Discord Bot (enables users to connect their Discord community to [product/service name]).
Other Information We Receive
We use technical, interaction, error, and website analytics data to help us improve the [product/service name] and [product/service name] experiences:
Technical data: We receive data about the type of device you use to interact with [product/service name], as well as its operating system, language, the name and version of browser, and other data needed to load and operate a room.
Interaction data: We receive data about your interactions with [product/service name], such as the number of rooms created, messages sent through or to third-party services like Discord (including aggregated counts such as the number of messages and users who have joined relevant channels), the number of users in a particular room, the start and end time of a your interaction with [product/service name], the amount of time you interact with [product/service name] through virtual reality, the first time in a particular month or day that you begins to use [product/service name].
Error Data: When [product/service name] crashes or fails, [company name] receives error messages which may include the room URL, response time for requests, the page you were on when you encountered the error, your operating system, browser information, and your IP address.
Website Analytics Data: We use [analytics software] to better understand how you interact with [product/service name] For example, we collect de-identified information about the number of [product/service name] rooms you create or enter, your interactions with buttons and menus, your session length, your location (country, state/province, and city), language settings, your browser type and version, viewport size, and screen resolution. You can opt-out of [analytics software] data collection by installing the [analytics software] Opt-out Browser Add-on.
Information We Collect When Your Create and Publish Scenes or Custom Avatars
Scenes and avatars you create: You need an account to create scenes in Spoke and custom avatars in [product/service name]. When you create a scene or custom avatar, [company name] stores that scene or avatar so we can display it.
Attribution information: When you publish a scene or avatar to [product/service name], you have the option to “Allow Remixing with Creative Commons CC-BY 3.0” or allow [company name] to promote your scene or avatar. If you choose one or both of these options, [company name] will share your scene or avatar and your attribution information publicly.
Account information: To publish a scene or avatar to [product/service name], you need to have a [product/service name] account. [company name] will receive and store a hashed version of your email address to allow you to log in and view your 3D Room models and Avatars.
You can learn more by looking at the code itself for Spoke.
Who [product/service name] May Disclose Information To
Amazon Web Services (AWS): [product/service name] and Spoke use Amazon’s cloud storage service to store the information collected through [product/service name]. You can read AWS’s Privacy Notice for more information.
Search providers: You can search for images, GIFs, and 3D Models to share in [product/service name]. When you search, we will send your searches to supported third parties to fulfill the search. [company name] does not store your search queries or the search results. We support the following providers:
Tenor
Sketchfab
YouTube
Twitch
Twitter: If you connect Twitter to [product/service name], you can tweet and share 2D images from [product/service name] rooms. Any content you tweet will be shared with Twitter and published on the Twitter platform. You can see Twitter’s Privacy Policy for more information.
Discord: If you connect Discord to [product/service name], we store access tokens and the server and channel IDs that have been connected. We will synchronize chat messages, room changes, 2D and 3D objects you create, and whether you join or leave with the connected Discord channel. [product/service name] does not log any synchronized messages. You can see Discord’s Privacy Policy for more information.
About this template
What is this template?
Hubs and Spoke Privacy Notice by Mozilla is a free, ready-to-use Data Protection & Privacy template you can open, customize, and download on GitLaw. It gives you a professionally structured starting point, so you never have to draft from a blank page. The wording is plain and modern, organized into clear sections that are easy to read, edit, and adapt to your own situation before you share or sign it.
When should you use it?
Reach for this Data Protection & Privacy template whenever you need a reliable agreement quickly and want to be sure the essentials are covered. It suits individuals, freelancers, startups, and established businesses alike. Instead of paying for a document drafted from scratch, you can start here, tailor the details to your arrangement, and have a polished draft ready in minutes. This version is drafted with United States of America in mind, though you should always review the final wording against the laws that apply to you.
What's typically included?
A well-drafted Data Protection & Privacy usually sets out the parties involved, the scope of the agreement, and each side's rights and responsibilities. Expect sections covering key terms and definitions, how long the agreement lasts, how it can be ended, and what happens if something goes wrong. This template brings those building blocks together in a sensible order, so you can focus on the specifics rather than worrying about what to include. Open it to read the full document, then sign up to edit, negotiate, and e-sign it directly in GitLaw.