DMGKit Download
DMGKit · Legal

Privacy Policy

Effective date: October 26, 2026

1. Introduction and responsibility

Fuse Labs is a sole proprietorship based in Ontario, Canada. In this policy, “Fuse Labs,” “we,” “us,” and “our” refer to that business. This policy explains personal information handling for DMGKit 3, its built-in Kit assistant and Reports/Inspector features, CLIKit (including its standalone distribution), the separate DMGKit Inspector menu bar app, dmgkit.app, and related Fuse Labs purchase and support interactions.

Fuse Labs is responsible for personal information under its control, including information it accesses through purchase platforms. You can contact the person responsible for privacy at support@fuselabssoftware.com or through the Fuse Labs website. Apple, Gumroad, Setapp/MacPaw, and other services described below also handle information under their own policies and, where applicable, their own legal responsibilities.

Our apps primarily process your work on your Mac. This does not mean they never use the internet: notarization, some Apple trust checks, licensing, update checks, optional downloads, and the Setapp framework involve the services explained below. Website analytics is separate from app processing.

2. Information and purposes at a glance

  • Your work, processed locally: imported apps and archives, DMGs, PKGs, inspection results, signing-related settings, Designer content, templates, legal documents, and Kit inputs are used to perform the operations you choose. Local processing does not give Fuse Labs access to those files.
  • Purchase and license information: the customer information available to us through purchase platforms includes name, email address, license information, purchase date, and amount. Gumroad also makes a license activation/“uses” count available. We use relevant records to administer purchases, verify entitlement, manage activations, and address support or misuse issues.
  • Support information: when you email us or use the Fuse Labs contact form, we receive the information you submit, such as your contact details, message, and any information or files you choose to share. We use it to respond and resolve your request. Sending a report to support is a separate action from using local inspection or Kit.
  • Network request information: a service receiving an update check, download, license request, website visit, or Apple service request receives the information necessary to handle that request. Depending on the request, this includes the IP address, user agent, requested resource, and the specific information described in the relevant sections.
  • Website analytics: after you accept analytics, Google Analytics measures visits and button clicks on dmgkit.app. See the website section for information about consent and related data.

We do not sell or rent your personal information. We do not need your private project files, signing passwords, or private keys to provide ordinary customer support. Please do not include secrets in support messages or contact-form submissions.

3. Kit: entirely local AI processing

Kit answers questions about DMGKit and distribution workflows, explains export results, and helps diagnose failures. It processes your conversation, DMGKit’s current session log (including commands, results, status messages, and errors), and the open inspection report entirely on your Mac. Kit does not send your questions, answers, session logs, or inspection data to Fuse Labs or to an external AI service.

You can choose between Apple’s on-device model, provided by macOS through Apple Intelligence on supported systems (macOS 26 or later), and the optional Qwen3-4B-Instruct-2507 model run locally through llama.cpp. Apple’s model is part of macOS and is subject to Apple’s terms and privacy policy; this is an on-device integration.

Downloading Qwen is optional and initiated by you. The approximately 2.5 GB model file is downloaded from Hugging Face, which receives normal download-request information, including your IP address and user agent. This download does not send your Kit conversations or project content to Hugging Face. The downloaded model is stored locally in DMGKit’s Application Support folder. It unloads from memory after the configured inactivity period (two minutes by default); unloading it does not delete the downloaded file.

Kit chats and DMGKit session logs are held in memory only, are not saved to disk by DMGKit, and are discarded when DMGKit quits. Before Kit receives session-log content, DMGKit removes specified secrets, including app-specific passwords, API Key IDs, Issuer IDs, and authorization headers. This redaction applies to the session log; it should not be relied on to remove every possible secret from text you enter yourself, custom instructions, or files you voluntarily send to support.

Your optional custom instructions (up to 1,200 characters) are saved locally in preferences and remain until you change or remove them. They are distinct from the temporary chat. Kit’s generated responses may be inaccurate; do not put credentials in a conversation or custom instructions.

4. Signing, notarization, stapling, and Apple checks

Signing, installer creation, and compression are performed using local tools. When you choose notarization in DMGKit or CLIKit, Apple’s notarytool uploads the full submitted app, DMG, or PKG to Apple’s notary service using your own credentials. Files included in that submission are therefore disclosed to Apple, even though other app processing is local. Review the content of artifacts before submitting them. Apple’s service terms and privacy policy govern Apple’s handling.

Developer ID certificate names and notary Keychain profile names are stored in local preferences. Passwords associated with a notary profile remain in the macOS Keychain and are not read or stored by DMGKit. Signing uses your configured Developer ID certificates, including a Developer ID Installer certificate for signed PKGs.

If you choose App Store Connect API-key authentication, DMGKit copies the selected .p8 private-key file to ~/Library/Application Support/DMGKit/NotaryKeys with owner-only file permissions (0600). Key ID and optional Issuer ID are saved in local preferences. Apple’s notarization tool uses the key for authentication to Apple’s notary service. DMGKit does not send the key to Fuse Labs, Gumroad, Google, or an AI provider.

Stapling retrieves an Apple notarization ticket matching an artifact’s signature. The “Staple Only” workflow does not resubmit the full artifact for notarization and does not use notarization credentials. The request still communicates with Apple. Gatekeeper assessments, stapler checks, and final notarization/status checks may also contact Apple to confirm trust or ticket status as part of macOS behavior.

DMGKit may prepare a working copy of an imported app by removing quarantine attributes, adjusting permissions, or re-signing it. DMG and PKG workflows otherwise remain local except for the Apple submissions and checks described here.

5. Built-in Reports and DMGKit Inspector

The built-in Reports screen, CLIKit inspection commands, and the separate DMGKit Inspector app use local macOS tools to inspect artifacts. Reports can include file size and hashes, signing identities, Developer/Team IDs, bundle identifiers, versions, minimum macOS, architectures, entitlements, notarization and stapling information, and Gatekeeper results. DMGs are mounted read-only for inspection and ejected afterwards.

Inspection content is not uploaded to Fuse Labs. Apple Gatekeeper and stapler checks may contact Apple as described above. The trust score summarizes Apple trust signals; it is not a guarantee that a file is safe or free of malicious content.

The separate DMGKit Inspector app keeps inspection results in memory only and stores its display settings in local preferences under com.ruimiguel.DMGKit-Inspector. Its optional “Open at login” setting uses the macOS login-item service. It checks its own GitHub Gist update feed, separate from DMGKit’s feed. Inspection does not itself collect diagnostic or license records for Fuse Labs.

6. CLIKit configuration, installation, and updates

CLIKit is a free command-line tool that can run from Terminal, SSH, or CI. It can sign, notarize, staple, inspect, verify, and create DMG or PKG installers. It can import DMGKit settings such as Developer ID names, the notary profile name, API-key path and identifiers, and export options. A generated Xcode post-archive action can run CLIKit automatically after an archive; it uses the same processing and Apple service flows.

CLIKit stores configuration locally in ~/.config/clikit/config.json, readable only by the user, and optionally in a project’s clikit.json. It does not save passwords in its configuration; it uses your macOS Keychain notary profile or API-key file. Project configuration, terminal output, and CI output are under your control and may also be retained by your terminal, project, or CI service.

Interactive Terminal sessions check for updates once per day unless you set CLIKIT_NO_UPDATE_CHECK=1. Checks retrieve dmgkit.app/CLIKit/latest.json; an update download retrieves dmgkit.app/CLIKit/CLIKit.dmg. Our website host receives normal request information, including the IP address and user agent. These requests are distinct from consent-based website analytics.

Installation to /usr/local/bin may require an administrator password. You enter it into macOS’s own authorization prompt; DMGKit does not see or store it. CLIKit’s notarization and stapling communicate with Apple as described in this policy.

Designer operations, background text and icon labels, images and stickers, preview settings, template creation, DMG compression, and disk-image building are processed locally. Templates (.dkt) and embedded media are saved where you choose. Designer data and stickers are also stored locally in Application Support. If you choose a cloud-synchronized folder or share a template, the handling by that storage or sharing service is separate from DMGKit’s local processing.

The legal-document editor stores your Terms, Privacy Policy, and EULA texts locally in preferences and ~/Library/Application Support/DMGKit/LegalDocuments. You can include them in a DMG license agreement or PKG license page, including multiple languages. Recipients of an installer can view the legal text you include in it; a full artifact submitted for notarization is sent to Apple.

Legal translation uses Apple’s Translation framework on the Mac. macOS may contact Apple to download required language packs. This does not turn the legal editor into a Fuse Labs cloud translation service.

Sparkle appcast generation runs the local generate_appcast tool using your saved app profiles and Sparkle signing keys in the macOS Keychain. Signing keys stay in your Keychain. Generating an appcast does not itself publish or upload it. This workflow is separate from DMGKit’s own GitHub-based update checks.

8. Preferences, first launch, and notifications

Local preferences remember settings such as window position, the Slide to Start/Start-button choice, the last version whose intro was shown, EULA acceptance, certificate and notary profile names, API-key identifiers, Sparkle app profiles, and security-scoped bookmarks used to access selected apps. These local first-launch and EULA preferences are not an acceptance-reporting service for Fuse Labs.

DMGKit requests macOS notification permission on first launch. Notifications are enabled by default subject to that permission and turn off if it is denied. Optional local notifications can report completion or failure of exports, notarization, status checks, inspections, CLIKit installation, and model downloads. Notification text may contain filenames and results visible to someone who can see your screen or notification history. Manage permission and display options in macOS notification settings.

9. Gumroad licensing and purchase records

The direct version uses Gumroad. License verification sends the license key and product ID to Gumroad’s license-verification endpoint. Activations increment Gumroad’s license “uses” count, which is visible in the seller dashboard. As with other internet requests, Gumroad receives connection/request information.

The direct build stores the license key, activation record, and a randomly generated install ID locally in the macOS Keychain under the service NEPTUN_.license. No additional device or activation identifiers are sent to Fuse Labs as part of this flow. GitHub Gists are used for version information, not a customer license list.

Gumroad handles purchases and payment processing under its privacy policy. The customer purchase information available to Fuse Labs is name, email address, license information, purchase date, and amount, together with the activation count described above. The apps do not need your payment-card details for license verification.

License records are used to administer entitlement and activation limits, respond to purchase/support issues, and address misuse. Licenses may be cancelled for misuse or breach of applicable terms, or at the user’s request. A privacy inquiry, access request, or withdrawal of website analytics consent is not itself a request to cancel a license.

10. Setapp version and its framework

The Setapp version uses Setapp licensing rather than the direct-build Gumroad licensing flow. It includes MacPaw’s Setapp framework, which handles subscription entitlement, displays Setapp release notes, and communicates with the Setapp app and MacPaw’s servers. This includes subscription confirmation and usage reporting for Setapp revenue sharing.

This is an important exception to the absence of developer analytics SDKs described below. Fuse Labs does not control or receive the framework’s underlying per-user data. MacPaw’s Setapp Privacy Notice explains its collection, purposes, retention, and user choices. The direct Gumroad build and CLIKit do not include this framework.

11. DMGKit and Inspector update checks

DMGKit and DMGKit Inspector retrieve version information from JSON files hosted at gist.githubusercontent.com. Inspector has a separate feed. At launch or during an update check, the installed version is compared with the available version so the app can notify you about an update. Compatibility checks limit offered updates to supported macOS versions and architectures.

Automatic DMGKit checks can be disabled in Settings. GitHub receives normal request information such as IP address and user agent. These requests do not upload projects, Kit conversations, or inspection reports. GitHub does not give Fuse Labs per-user records for these feed requests. See GitHub’s privacy statement.

12. Websites, support, cookies, and Google Analytics

We use Namecheap for website hosting and related website/email services, including the Fuse Labs support website and its contact form. Website requests, downloads, CLIKit update requests, and contact-form/email delivery require handling by the relevant hosting and communication infrastructure. Requests expose normal connection information, such as IP address, user agent, and requested resource. Server access logs may be available to Fuse Labs if the host provides them; this is separate from Google Analytics. Namecheap explains its own processing in its privacy policy.

If you use the Fuse Labs contact form or email support@fuselabssoftware.com, your submission is sent to us so we can respond. Do not send private signing keys, passwords, payment-card information, or unnecessary personal information. Our access to messages you send is distinct from the apps’ local processing.

Google Analytics on dmgkit.app is activated only after you accept analytics. It measures visits and button clicks to help us understand website use and improve navigation. Analytics can use cookies or similar browser identifiers and process page URLs, referral information, interaction events, browser/device details, and approximate geographic information. Requests to Google also expose your IP address for handling the request and deriving location information; this does not mean we receive your raw IP address in Analytics reports. Analytics data should not be treated as anonymous merely because it does not include your name.

You can refuse analytics and use the website. Use the Cookie Settings control in the footer to review or withdraw your choice. Withdrawal applies to future analytics processing and does not undo processing already carried out lawfully. Browser controls can remove existing cookies; removal does not itself delete data already held by Google. Necessary handling to deliver requested pages, downloads, or support continues independently of analytics consent.

Google’s privacy policy and information about partner sites describe its handling. Fuse Labs has not set a separate retention period for website analytics. Google Analytics retention is governed by the service’s applicable settings and processing rules; aggregate reports can be retained separately. We do not promise a particular automatic deletion date. You can contact us with an analytics-related privacy request.

The apps do not contain Fuse Labs analytics, tracking, or crash-reporting SDKs and do not send app usage data to the developer. Website analytics, Apple service interactions, licensing/update requests, and the Setapp framework exception described above must be considered separately.

For our Ontario commercial activities, the Canadian Personal Information Protection and Electronic Documents Act (PIPEDA) applies where its scope is met. We explain our purposes and seek meaningful consent where required. Optional analytics requires your acceptance. Choosing a local feature does not amount to consent to unrelated tracking. Accepting an EULA does not replace a separate consent that privacy law requires.

For individuals protected by the EU GDPR or UK GDPR, where applicable, the legal grounds for handling personal information are:

  • Contract or requested pre-contract steps: handling purchases, verifying licenses and activations, and responding to requests needed to provide your product or service.
  • Consent: optional website analytics. You may withdraw it without affecting the lawfulness of earlier processing.
  • Legitimate interests: proportionate security, preventing licensing misuse, resolving non-contractual inquiries, and establishing or defending legal claims, subject to your rights and interests.
  • Legal obligations: records or disclosures required by applicable accounting, tax, privacy, or other laws.

We limit use of information to the described purposes or another purpose permitted by law. You do not need to provide support correspondence or accept analytics to use local app features. Information needed to verify a purchase or license may be necessary to provide licensed functionality. For processing independently carried out by Gumroad or Setapp, their own privacy notices explain the legal grounds they rely on and the rights available through their services. Fuse Labs’ handling of purchase information it can access, support correspondence, and its own website analytics remains covered by this policy and the applicable grounds above.

14. Recipients and international processing

The recipients described in this policy are Apple (notarization, trust checks, and operating-system services), Gumroad (direct purchases and licensing), Setapp/MacPaw (the Setapp distribution), GitHub (update feeds), Hugging Face (the optional model download), Namecheap (hosting and related communications), and Google (consented website analytics). What each receives depends on which distribution, feature, or service you use.

Hosting and communication providers process information to operate services for us. Purchase platforms and Apple or other services you engage can also act independently for their own payment, account, security, or legal purposes. Calling a service a third party does not remove Fuse Labs’ responsibilities for information under its control.

Fuse Labs is based in Canada. Third-party services can process information outside Canada, including in the United States and other countries where they operate. Information processed abroad may be accessible to courts, law enforcement, or public authorities under local law. We do not promise that information remains in Canada or that every provider uses the same country or retention period.

For purchases and licensing through Gumroad, or subscriptions and framework processing through Setapp/MacPaw, consult the relevant platform’s privacy notice for its independently determined legal grounds, international-processing arrangements, transfer safeguards, and privacy-request channels. Those notices apply to the platform’s own processing; they do not replace this policy for information handled by Fuse Labs.

Where EU or UK transfer restrictions apply to information under Fuse Labs’ control, the applicable law requires a valid transfer mechanism. Canada’s adequacy recognition is limited to its applicable scope, including PIPEDA-covered commercial processing; it does not automatically cover onward transfers to every service. The other provider notices linked in this policy explain their own international-processing arrangements. Contact us about information under our control. This policy does not claim that platform distribution alone satisfies every EU or UK privacy requirement.

Personal information may also be disclosed when required by law or necessary and legally permitted to address fraud, misuse, security incidents, or legal claims. This is not an authorization to disclose local project contents that Fuse Labs does not hold.

15. Retention and storage

  • Kit and inspection sessions: Kit conversations and DMGKit session logs are held in memory and discarded when DMGKit quits. The separate Inspector’s results are also memory-only.
  • Local persistent files: downloaded models, imported-app copies, legal documents, Designer data, settings, copied API keys, CLIKit configuration, and Keychain records remain locally until removed or changed. Uninstalling an app does not necessarily remove Application Support, preferences, or Keychain items.
  • Working files: temporary export working files are created in the system temporary folder and deleted afterwards. Exported artifacts, saved templates, original files, and copies you retain or back up are separate.
  • Purchase and licensing records: we retain the records available to us without a fixed retention period or scheduled automatic deletion. They may therefore remain available indefinitely unless you request deletion, subject to the legal limits explained below. You may request deletion at any time. Records necessary for an active license are linked to that entitlement; removing the essential licensing record can prevent continued verification or require cancellation of the license. We will explain the effect before acting on such a request. An unrelated support or analytics request does not automatically cancel your license.
  • Support, hosting, and analytics: Fuse Labs has not established fixed retention periods or a scheduled automatic deletion process for records under its control in these categories. Records we retain may therefore remain until deletion is requested, subject to applicable legal requirements. Providers may apply their own retention settings and deletion processes to records they hold; the absence of a Fuse Labs schedule does not mean that every provider retains every record indefinitely. Google Analytics retention is described in the website section.

Deletion rights have legal limits. Records may need to be retained to meet legal obligations or address an existing dispute or claim. Gumroad, Setapp, and other independent providers may retain their own transaction or service records under their policies and legal duties; Fuse Labs cannot promise to erase every provider’s records. Backups or copies maintained by you or a service may have separate deletion cycles.

16. Removing data from your Mac

Quit DMGKit and DMGKit Inspector before manually removing stored files or preferences so the apps do not write settings back. These actions can remove configuration or working content; keep anything you need first. Local deletion does not erase information already sent to Apple, a purchase platform, or another service.

  • Qwen model: use Settings → Kit → Delete, or remove ~/Library/Application Support/DMGKit/Kit.
  • DMGKit’s copied API key: use the API Key trash button in Notarization settings (“Remove DMGKit’s copy of the key”), or remove the copy in ~/Library/Application Support/DMGKit/NotaryKeys. The in-app control removes the copy and saved path; it leaves the original file you selected untouched. Deleting a copy does not revoke the key with Apple.
  • Other DMGKit content: ~/Library/Application Support/DMGKit includes imported-app copies under ImportedApps, legal texts under LegalDocuments, model files, and copied keys. Designer data is under ~/Library/Application Support/com.ruimiguel.NEPTUN- for the direct build or ~/Library/Application Support/com.ruimiguel.DMGKit-setapp for the Setapp build. Templates and exports saved elsewhere must be removed separately.
  • Preferences: the preference domains are com.ruimiguel.NEPTUN- (direct), com.ruimiguel.DMGKit-setapp (Setapp), and com.ruimiguel.DMGKit-Inspector (Inspector). Removing the relevant domain removes its saved settings. Contact support if you need help.
  • Direct-build licensing: in Keychain Access, search the login Keychain for NEPTUN_.license to find the license, activation, and install-ID items. Removing them deactivates the app on that Mac and may require support to reset activation before reuse. Licenses bought on or after June 12, 2026 allow one activation. Removing local records does not erase the purchase platform’s records.
  • CLIKit: Settings → CLIKit → Remove deletes the installed tool but keeps its settings. Remove ~/.config/clikit and any project-level clikit.json separately to remove those settings.
  • Operating-system services: notification permissions, Inspector’s login item, and Translation Languages can be managed in macOS System Settings. Notary profiles and Sparkle signing keys are created by other tools and may be shared with other workflows. Removing them can break those workflows; losing a Sparkle signing key can prevent signing future updates for an already distributed app.

17. Security and incidents

The documented safeguards include local processing of project and AI content, macOS Keychain storage for relevant credentials and direct-build licensing, owner-only permissions for copied API keys and CLIKit’s user configuration, and session-log secret redaction before Kit processing. These are specific safeguards, rather than a claim that every local file is separately encrypted by DMGKit.

Access to your Mac, user account, project folders, terminal/CI history, backups, notifications, and exported files affects the confidentiality of your information. No storage or transmission method provides an absolute guarantee against unauthorized access or loss.

If a breach involving personal information under our control occurs, applicable law determines our duties to assess it, keep records, report to regulators, and notify affected individuals. Under PIPEDA, breaches creating a real risk of significant harm require reporting and notification, and breach records must be kept for at least two years. Report suspected privacy or credential exposure to support@fuselabssoftware.com without sending the exposed secret itself.

18. Your privacy rights and complaints

Subject to applicable law and limited exceptions, you may ask whether we hold personal information about you, request access and information about its use and disclosure, challenge its accuracy, seek correction, and raise a complaint about our practices. You may withdraw consent where processing depends on it, subject to lawful restrictions and notice of any effect on a service. PIPEDA does not create an unlimited right to erase every transaction record.

For a request, email support@fuselabssoftware.com and identify the information or service involved. We may request proportionate verification to avoid disclosing information to an unauthorized person; do not send passwords or private keys. Under PIPEDA, access requests generally require a response within 30 calendar days, with only legally permitted extensions. We will explain an applicable refusal, restriction, or extension and how to challenge it.

Where EU or UK data-protection law applies, you may also have rights to erasure, restriction, portability, objection to processing based on legitimate interests, withdrawal of consent, and protection concerning solely automated decisions with legal or similarly significant effects. These rights depend on their legal conditions. For GDPR-covered requests, the usual response period is one month, subject to lawful extensions. Kit’s local generation of answers is separate from Fuse Labs’ handling of customer privacy requests.

Contacting us first can help resolve a concern, but you may complain directly to the Office of the Privacy Commissioner of Canada. Where applicable, you may also complain to your EU/EEA supervisory authority or the UK Information Commissioner’s Office. This policy does not waive mandatory rights or require an Ontario-only complaint route.

We cannot retrieve locally held conversations or files that were never sent to us. Use the local controls above for those records. For records independently held by Gumroad, Setapp, Apple, or another provider, you can also use that provider’s privacy request process; we remain responsible for responding about information under our own control.

19. Children’s privacy

Our products and related services are not intended for children under 13. We do not knowingly collect personal information from children under that age. If you believe a child has submitted personal information to us, contact us so we can assess and address it. Where the law requires parental or guardian consent for an older child’s processing, that higher or additional protection still applies; the under-13 statement is not a claim that a 13-year-old can consent in every jurisdiction.

20. Changes to this policy

We may update this policy when features, services, practices, or legal requirements change. The effective date above identifies this version. Material changes will be brought to your attention through an appropriate notice, and we will obtain fresh consent where required before using information for a new purpose that needs it. A revised policy does not itself override an existing consent choice.

21. Contact Fuse Labs

  • Business: Fuse Labs, an Ontario, Canada sole proprietorship.
  • Privacy and support: support@fuselabssoftware.com.
  • Business website and contact form: fuselabssoftware.com.
  • Product website: dmgkit.app.