Terms of Service

1. Definitions

• "SDK" means the Jingle Plug-In software development kit provided to Developer.
• "Host App" means the Developer's mobile application that integrates the plug-in.
• "End User" means an individual who uses the Host App with the plug-in activated.
• "Jingle Network" means the telecommunications infrastructure operated by Minutes Network FZ-LLC.
• "Revenue Share" means the percentage of call termination revenue allocated to the Developer.
• "Integration Agreement" means the written agreement signed between the Company and the Developer that governs the commercial terms of the partnership, including the agreed Revenue Share percentage and the applications licensed to use the plug-in.

2. Acceptance and Changes to These Terms

• By accessing or using the Service, you accept these Terms as they apply at the time of use. The "Last updated" date at the top of this page records the current revision.
• We may update these Terms from time to time, for example to reflect changes in law, regulation, our services, or business practices.
• We will give at least 30 days' notice of material changes by email and/or via the Developer Dashboard before they take effect.
• Continued use of the Service after a change takes effect constitutes acceptance of the updated Terms. If you do not agree to a change, you must stop using the Service and may terminate in accordance with Section 16.
• Material changes to Revenue Share terms require mutual written agreement and cannot be imposed unilaterally through an update to these Terms.

3. Eligibility and Business Use

• The Service is offered solely to businesses and professional app developers for business purposes. It is not offered to, or intended for use by, consumers.
• By using the Service you confirm that you are at least 18 years of age, that you are acting in the course of a business, and that you have full authority to bind the business or legal entity on whose behalf you act.
• You must not use the Service where doing so is prohibited by applicable law, regulation, or sanctions.

4. Service Description

The Jingle Plug-In enables Host Apps to generate revenue by participating in the Jingle Network's call termination service. When an international call is routed and terminated through an End User's device - only after that End User has given explicit, informed consent (see Section 6) and while a call is being handled - via the Jingle Network, termination revenue is generated and shared between the Company and the Developer. The Jingle Plug-In supports multiple call delivery modes: foreground delivery (app in active use), background delivery (app backgrounded, maintained by an Android foreground service whose persistent notification is visible to the user), and wake-on-demand delivery (a UDP wake path, with Firebase Cloud Messaging as a fallback, when the app is closed).

5. Integration Requirements

Developer agrees to:

• Integrate the Plug-In in accordance with our technical documentation
• Obtain clear and informed End User consent before activating Jingle functionality
• Disclose Jingle's data practices in the Host App's privacy policy
• Accurately declare SDK permissions and data collection in app store listings
• Not modify, reverse-engineer, or decompile the SDK
• Keep the plug-in at the current supported version, updating within 30 days of a new release (the 30-day update window in the Integration Agreement)

6. End User Consent

Developer MUST obtain explicit, informed consent from End Users before activating Jingle. The consent flow must include a prominent disclosure screen presented before any permission request that clearly explains:

• The user-facing voice feature (e.g. voice search, voice messages, call overlay) and its purpose
• That Jingle delivers international calls to the user's device, which the user can answer like any normal incoming call
• What data is collected (phone number, pseudonymised device token, country / region (country-level, from the verified phone number - no GPS), network state, audio processed ephemerally and never stored, call metadata, anonymous session identifiers)
• That the service generates revenue for the app
• How the End User can disable Jingle independently in Settings without losing the voice feature

Pre-checked boxes, hidden consent, or bundled consent with unrelated permissions are not acceptable.

7. Revenue Share and Payment Terms

• Revenue Share percentages are agreed in the signed Integration Agreement (typically 50%).
• Revenue is calculated based on the per-minute revenue rate multiplied by the total number of minutes of successfully terminated calls through the Jingle Network.
• Revenue reports are available in real-time via the Developer Dashboard, and the Company provides monthly revenue statements detailing call volumes, durations, termination rates, and the calculated Revenue Share.
• Payments are made monthly, by wire transfer to the bank account specified by Developer, within 30 calendar days of the end of each calendar month.
• Minimum payment threshold: £100 (or USD equivalent). Amounts below this threshold roll over and carry forward to the following month(s) until the threshold is reached.
• Company reserves the right to withhold payment if fraud or Terms violations are suspected, pending investigation. Revenue attributable to artificial or fraudulent traffic is not payable.

Payment terms summarised on this website are for information; the signed Integration Agreement sets out the definitive payment terms that apply between the parties.

8. Revenue Expectations

Jingle is built to generate real revenue for partners, and our economics only work when yours do. Because every app and audience is different, the revenue figures, calculators and worked examples on this website and in partner materials are illustrations of how the model works, based on stated assumptions - not predictions for your specific app.

• Your results will depend on factors including the size and geography of your user base, opt-in rates, device and network availability, call routing demand, and prevailing termination rates - some of which are outside either party's control.
• For that reason, the Company does not promise, represent, or warrant any particular level of revenue, earnings, opt-in rate, call volume, or other outcome, and illustrative figures should not be the basis of your decision to integrate the plug-in or enter into an Integration Agreement - the best foundation is a tailored estimate from our team and your own commercial assessment.

Nothing on this website constitutes financial, investment, or professional advice.

9. Acceptable Use and Compliance

Developer shall at all times:

• Comply with all applicable laws and regulations, including telecommunications, consumer protection, and data protection laws
• Comply with Google Play Developer Program policies, including prominent disclosure and Data Safety declaration requirements
• Obtain and maintain valid End User consent as described in Section 6 before activating Jingle functionality

Developer shall not:

• Generate artificial or fraudulent call traffic
• Activate Jingle without valid End User consent
• Use the plug-in in apps directed at children under 13
• Interfere with, disrupt, or overload the Jingle Network
• Sub-license, resell, or redistribute the SDK
• Use the plug-in for any unlawful purpose or in violation of telecommunications regulations
• Misrepresent the nature of the Jingle service to End Users

10. Intellectual Property

• The SDK, the Jingle Network, and all related technology, trademarks, and documentation are and remain the exclusive property of Minutes Network FZ-LLC. Nothing in these Terms transfers any ownership of intellectual property rights to Developer.
• Developer is granted a limited, non-exclusive, non-transferable, revocable licence to use the plug-in solely for integration with the Host App in accordance with the Company's technical documentation and these Terms. The licence terminates automatically when these Terms or the Integration Agreement terminate.
• Developer retains all rights in the Host App and its content.
• Any use of either party's name, logo, or trademarks to promote the integration requires prior written approval, as set out in the Integration Agreement.

11. Data Protection

Both parties agree to comply with applicable data protection laws including the UK GDPR and Data Protection Act 2018. A separate Data Processing Agreement (DPA) governs the processing of End User data and is incorporated by reference into these Terms. In respect of End User personal data, Developer acts as data controller and the Company acts as data processor, as set out in the DPA. In respect of partner and website data, the Company acts as data controller, as described in our Privacy Policy.

12. Warranties and Disclaimers

The Service is provided on an "as is" and "as available" basis. To the fullest extent permitted by law, the Company excludes all warranties, conditions, representations, and other terms, whether express or implied (including any implied terms of satisfactory quality, fitness for a particular purpose, and non-infringement), except for any express warranties set out in a signed Integration Agreement. While we strive for high availability and call quality, we do not warrant:

• Uninterrupted, error-free, or secure service availability
• Specific call success rates or revenue amounts
• Compatibility with all devices or Android versions

Operational and performance metrics published elsewhere on this website are descriptive only and do not form part of any warranty or service commitment under these Terms. Revenue projections provided during sales discussions are estimates only and not guarantees (see Section 8).

13. Limitation of Liability

To the maximum extent permitted by law: (a) neither party shall be liable for any indirect, incidental, special, consequential, or punitive losses, or for any loss of profits, revenue, business, anticipated savings, goodwill, or data, even if advised of the possibility of such losses; and (b) the Company's total aggregate liability arising out of or in connection with these Terms shall not exceed the total Revenue Share paid to Developer in the 12 months preceding the event giving rise to the claim.

Nothing in these Terms excludes or limits either party's liability for death or personal injury caused by its negligence, for fraud or fraudulent misrepresentation, or for any other liability that cannot be excluded or limited under the laws of the United Arab Emirates.

14. Indemnification

Developer agrees to indemnify, defend, and hold harmless the Company, its officers, employees, and agents from and against all claims, losses, damages, liabilities, costs, and expenses (including reasonable legal fees) arising from: (a) the Host App, its content, and its operation; (b) Developer's breach of these Terms or of applicable law; (c) Developer's failure to obtain valid End User consent or to comply with data protection laws; (d) the Host App's violation of app store policies, including Google Play policies; (e) any claim that the Host App or Developer's content infringes third-party rights.

Under a signed Integration Agreement, the Company indemnifies the Developer against third-party claims that the plug-in infringes intellectual property rights.

15. Suspension

The Company may suspend or restrict Developer's access to the plug-in, API keys, Developer Dashboard, or any part of the Service, with immediate effect, where it reasonably suspects:

• Artificial or fraudulent call traffic
• Breach of the acceptable use or End User consent requirements in these Terms
• Violation of app store policies (including Google Play policies) that creates risk for the Company, the Jingle Network, or End Users
• A security threat to the Service or the Jingle Network
• That suspension is required by law, regulation, or a carrier interconnection

The Company will use reasonable efforts to notify Developer of any suspension and to restore access once the issue is resolved. Legitimately accrued Revenue Share remains payable in accordance with Section 7; revenue attributable to artificial or fraudulent traffic is not payable.

16. Term and Termination

• These Terms remain in effect until terminated by either party.
• Either party may terminate with 60 days' written notice.
• Either party may terminate immediately if the other materially breaches these Terms and fails to cure the breach within 30 days of written notice.
• Company may terminate immediately, without a cure period, in cases of fraud, artificial traffic generation, or serious or repeated abuse of the Service or app store policies.
• Upon termination, Developer must remove the plug-in from the Host App within 30 days.
• Accrued Revenue Share up to the termination date will be paid within 60 days of termination.
• Provisions that by their nature should survive termination (including intellectual property, limitation of liability, indemnification, and governing law) survive termination.

17. AI Assistant and Website Content

This website includes an AI-powered chat assistant. Responses generated by the assistant are produced automatically, are provided for general information only, and may contain errors or omissions. They do not constitute legal, financial, or professional advice, a contractual offer, or a binding representation by the Company, and you should not rely on them when making commercial decisions. Only a signed Integration Agreement creates a binding commercial relationship between the Company and a Developer. For authoritative answers, contact partners@jingleplugin.com.

18. General

• Force majeure. Neither party is liable for any delay or failure to perform caused by events beyond its reasonable control, including carrier or network outages, acts of God, war, civil unrest, or government action.
• Severability. If any provision of these Terms is held invalid or unenforceable, the remaining provisions remain in full force and effect.
• Entire agreement. These Terms, together with the documents referred to in them (including the Privacy Policy and DPA), constitute the entire agreement between the parties in relation to use of the Service in the absence of a signed Integration Agreement. Where a signed Integration Agreement exists, it prevails to the extent of any conflict. Neither party relies on any statement not set out in these Terms or a signed Integration Agreement, save that nothing in this clause limits liability for fraud.
• Assignment. Developer may not assign or transfer these Terms without the Company's prior written consent. The Company may assign these Terms to an affiliate or a successor in business.
• No waiver. A failure or delay by either party to enforce any provision of these Terms is not a waiver of that provision or of any other right.
• Third-party rights. A person who is not a party to these Terms has no rights under the Contracts (Rights of Third Parties) Act 1999 to enforce any provision of these Terms.

19. Governing Law and Disputes

These Terms, and any dispute or claim arising out of or in connection with them (including non-contractual disputes or claims), are governed by the laws of the United Arab Emirates. Any disputes shall be resolved through good faith negotiation, followed by mediation, and if necessary, the exclusive jurisdiction of the courts of Ras Al Khaimah, United Arab Emirates.