End User License Agreement

Effective October 21, 2026 · Version 1.3

Important: Read Carefully Before Using This Software

This End User License Agreement (“Agreement”) is a legally binding contract between you (“User,” “you,” or “your”) and buxjr (“Developer,” “we,” “us,” or “our”), governing your use of the Melia Email Client software application (“Software”).

By installing, copying, or otherwise using the Software, you acknowledge that you have read, understood, and agree to be bound by this Agreement. If you do not agree, do not install or use the Software.

1. Definitions

  • “Software” means the Melia Email Client application, including all associated files, libraries, documentation, updates, patches, and copies thereof.
  • “License Key” means the digital credential issued upon purchase that unlocks paid features.
  • “Free Tier” means the version limited to one (1) email account.
  • “Paid Tier” means the version unlocked by a valid License Key permitting multiple email accounts.
  • “Licensing Service” means the remote license validation system operated by the Developer.
  • “User Data” means emails, contacts, credentials, settings, and other data stored or processed by the Software on your device.

2. Grant of License

2.1 License Grant. Subject to this Agreement, the Developer grants you a limited, non-exclusive, non-transferable, non-sublicensable, revocable license to install and use the Software for personal or internal business use.

2.2 Device Limit (Paid Tier). A Paid Tier license permits use on up to five (5) devices owned or controlled by you. Use beyond this limit is not permitted without additional licenses.

2.3 Free Tier. You may use the Software at no cost with one (1) email account configured.

2.4 Paid Tier. Upon payment and receipt of a valid License Key, Paid Tier features are unlocked. The license is perpetual for the version purchased, subject to this Agreement.

2.5 No Ownership. This Agreement grants a license only. No ownership or intellectual property rights are transferred.

3. Acceptable Use and Restrictions

You agree not to:

  • Reverse engineer, decompile, disassemble, or attempt to derive the source code of the Software, except to the extent expressly permitted by this Agreement, an applicable third-party open-source license, or applicable law
  • Circumvent licensing, validation, or security mechanisms
  • Copy, distribute, sublicense, or resell the Software
  • Use the Software to develop a competing product
  • Share or distribute License Keys outside your personal or internal business use
  • Use the Software to send unlawful, abusive, fraudulent, or unsolicited communications (including spam)
  • Use the Software in violation of any applicable law or third-party terms

Open-source components. The Software includes third-party open-source software components that are licensed under their respective open-source licenses. Those components are not licensed to you under this Agreement, and nothing in this Agreement is intended to restrict, limit, or supersede any rights granted to you under the applicable open-source licenses.

To the extent any provision of this Agreement conflicts with an applicable open-source license with respect to an open-source component, the terms of that open-source license control with respect to that component. This includes, where applicable, rights to copy, modify, redistribute, replace, relink, or reverse engineer the Software to the extent necessary to exercise rights granted under the applicable open-source license, including debugging modifications to an open-source component.

A list of open-source components included with the Software, together with their applicable licenses and notices, is available in the Software under Settings → About → Legal and at melia.buxjr.com/open-source.

4. Intellectual Property

The Software and all associated intellectual property rights, excluding third-party components and other materials owned by their respective licensors, are the exclusive property of the Developer.

If you provide feedback, you grant the Developer a perpetual, irrevocable, royalty-free right to use it without restriction.

5. Data Handling and Privacy

5.1 Local Storage. User Data is stored locally on your device in a SQLite database in Melia’s configuration folder (normally ~/.config/melia/). The Developer does not receive your email content.

5.2 Credentials. Credentials are encrypted with a key held in your operating system’s secure keyring (Electron’s safeStorage is used only where no keyring is available). The Developer does not access them.

5.3 Network Activity. The Software may connect to:

  • Email servers you configure (IMAP/SMTP)
  • Address book servers you configure (CardDAV)
  • OAuth providers (Microsoft), when you sign in with OAuth
  • The Licensing Service: on every installation, to check for updates (sending only the product and the installed version); on licensed installations, also to activate and validate the license (Section 6)
  • GitHub, to download an update you choose to install
  • DNS services (for SPF/DKIM/DMARC verification, and to discover server settings when you add an account)
  • Remote content servers named in a message, such as remote images, which load by default and can be blocked in Settings
  • Google’s dictionary servers, to download spell-check dictionaries
  • Features you choose to turn on or use: sender logos (from a brand’s certificate, or a contact’s own website), link previews in compose, and unsubscribe links you click

5.4 No Telemetry. The Software does not collect analytics, usage telemetry, or behavioral tracking data.

5.5 No Advertising. The Software contains no ads and does not sell or share User Data.

5.6 Future Changes. The Developer will not introduce telemetry or data collection features without updating this Agreement.

5.7 User Responsibility. You are solely responsible for securing your device and accounts, and maintaining backups of your data.

For full details, see the Privacy Policy and Privacy Architecture.

6. License Validation

  • Activating a License Key requires a connection to the Licensing Service.
  • After activation, your license is verified on your device using a signed license token. When an internet connection is available, the Software checks in with the Licensing Service approximately every 14 days. If the Licensing Service cannot be reached, the check is skipped and the Software continues to work normally.
  • An activated Paid Tier license does not expire, and does not lose its Paid Tier features, solely because the device has been offline, regardless of how long it was offline. The Developer will not retroactively impose an offline time limit on licenses already purchased.
  • To keep device slots available, the Licensing Service releases the slot of a device it has not heard from in 90 days. When that device reconnects, the Software re-activates it automatically using its existing License Key. If all five of the license’s device slots (Section 2.2) are in use by other devices at that time, the device returns to the Free Tier until a slot is freed and the License Key is entered again.
  • License Keys may be revoked for fraud, chargebacks, abuse, or material violations of this Agreement, subject to Section 12. A revocation normally takes effect when the device next contacts the Licensing Service.

For full details on how licensing works, see Licensing Transparency.

7. Payments and Refunds

  • Paid Tier is a one-time purchase (no subscription)
  • Refund requests may be submitted within thirty (30) days of purchase and are evaluated reasonably at the Developer’s discretion
  • Refunded licenses will be revoked

8. Updates and Support

  • Updates may be provided at the Developer’s discretion
  • No obligation exists to provide updates, maintenance, or support
  • Support, if offered, is provided on a best-effort basis without guarantees

9. Third-Party Services

The Software depends on third-party services (email providers, OAuth providers, DNS systems). The Developer is not responsible for:

  • Service outages
  • API restrictions or changes
  • Account suspensions
  • Data loss caused by third-party systems

10. Disclaimer of Warranties

THE SOFTWARE IS PROVIDED “AS IS” AND “AS AVAILABLE,” WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED.

THE DEVELOPER DISCLAIMS ALL WARRANTIES, INCLUDING BUT NOT LIMITED TO: MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT.

THE DEVELOPER DOES NOT GUARANTEE: UNINTERRUPTED OPERATION, ERROR-FREE PERFORMANCE, SECURITY OR ABSENCE OF VULNERABILITIES, OR DELIVERY, INTEGRITY, OR STORAGE OF EMAIL DATA.

YOU ARE RESPONSIBLE FOR MAINTAINING BACKUPS OF YOUR DATA.

11. Limitation of Liability

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW:

  • THE DEVELOPER SHALL NOT BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES
  • TOTAL LIABILITY SHALL NOT EXCEED THE GREATER OF: THE AMOUNT PAID BY YOU IN THE LAST 12 MONTHS, OR $10 USD

12. Termination

12.1 By User. You may terminate this Agreement at any time by uninstalling the Software.

12.2 By Developer. The Developer may terminate this Agreement if you violate its terms.

12.3 Effect. All rights granted under this Agreement cease upon termination. Sections 4, 10, 11, 13, 14, and 17 survive termination.

12.4 Data. Your data remains on your device after termination. The Software does not delete User Data upon uninstallation.

13. Indemnification

You agree to indemnify and hold harmless the Developer from any claims, damages, or expenses arising from your use or misuse of the Software, or your violation of this Agreement.

14. Governing Law

This Agreement is governed by the laws of the State of South Carolina, United States of America. All disputes arising under this Agreement shall be resolved in the courts located in Lexington County, South Carolina.

15. General Provisions

  • Entire Agreement. This Agreement constitutes the entire agreement between you and the Developer regarding the Software and supersedes all prior agreements.
  • Severability. If any provision is held invalid or unenforceable, the remaining provisions remain in full force and effect.
  • No Waiver. Failure to enforce any provision does not constitute a waiver of that provision.
  • Assignment. The Developer may assign this Agreement. You may not assign your rights or obligations without prior written consent.
  • Force Majeure. The Developer is not liable for failures caused by events beyond reasonable control.
  • Export Compliance. You agree to comply with all applicable export laws and regulations.

16. Contact

buxjr
Email: melia@buxjr.com
Website: melia.buxjr.com

17. Source Code Release Upon Abandonment

The Developer commits that, if the Software is discontinued, the source code for the most recent shipped version will be released to the public under a permissive open-source license.

17.1 Triggering Conditions. “Discontinued” means either:

  • No public release of the Software for twelve (12) consecutive months; or
  • Formal dissolution, sale, or wind-down of buxjr’s commercial operation of the Software.

17.2 Release Window. The Developer will publish the source code within ninety (90) days of either triggering condition being met.

17.3 License. The released source code will be made available under either the MIT License or the Apache License 2.0, at the Developer’s election.

17.4 Scope. The source-code release obligation applies to the Software itself. It does not extend to third-party services, API credentials, customer data, signing keys, or operational infrastructure. Third-party components remain subject to their respective licenses.

17.5 Survival. This Section 17 survives termination of any individual user’s license. The obligation runs to all users of the Software in the aggregate.

18. Acknowledgment

By installing or using the Software, you acknowledge that you have read, understood, and agree to be bound by this Agreement.

Changes to this Agreement

  • Version 1.3, October 21, 2026: Section 6 rewritten. A Paid Tier license no longer has any offline time limit; the 90-day device-slot release and automatic re-activation are described; revocation reasons and timing are stated. Section 5.3 corrected to list every connection the Software makes, including the update check every installation performs; remote images load by default, which the previous text did not say.