Privacy
Installer reporting
To count installs and find failures, the installer reports whether an install started, finished or failed, the firmware it started from and the build. The event does not include a device identifier, account or email address.
The installer also reports when a supported instrument connects or an update ends in a rescue state. A temporary random identifier groups events from the same page load; it is sent with the event and is not stored in your browser. If an installation fails, a short error code is also reported. These events are recorded by the site and may be sent to Google Analytics for aggregate reporting, independently of the optional page-visit analytics choice below.
Website analytics and storage
On gjelly.com, you can choose whether to allow Google Analytics page-visit measurement. If you allow it, Google Analytics uses cookies and may collect information about your browser, device, approximate location and activity on the site. See Google’s explanation of Analytics data.
The site remembers your analytics choice in browser storage. It also uses a cookie, or temporary browser storage if a cookie is unavailable, to remember your choice to open the installer. A separate temporary cookie identifies your browser for installer checkout and update signup requests. After a confirmed contribution, browser storage records that you contributed. For one firmware build, the installer also stores a random configuration marker used when preparing an installation. Clearing your browser data removes these stored items.
Contributions and email updates
Contributions are optional. If you contribute, we send the amount and email address you provide to Stripe to create a checkout session; Stripe handles payment details and receipts. See Stripe’s privacy policy.
If you explicitly opt in to JamesOS updates, your email address and consent information are saved with Stripe. You can use the free installer without opting in.
Editor and project files
The Editor communicates directly with your instrument through your browser’s MIDI permission. Project files stay on your computer and are processed in your browser; their contents are not sent to the JamesOS server.
Privacy questions and email preferences
For privacy questions, requests about your information, or to unsubscribe from JamesOS updates, email [email protected].
Other services
Our hosting provider may process ordinary connection information, such as an IP address, to deliver and operate the site. Links to other services, including YouTube and GitHub, take you to sites with their own privacy practices.