Privacy Policy

Last updated: October 20, 2026

This policy describes how Jojo’s Shenanigans handles privacy in our Android games, all our native apps and games for Windows, Linux, and macOS (including Steam releases), the Jambor Launcher, and our public GitHub issue tracker.

Playing our games

We do not collect gameplay telemetry, usage analytics, or advertising identifiers through our games. We do not sell player data. Our native desktop apps and the Jambor Launcher process the installation and host information described below for licensing; this is separate from gameplay analytics.

Games may save progress and preferences on your device. Those local files are not sent to us. You control them through the game or your device’s storage settings. Backups or cloud features provided by your operating system or distribution platform are governed by that provider’s settings and policies.

Licensing in native apps and the Jambor Launcher

Our native apps and games for Windows, Linux, and macOS, including the Jambor Launcher, use Jojo.Core.Licensing to capture and compare information about the host device for licensing. This desktop collection table does not apply to our Android games.

Your JojoId is an installation identifier generated independently of hardware attributes. You can find it in your app, including the launcher, and use it to reference your installation in a deletion request. It is not your name, an advertising ID, or proof of ownership. Different installations may have different IDs.

Information read by host operating system

The table lists the source values read locally, before protection. A source may be unavailable because of device capabilities or operating-system permissions; the collector does not elevate privileges to access it.

These are operating-system observations, not a complete hardware inventory. They can change after OS updates, hardware changes, or configuration changes. A UID or SID identifies an OS user context, not necessarily a particular person. Linux firmware identifiers may be inaccessible, and ARM devices may lack DMI sources.

How the information is protected

The module briefly reads raw values in process memory and converts each available value into a keyed fingerprint using HMAC-SHA-256, scoped to the installation. It returns the JojoId, schema and key identifiers, protected fingerprints, and signal availability statuses—not the raw source values. These outputs are pseudonymized device metadata, not anonymous data: they allow observations from the same installation to be compared.

Jojo.Core.Licensing itself does not log, persist, or transmit this information and does not issue or activate licenses. Storage, retention, and any transmission are responsibilities of the app integrating it; the module alone does not establish a server-side collection or retention period. Any introduction of server-side licensing collection will be described here before it starts.

This collector does not read host names, user names, IP or MAC addresses, disk inventories, or GPU inventories. Do not include raw device identifiers, fingerprints, or licensing keys in public reports.

Crash reports are your choice

We do not automatically send crash reports to the studio or open GitHub issues. If something goes wrong, you may choose to report it on our public issue tracker. Reporting is optional and is never required to play.

You decide what to share. A product name, version, platform, and description of the problem are usually enough to start. Logs, screenshots, save files, and other attachments are optional. We use the information you voluntarily provide to investigate the problem and reply to you.

GitHub reports are public

Anyone can read the tracker. Submitting an issue requires a GitHub account and makes your username, report, comments, and attachments visible to others. Public content can be indexed by search engines or copied by third parties.

Do not post personal or sensitive information beyond the JojoId needed for a deletion request. Before sharing an excerpt or screenshot, remove names, email addresses, account identifiers, private file paths, passwords, tokens, and other secrets. Do not upload full crash dumps or private files.

Public reports may remain available as a record of a problem and its resolution, including after an issue is closed. Closing an issue does not delete its contents. You can edit your contributions and ask the maintainers to remove content. We review those requests, but cannot guarantee removal of copies made by others. GitHub manages its own storage, backups, and account data under its Privacy Statement.

Stores, platforms, and this website

Google, Valve, and GitHub operate their own services. They may process account, purchase, device, usage, or diagnostic data under their own policies and settings. This policy’s description of collection by our apps does not describe all data handled by Android, Google Play, the Steam client, or GitHub.

• Google Privacy Policy
• Steam Privacy Policy
• GitHub Privacy Statement

Website analytics

We use Cloudflare Web Analytics to understand page views, traffic sources, and loading performance. It uses no analytics cookies, localStorage identifiers, persistent visitor identifiers, session recordings, or form capture. We do not add advertising trackers or custom click events.

The browser sends the page URL without query parameters or fragments, an origin-only referrer when available, a random page-load identifier, timing and memory measurements (including element selectors and resource URLs for performance attribution), and browser and operating-system version information. The page-load identifier is not a persistent visitor ID. Cloudflare receives your IP address as part of the network connection; according to Cloudflare, it does not use IP addresses to fingerprint visitors for analytics.

We skip analytics when Do Not Track or Global Privacy Control is enabled, when a referrer contains a path beyond its origin or other potentially sensitive URL components, and on pages whose URL does not match their canonical URL. We respect blockers and do not proxy analytics to bypass them. Reading the site works without JavaScript. These limits mean our counts are incomplete.

The analytics dashboard is for internal use. The audited third-party script is protected with Subresource Integrity: if Cloudflare changes it, the browser blocks it until we review the new version and update its hash. We do not maintain a separate raw-event archive. Cloudflare operates the analytics service under its own retention and data-handling policies; this setup does not establish a custom deletion period there. See Cloudflare Web Analytics and Cloudflare’s Privacy Policy.

GitHub Pages hosts this website and may process connection data, such as IP addresses, to operate and secure the service.

Request deletion using your JojoId

To request deletion of licensing data associated with your installation, open a deletion request in our public issue tracker. State that you are requesting deletion, name the app, and include the JojoId shown in that app or in the Jambor Launcher. If you are requesting deletion for several installations, include each relevant JojoId.

Your request and JojoId will be public and may be linked to your GitHub account, indexed, or copied. Share only the installation ID needed to locate the records; do not attach licensing keys, raw hardware identifiers, fingerprints, or private files. A public JojoId alone does not authorize deletion: we may need to verify that you control the installation before acting. We will review the request for data we hold and explain any limitations. Closing the request does not delete the issue itself or copies held by others.

Questions, removal requests, and changes

For privacy questions or requests concerning a public report, contact Jojo’s Shenanigans through the issue tracker. Reference the relevant issue or comment without repeating sensitive information. For data held by a platform, use the controls and contact options in its privacy policy.

We will update this page and its date if our practices change. Any future changes to collection by our apps will be explained before it starts, with consent requested where required.