AppJars™ Subscription & Service Terms

Version 1.0 — effective 2026-01-01

These Subscription & Service Terms (the “Service Terms”) govern the commercial relationship between Flowing Code LLC (“AppJars”, “we”, “us”) and subscribers (the “Customer”, “you”) who purchase a subscription to AppJars software components through any of AppJars’ authorized sales channels.

The AppJars software is developed by Flowing Code S.A. (Argentina). Flowing Code LLC is the provider of the commercial service and your contracting party under these Terms.

These Service Terms complement, and do not modify or replace, the AppJars Software License Agreement (the “License Agreement”) that ships with each AppJars JAR and is also published at https://appjars.com/legal/license/v1. The License Agreement governs the license to use the Software; these Service Terms govern subscription duration, fees, support entitlements, and other commercial matters.

In the event of a conflict between these Service Terms and the License Agreement on a matter of license rights or restrictions, the License Agreement controls. In the event of a conflict on a matter of subscription duration, fees, support, or other commercial matters, these Service Terms control.

1. Definitions

Capitalized terms used in these Service Terms have the meaning given to them in the License Agreement. Additional definitions:

“Subscription Tier” means the level of subscription purchased by Customer, namely Core, Startup, or Enterprise.

“Subscription Term” means the period of one (1) year commencing on the Purchase Date.

“Customer Portal” means the web portal at https://customers.flowingcode.com through which Customer manages its subscription, accesses support resources, and reviews and accepts updates to these Service Terms.

“Support Hours” means hours of human support provided by AppJars personnel as set forth in Section 4.

2. Subscription Tiers

AppJars offers three Subscription Tiers, each available per Component or as a bundle covering all Components:

Core. Includes the Commercial License under the License Agreement for the licensed Component(s). Does not include human support, the AI documentation assistant, or issue escalation.

Startup. Includes everything in Core, plus access to the Customer Portal (including its AI documentation assistant), plus ten (10) Support Hours per Subscription Term, usable for integration assistance and similar matters (see Section 4).

Enterprise. Includes everything in Startup, plus issue escalation (queue precedence for a bug report, on the terms and with the limits set out in Section 4.6), plus a total of eighty (80) Support Hours per Subscription Term.

The price of each Subscription Tier and Component is published at https://appjars.com/pricing and is set at the time of purchase. The specific Subscription Tier and Component(s) purchased by Customer are recorded in Customer’s order confirmation and in the Customer Portal.

3. Subscription Term, License Keys, and Updates

3.1 Subscription Term

Each subscription is granted for one (1) year commencing on the Purchase Date.

3.2 License Keys

Upon completion of the purchase, AppJars will deliver one or more License Keys to the email address provided at checkout. Each License Key covers one Component for one Permitted Application. License Keys are bound to the Customer name and Permitted Application identified at the time of purchase and are subject to the License Agreement (in particular, Sections 4 and 6(d) regarding transferability and end-user restrictions).

3.3 Updates during the Subscription Term

During the Subscription Term, Customer is entitled to receive and use all updates, releases, and bug fixes for the licensed Component(s) issued during that period.

3.4 Perpetual use of the last covered release

Upon expiration of a Subscription Term, Customer’s Commercial License under the License Agreement remains perpetual with respect to the last release of each licensed Component that was issued during the active Subscription Term, in accordance with Section 5 of the License Agreement. Releases issued after the Subscription Term will not validate against Customer’s License Keys.

3.5 Renewal and auto-renewal

Subscriptions renew automatically at the end of each Subscription Term unless disabled by Customer through the Customer Portal at any time before the renewal date. Renewal fees are charged at the then-current price published at https://appjars.com/pricing. AppJars will send Customer a renewal notice email at least thirty (30) days prior to each renewal date.

Disabling auto-renewal does not cancel the current Subscription Term; Customer retains its entitlements through the end of the active Subscription Term.

4. Support

4.1 Support Hours

For Startup and Enterprise tiers, AppJars provides the number of Support Hours specified in Section 2 per Subscription Term. Support Hours are consumed in fifteen (15) minute increments and may be used for:

• investigation of suspected defects in a licensed Component,
• guidance on integrating a licensed Component into a Permitted Application,
• clarification of documentation, and
• any other matter directly related to the use of a licensed Component.

4.2 Out of scope

Support Hours do not cover:

• custom development, feature work, or design services,
• training on Java, Maven, or other third-party technologies not provided by AppJars,
• review or debugging of Customer code that does not invoke an AppJars Component, or
• any matter unrelated to a licensed Component.

4.3 Response time

AppJars uses commercially reasonable efforts to acknowledge support requests within one (1) business day for Startup and within four (4) business hours for Enterprise. Response time is not the same as resolution time; resolution depends on the nature of the issue and may require engineering review under Section 4.6.

4.4 Business hours

Support is provided during AppJars’ published business hours. Outside of those hours, the Customer Portal and its AI documentation assistant remain available 24/7 for Startup and Enterprise tiers.

4.5 Carryover and additional hours

Unused Support Hours expire at the end of the Subscription Term and do not carry over. Customer may purchase additional Support Hours at any time through the Customer Portal at the rate published at https://appjars.com/pricing. Additional hours purchased mid-term expire at the end of the then-current Subscription Term.

4.6 Issue escalation (Enterprise only)

Issue escalation is available to Customers on the Enterprise tier only. It is not available on the Core or Startup tiers and cannot be purchased separately.

4.6.1 Scope. Escalation applies to bug reports only, that is, to a report that a licensed Component does not behave as documented. Feature requests are not eligible for escalation, and neither is any other matter that is not a suspected defect in a licensed Component (including custom development, integration assistance, and questions answered under Sections 4.1 and 4.2). A request to escalate an ineligible item does not occupy the escalation slot described in Section 4.6.2.

4.6.2 Quota. Each License Key carries one (1) concurrent escalation. The quota attaches to the License Key: it is not a per-Permitted-Application limit, it is not a per-Customer-account limit, and it is not an annual allowance. There is no limit on the number of escalations Customer may request during a Subscription Term, provided that no more than one escalation per License Key is active at any given time.

4.6.3 How an escalation is requested. Escalation is requested exclusively through the Customer Portal, by opening a ticket of the dedicated escalation type. Escalation is never requested on GitHub: a comment on a public issue, a reaction, or a mention of AppJars does not create an escalation and has no effect on the fix queue. AppJars confirms in the escalation ticket whether the escalation has been accepted and the slot taken.

4.6.4 Public effect. Where an escalation is accepted, AppJars applies the Prioritized label to the corresponding public issue in the AppJars public issue tracker. That label is the only public effect of an escalation. The label does not identify the Customer that requested the escalation, and AppJars does not disclose publicly which Customer escalated an issue.

4.6.5 What escalation grants. Escalation grants queue position, and nothing else: the escalated bug report takes precedence in AppJars’ fix queue over reports that are not escalated. Escalation does not create a service level, a committed timeframe, or any guarantee that the reported bug will be fixed. AppJars may propose a workaround instead of a code fix. The acknowledgement times in Section 4.3 apply to the escalation ticket itself and not to the resolution of the underlying defect.

4.6.6 When an escalation is resolved. An escalation is resolved when the fix for the reported defect is included in a released version of the affected Component that Customer is able to verify and accept. A fix that is complete in AppJars’ source code but not yet published in a release does not resolve the escalation and does not free the escalation slot.

4.6.7 Holding and release of the slot. The escalation slot remains occupied until AppJars closes the escalation ticket. Customer cannot withdraw, transfer, or replace an active escalation: it cannot be moved to a different issue, reassigned to a different License Key, or transferred to another Customer. AppJars closes the escalation ticket, and the slot becomes available again, in the following cases:

1. the fix has been released and accepted by Customer as described in Section 4.6.6;
2. AppJars decides not to fix the reported issue, in which case AppJars informs Customer of that decision and of the reasons for it; or
3. the reported issue is already under escalation by another Customer, in which case AppJars informs Customer and closes the escalation ticket without the escalation consuming Customer’s slot.

4.6.8 Regressions. If a released fix regresses and the issue is reopened, the escalation is reinstated and consumes Customer’s escalation slot again, on the same terms as the original escalation.

5. Fees, Refunds, and Cancellation

5.1 Fees and taxes

All fees are stated in U.S. Dollars and are exclusive of applicable taxes, which Customer is responsible for paying. Where AppJars is required by applicable law to collect and remit taxes, those amounts will be added to the invoice at checkout.

5.2 Non-refundable

Subscription fees are non-refundable. AppJars does not offer pro-rated refunds for unused time, downgrades during a Subscription Term, or partial use of Support Hours.

5.3 No cancellation of issued License Keys

Once a License Key has been issued to Customer, the License Key remains valid for the duration of the Subscription Term and entitles Customer to perpetual use of the last release of the licensed Component(s) issued during that term, in accordance with the License Agreement. Customer may disable auto-renewal as described in Section 3.5 to prevent further charges, but cannot revoke or shorten an issued License Key.

5.4 Statutory rights

The foregoing applies to the maximum extent permitted by applicable law. Customers in jurisdictions whose mandatory law grants a non-waivable cooling-off, withdrawal, or refund right (such as certain consumer protections in the European Union or specific U.S. states) retain those rights notwithstanding the foregoing. Customer must invoke any such right within the period and through the procedure set by applicable law by contacting AppJars at the email address published at https://appjars.com/contact.

5.5 Chargebacks

A chargeback initiated by Customer in respect of a non-refundable subscription fee, where Customer has no statutory right of refund and has not first contacted AppJars in good faith to resolve the underlying dispute, may be treated by AppJars as a material breach of these Service Terms and the License Agreement. AppJars may, in such circumstances, suspend Customer’s access to the Customer Portal and pursue any other remedies available at law.

6. Acceptance and Updates

6.1 Initial acceptance

Customer accepts these Service Terms and the License Agreement by checking the corresponding box at the AppJars checkout. The checkout record (or equivalent record at any other authorized sales channel) is conclusive evidence of acceptance.

6.2 Updates to these Service Terms

AppJars may update these Service Terms from time to time. Material changes apply only to new subscriptions and to renewals of existing subscriptions, not retroactively to the active Subscription Term. AppJars will notify Customer of material changes by email and through the Customer Portal at least thirty (30) days prior to the change taking effect for renewals.

6.3 Re-acceptance

Where applicable law or AppJars’ policy requires re-acceptance of materially-updated Service Terms, AppJars will gate access to the Customer Portal at the next login until Customer accepts the updated Service Terms. Non-material changes (clarifications, formatting, contact details) take effect on publication and do not require re-acceptance.

6.4 Versioning

A historical archive of these Service Terms is maintained at https://appjars.com/legal/service-terms/archive. Customers may always identify which version of these Service Terms applied to a particular purchase by reference to the Purchase Date and the archive.

7. Customer Portal Access

7.1 Account

Customer’s access to the Customer Portal is created at the time of first purchase using the email address provided at checkout. Customer is responsible for maintaining the confidentiality of its Customer Portal credentials and for all activity under its account.

7.2 Suspension

AppJars may suspend Customer Portal access for material breach of these Service Terms or the License Agreement, including non-payment of fees, fraudulent chargebacks, abuse of support resources, or violation of the License Agreement. Suspension of Customer Portal access does not invalidate already-issued License Keys; the perpetual rights described in Section 3.4 are preserved.

8. Limitation of Liability

The limitations of liability set forth in Section 8 of the License Agreement apply to AppJars’ obligations under these Service Terms in the same manner and to the same extent. For the avoidance of doubt, AppJars' total aggregate liability arising out of or relating to these Service Terms and the License Agreement combined is limited as set forth in Section 8 of the License Agreement, subject to the carve-outs stated therein.

9. Governing Law

These Service Terms are governed by the laws of the State of Florida, United States, without regard to its conflict of law principles, consistent with Section 10 of the License Agreement. Any legal action or proceeding arising under these Service Terms will be brought exclusively in the state or federal courts located in Miami-Dade County, Florida.

10. Relationship to the License Agreement

These Service Terms are a complement to, and not a replacement of, the AppJars Software License Agreement. The License Agreement governs the rights to use the Software (the “what you can do”); these Service Terms govern the commercial relationship (the “what you get and what you pay”). In any conflict between these Service Terms and the License Agreement on a matter of license rights or restrictions, the License Agreement controls. In any conflict on a matter of subscription duration, fees, support entitlements, or other commercial matters, these Service Terms control.

11. Contact

Questions about these Service Terms can be sent to the email address published at https://appjars.com/contact.

Copyright © Flowing Code S.A. All rights reserved.