Privacy

Last updated: October 2026.

Your files stay in your browser

Tools that open files, including schematics, images, and audio, process them on your device. Those files are not uploaded to a pugtools server. If a tool calls an external service, the tool page says so.

Optional accounts and profiles

The unlisted account preview is disabled unless account services are configured. If enabled, signing in uses Clerk and the identity provider you choose. Clerk manages your account and essential sign-in cookies. Drafts you explicitly save and JSON files you explicitly upload are stored privately in Neon under your account identifier. Existing tools do not upload your work automatically. Signing out clears the preview on this device; it does not delete saved data. The account preview does not initialize analytics or session replay.

The profile preview can also save a local draft after you choose to start one. This draft stays in this browser and can include private goals. Exported profile files include those goals, so only share an export with people you intend to give that information to. Clearing the local draft removes it from this browser.

When cloud profiles are enabled, saving keeps your draft private. Publishing is a separate action that makes the selected profile fields accessible to anyone with the profile link. Personal goals are always excluded. Updating a draft does not update the published page until you publish again. You can unpublish or delete profile data; a previously claimed handle stays reserved to prevent someone else taking the link. Profile pages do not initialize analytics or session replay. Creator links open external sites with their own privacy policies.

Analytics

pugtools uses privacy-friendly, aggregate analytics to understand which tools and features are useful. We use Umami for page views, broad engagement signals, useful tool outcomes and errors, and views/clicks on support offers. Analytics is cookieless. We do not send file contents, typed searches, seeds, coordinates, or raw error messages. Tool-state query parameters and URL fragments are removed before tracking; short campaign labels are kept. A support-link click does not tell us whether a payment was completed.

Application diagnostics

When configured, we use PostHog to investigate application errors, count page loads by page address, and understand a small set of tool actions and completed results. Diagnostic errors use generic messages with sanitized application-code locations, and note whether the browser had translated the page (not the language). We remove tool-state query parameters and URL fragments, and do not send your files, project names, typed searches, seeds, or coordinates.

A sample of tool-page sessions can include masked interaction replays. Text and input values are masked. Images, audio, video, canvas previews, embedded apps and file inputs are excluded. We do not record console contents or network request and response bodies. An anonymous session identifier is kept in this tab's session storage to connect diagnostics and replay. We do not use tracking cookies, create a person profile, or link this identifier to an account.

Site owners can disable browser analytics and diagnostics by setting umami.disabled to 1 in browser local storage. Your browser may also block analytics requests.

To recognize whether this browser has been here before, the site keeps the date you first arrived, the date you last opened a given tool, and short campaign labels from the link that brought you here. Dates stay on your device; only coarse time bands are sent. Campaign labels can accompany actions during the current tab session. There is no account identifier attached to these values. Clearing browser storage clears this history. Analytics requests can also be blocked by your browser.

Developer API and MCP logs

The Pugtools developer service records structured operational data such as the endpoint or MCP tool used, success or failure, duration, cache status, result quality, requested data kind, version selection, and normalized static Minecraft identifiers. For MCP requests, the service may retain the client application's self-reported software name and version. It does not log user prompts, arbitrary request bodies, player usernames, UUIDs, or skin URLs. Player lookups, when enabled, contact Mojang's Java profile services and return an upstream skin reference instead of storing the image.

Donations and external links

Support links point to third-party platforms with their own privacy policies. pugtools does not process payments itself.

Contact

Questions about privacy? Reach out via the project's GitHub.