Privacy Policy

1. Definitions

For purposes of this Privacy Policy:

• Application means the mTarsier desktop software.
• Device means any computer or system capable of running the Application, including Windows, macOS, and Linux devices.
• Personal Data means information that identifies, relates to, describes, or could reasonably be linked to an individual.
• Service means the functionality provided by the mTarsier desktop application.
• Usage Data means technical or diagnostic information generated through use of the Application, where applicable.
• MCP means Model Context Protocol.
• Open Source means software whose source code is publicly available for review, use, and modification under the applicable license.
• You means the individual or entity using the Application.

2. Information We Collect

2.1 Information We Do Not Collect

mTarsier is designed to operate locally and with minimal data handling. We do not collect or store:

• Personal identification information
• MCP server configurations created or managed by you
• Analytics or telemetry about how you use the Application
• Browsing behavior or usage patterns
• IP addresses for our own tracking purposes
• Device identifiers for our own tracking purposes
• Data from your local machine for our own access or storage

2.2 Limited Technical Interactions

In limited cases, the Application may interact with third-party services as part of features you choose to use:

• Update Checks: If the Application includes update-check functionality and you choose to use it, limited technical information such as the current application version may be sent directly to GitHub or another release host to determine whether an update is available.
• Crash Reports: If crash reporting is offered and you affirmatively opt in, diagnostic information related to the error may be transmitted. We intend for such reports to contain technical debugging data only and not intentionally include personal information.
• Marketplace or Repository Downloads: If you install MCP servers or related resources from public repositories, your device connects directly to those third-party hosting services, such as GitHub.

2.3 Local Storage

mTarsier stores application-related data locally on your Device. This may include:

• Preferences and settings
• Backup files for your MCP configurations
• Cached marketplace or repository metadata
• Local application logs

This information remains on your Device unless you choose to export, share, sync, or otherwise transmit it yourself.

3. How Information Is Used

Because mTarsier primarily operates locally, most functionality does not require us to receive or process your data. The Application may use locally stored information to:

• Manage MCP server configurations on your Device
• Create and restore local backups
• Support terminal or CLI-based operations
• Detect compatible AI clients installed on your system
• Cache public repository or marketplace data for performance and offline convenience

Where the Application connects to third-party services at your direction, those interactions are used only to complete the requested function, such as checking for updates or downloading a package.

4. Third-Party Services

The Application may rely on third-party services that operate independently from us. These may include:

• GitHub, for software releases, repository access, and package downloads
• Public MCP server repositories, when you choose to install or access server packages

Your use of those services is subject to their own terms and privacy policies. We are not responsible for the privacy practices of third-party platforms.

5. Data Security

Because mTarsier stores data locally, the security of that data depends in significant part on the security of your Device and environment.

You are responsible for maintaining appropriate safeguards, including:

• Keeping your operating system up to date
• Using current endpoint protection or security software where appropriate
• Securing backup files and local configuration data
• Limiting unauthorized access to your Device

mTarsier does not intentionally transmit your local configuration data to us. As an open-source project, the Application's codebase can be publicly reviewed to evaluate its behavior and security design.

6. Your Rights and Choices

Because we do not generally collect or store personal data ourselves, many traditional data-access or deletion rights may not apply in the usual way. However, you may at any time:

• Use the Application without enabling optional network-based features
• Disable update checks, if supported
• Decline optional crash reporting, if offered
• Review the source code to assess privacy-related behavior
• Delete the Application and remove its locally stored data from your Device
• Modify or fork the software in accordance with its license

If in the future our data practices materially change, we will update this Privacy Policy accordingly.

7. Children's Privacy

mTarsier is not directed to children and is intended primarily for developers, technical users, and similar audiences. We do not knowingly collect personal information from children.

8. Open-Source Transparency

mTarsier is developed as an open-source project. We value transparency and verifiability. Our commitment includes:

• Making the source code publicly available
• Allowing users and contributors to inspect and audit the codebase
• Avoiding hidden telemetry or undisclosed tracking mechanisms
• Encouraging community review and contribution

9. Changes to This Privacy Policy

We may update this Privacy Policy from time to time to reflect changes in the Application, legal obligations, or operational practices.

When we make changes, we will revise the "Last Updated" date above. Material updates may also be described in release notes or the project repository.

10. Contact

For questions about this Privacy Policy or the Application, you may contact the project through:

• GitHub Issues: github.com/mcp360/mTarsier/issues
• X (Twitter): @0fficialRohit and @rege_dev

Project: mTarsier
License: MIT License