Is Mighty affiliated with Logitech?
No. Mighty is independent software. Logitech names are used only to describe device compatibility.
No. Mighty is independent software. Logitech names are used only to describe device compatibility.
A one-time license for Pro controls Mighty exposes for supported devices, including advanced tuning and button mapping where the mouse reports those capabilities.
Mighty recognises a fixed list of Logitech product identifiers rather than every Logitech device. Battery, DPI, and polling-rate features require a supported Logitech receiver: Unifying, Bolt, Nano, or LIGHTSPEED. A mouse connected only by a USB cable is not supported. A directly paired Bluetooth mouse on the recognised list is detected and listed, but the HID++ controls are not available over that connection.
Mighty does not write firmware and does not modify your mouse's stored onboard profiles. Changing the polling rate temporarily switches the mouse from onboard mode to host mode, and restores the previous mode if the write fails. Button remaps apply to the current session and are restored when Mighty exits.
Mighty processes mouse details locally. Anonymous product events, when you turn them on, use coarse categories such as connection type, capability-count bucket, battery bucket, and operation outcome. Mighty never sends model names, product IDs, serials, receiver slots, runtime IDs, exact DPI or polling values, exact battery percentages, HID traffic, profile names, application names, or support-report contents.
Use Homebrew: brew install --cask mikezamayias/mighty/mighty. Direct downloads use /downloads/mighty-latest.dmg. Mighty has no embedded auto-updater; the update check only tells you whether a newer version exists and opens the download page.
Send a support report from the app. It is composed on your Mac and nothing is sent until you send it yourself. If Mighty cannot support your setup, request a refund from the support page.
Analytics and diagnostics code exists only in Mighty 2026.8.1 and later, currently available on the mighty@beta channel. Releases up to and including 2026.7.16 contain no telemetry code at all and cannot send anything under any setting. 2026.7.16 is the current stable release, and it is what brew install --cask mikezamayias/mighty/mighty installs today. The answers below describe 2026.8.1 and later, after you opt in.
PostHog receives explicit anonymous events about app startup, navigation, onboarding, permission outcomes, device discovery and responsiveness, settings outcomes, low-battery notifications shown, paywall-configuration fetch outcomes, profile and mapping adoption, license-flow outcomes, Launch at Login, updates, and support actions. Properties are fixed enums, booleans, bounded counts, coarse buckets, and capped durations, and every event name and property is checked against a closed allowlist before it leaves your Mac. A random persistent device-level identifier connects events until opt-out; re-enabling creates a fresh identifier. PostHog uses EU ingestion, person profiles are disabled, Mighty forces geolocation lookup off on every event and the project discards client IPs, and Mighty never calls identify, alias, or group.
Sentry receives crashes, app hangs, release health, sanitized operation failures, and manual performance timings for startup, device work, profile application, licensing, Launch at Login, and user-requested update checks. In production only a sample of performance timings is sent. Default PII, network request data, logs, screenshots, view hierarchy, profiling, and automatic or network breadcrumbs are disabled. Before sending, Mighty clears the user, request, context, and extra fields and your Mac's machine name, and replaces every exception message and type with a fixed string. Choosing “Download Latest Version” opens the download page and fetches a small version manifest from Mighty’s own site; telemetry receives only completion time, outcome, and whether a newer version exists.
Anonymous analytics and crash diagnostics start disabled. Each system starts only after you enable its independent control. A first-launch or update notice explains both controls. Neither system affects device access, licensing, Pro features, or support.
Open Mighty → General → Privacy & Diagnostics. Analytics and crash diagnostics have independent switches and stop future collection immediately. Mighty also deletes queued, undelivered PostHog batches before analytics can restart. Enabling after opt-out starts a fresh SDK session and anonymous analytics identity. Events delivered before opt-out remain until normal retention expiry or an approved deletion request.
No. Mighty does not enable or use Session Replay. Screenshots, view hierarchy, element capture, key logging, mouse-movement video, clipboard access, file contents, browsing activity, text-field contents, button presses, and dispatched key sequences are not collected.
Mighty never sends license keys or fragments, customer email, Polar IDs, Mac names, usernames, device serials or IDs, profile names, bound app bundle IDs, application paths, authorization headers, URLs or query strings, request or response bodies, raw errors, source paths, HID packets, or support email/report content through PostHog or Sentry.
PostHog and Sentry projects use EU hosting. Opt-in PostHog events may be retained for up to 84 months (seven years) under the current project plan; this exception is approved for Mighty 2026.8.1 only. That 84 months is the ceiling the plan permits, not a deletion schedule. No automatic deletion is enforced on that project today, so assume delivered events persist until deleted by hand. Sentry diagnostics is retained no longer than 90 days, and the EU projects are currently configured for 30 days. Purchase and licence records are stored separately on Cloudflare, which is not EU-restricted. See the Privacy Policy for vendors, purposes, legal basis, security, opt-out, and deletion details.
No. Mighty does not identify analytics users or connect PostHog/Sentry data to a license, customer, email, or Polar record. Polar separately processes purchase, billing, tax, and license fulfilment data as Merchant of Record. To request deletion, contact support with enough information to locate the relevant record; truly anonymous events may not be technically linkable back to you.