Terms of Service
Effective date: 2026-03-18 Last updated: 2026-03-18
License
mxr is free and open-source software, dual-licensed under the MIT License and Apache License 2.0, at your option. You may use, modify, and distribute mxr in accordance with either license.
No Warranty
mxr is provided “as is”, without warranty of any kind, express or implied, including but not limited to the warranties of merchantability, fitness for a particular purpose, and noninfringement. The authors and contributors are not liable for any claim, damages, or other liability arising from the use of this software.
No Guarantee of Availability or Support
mxr is a community-driven open-source project. There is no service level agreement (SLA), no guaranteed response time for issues, and no obligation to fix bugs or add features. Support is provided on a best-effort basis by the community.
Email and Data Risks
You acknowledge that:
- Data loss: mxr stores email data locally. Hardware failure, accidental deletion, or software bugs could result in loss of local email data. mxr is not a backup solution.
- Email delivery: mxr relies on third-party services (Gmail API, IMAP, SMTP) for sending and receiving email. Delivery failures, delays, or errors caused by these services are outside mxr’s control.
- Account access: OAuth tokens can expire or be revoked. mxr is not responsible for loss of access to your email accounts.
Third-Party Service Compliance
When using mxr with Gmail or other email providers, you are responsible for complying with those providers’ terms of service:
mxr does not modify or circumvent any provider’s terms.
OAuth Credentials
If you use the bundled OAuth client ID, you agree to use it solely for personal email access through mxr. Abuse of the bundled credentials (automated scraping, bulk operations beyond normal email use, or redistribution of the credentials for other applications) may result in Google revoking access for all users.
If you provide your own OAuth credentials (BYOC), you are solely responsible for their management, security, and compliance with Google’s policies.
Changes to These Terms
These terms may be updated as the project evolves. Changes are tracked in the project’s Git history. Continued use of mxr after changes constitutes acceptance of the updated terms.
Contact
For questions about these terms, open an issue on the GitHub repository.