Privacy Policy

Last updated: August 1, 2026

Bricky is an independent, hobby-scale project currently in early alpha, run by one person. This is a plain-language description of what data is (and mostly isn't) involved — not a policy written or reviewed by a lawyer, because there isn't a company behind this to have one.

The desktop app

Bricky (the launcher you install) keeps almost everything local to your own device:

Settings, installed Minecraft versions, mods, modules and layers, and your login session are all stored on your own machine. None of it is sent to us.
Signing in uses Microsoft's own login page, opened in your default browser — not a form inside Bricky. Bricky never sees your Microsoft password; that flow is entirely between you and Microsoft, governed by their own privacy policy.
Installing mods talks directly to Modrinth's API to fetch mod files and metadata. Modrinth's own privacy policy applies to those requests.
The auto-updater periodically contacts our server to check the current version and, if you choose to update, downloads the new installer from it. Like any web request, this shows up in ordinary server access logs (IP address, timestamp, requested file) — we don't tie that to your Microsoft account or any identity, and don't use it for anything beyond keeping the update pipeline working.
No telemetry, analytics, or automatic crash reporting is collected. Bug reports are entirely voluntary, submitted by you through Discord, with whatever details you choose to include.

This website

bricky.myky.cz doesn't use cookies, tracking scripts, or analytics. The server may keep standard access logs (IP address, page requested, timestamp) briefly for operating the site — the same baseline logging almost any web server keeps.

Changes

Bricky is under active alpha development, so this page may change as features change. Nothing here is retroactive — if something material changes about what data is involved, this page gets updated to reflect it.

Questions

Reach out on Discord.