Privacy Policy
Last updated: November 8, 2026
NTFS Kit is a local macOS application for managing NTFS volumes. This policy describes what it stores, when it uses the network, and what it never reads.
1. Summary
- There is no NTFS Kit account, sign-in, subscription or license key.
- Volume names, capacity, device identifiers and mount state are read from
diskutilon your Mac. - File contents and file names inside NTFS volumes are not read by the application and are never written to logs.
- There is no analytics SDK, advertising SDK or crash-reporting service.
2. Data stored on your Mac
| Data | Location | Purpose |
|---|---|---|
| Settings | ~/Library/Application Support/NTFS Kit/settings.json | Mount behavior, appearance, notifications and update preferences |
| Logs | ~/Library/Logs/NTFS Kit/ | Mount, verification, repair, format and system events, rotated by size and count |
| Diagnostics archive | Created only when you export it | Logs and system information for troubleshooting |
Uninstalling the app does not delete these directories. Remove them manually for a full wipe.
3. What is never collected
- Contents or names of files stored on NTFS volumes.
- Disk serial numbers as analytics. Device nodes and UUIDs are used locally to keep operations bound to the volume you selected.
- Passwords, Homebrew tokens or administrator credentials. Installation uses the system authorization prompt or the configured Homebrew command; secrets are not copied into logs.
- Usage events. There is no event pipeline.
4. Network connections
NTFS Kit opens a network connection only for an action you trigger.
| Connection | Trigger | What is sent |
|---|---|---|
| macFUSE release check | You open the driver installer | A request for the official release metadata and DMG |
| Homebrew package install | You confirm the NTFS-3G installation | The package name and the mirror you selected, through the system brew command |
| Update check | Only when an update source is configured and you enable checks | Current version and platform; no volume data |
| Links you open | You press a documentation or project link | Handled by your browser, not by the app |
The app does not upload volume names, capacities, paths or logs. Driver downloads go to the official project or the Homebrew mirror you chose for that installation.
5. Logs and diagnostics
- Logs use structured keys and never include NTFS file contents or file names.
- Volume names, device nodes, UUIDs and command outcomes may appear because they are needed to diagnose a failed mount or repair.
- Command output is treated as log material, not as the only user-facing error. The UI shows a stable error code and a readable message.
- A diagnostics export is a ZIP of logs and environment information. Review it before sharing; it can contain local paths and volume names.
6. Third-party components
macFUSE and NTFS-3G are separate projects. Their installers, system extensions, network behavior and licenses are governed by their own terms. The app links to official sources and does not silently bundle or modify them.
7. Your controls
- Disable automatic update checks in Settings.
- Clear logs or export a diagnostics archive when you choose.
- Remove the settings and log directories to erase local state.
- Build from source if you want to inspect every command and network call.
8. Contact
Use the project issue tracker or the contact link in the footer. Do not send diagnostics that contain information you are not allowed to share.