General
Jingle Plug-In is a lightweight (3-10MB) Android plug-in from Minutes Network™ that lets your app earn revenue by terminating international calls on opted-in users' devices - the call rings like a normal incoming call the user answers - only for users who have explicitly opted in, and only while a call is being handled. Participating devices connect over the network's 100% Tier 1 CLI routes, and you earn a 50% share of the net termination revenue.
The plug-in has a negligible performance footprint - call setup under 200ms, roughly 30-50KB per call minute, under 2% battery, and no impact on your foreground app's performance. It is active only for opted-in users and only while a call is being handled. When a call is routed to a user it arrives as a normal incoming call they can answer or decline, so they stay in control - and if they are already on a call, Jingle reroutes it elsewhere and never interrupts them.
Currently, we support Android natively (minSdk 26 / Android 8.0+). The SDK also works with Flutter and React Native apps via the native Android plug-in.
Not at all. It involves adding the io.minutesnetwork:jingle-fullservice:5.6.0 dependency, initialising the JingleAdapter, and adding the JinglePermissions user consent flow. A dedicated integration engineer is assigned to every partner, and you can go live as fast as your team can integrate.
Apps with large, active and geographically concentrated user bases are usually the strongest fit.
No. Jingle is designed to add an additional revenue layer alongside existing monetisation such as ads, subscriptions, in-app purchases or paid features.
Only the required consent, disclosure and permission flows need to be presented to users. The core app interface and user journey do not need to change.
Yes. Jingle can be rolled out selectively depending on geography, app version, user eligibility and other technical criteria.
Revenue
Jingle generates revenue from communication activity processed through Jingle-enabled applications. When supported traffic is successfully routed through the app, the app partner earns a revenue share. Revenue depends on active eligible users, supported countries, network demand, voice-traffic rate and actual traffic processed.
Earnings are calculated at the end of each month and paid by monthly wire transfer within 30 days of month-end.
Payments are made by international wire transfer, processed monthly.
Yes, the minimum payout threshold is $100 USD. Amounts below the threshold roll over to the following month.
We provide access to a real-time partner portal from day one, where you can view daily active users (DAU), call volume and minutes terminated, and estimated revenue.
Revenue share is based on voice activity generated through the integrated application.
Yes. Revenue potential depends on factors such as eligible users, supported countries, network demand, user opt-in rates, device availability and actual traffic routed through the network.
Reporting can be shown by geography, app version, traffic type, user segment or other available analytics dimensions.
No. Revenue depends on geographical location, user opt-in rates, market coverage, and carrier rates and demand.
Technical
Minimal. Battery impact is < 2%. The SDK consumes resources only while a call is active, so there is no continuous background drain.
Yes! Flutter and React Native apps integrate the native Android (Kotlin) SDK through each framework's standard native-module path, and your dedicated integration engineer can support your team through the setup.
The Jingle Plug-In adds roughly 3-10MB to your APK - a lightweight addition that keeps your install size in check.
The SDK works over both Wi-Fi and mobile data. Usage is negligible either way - roughly 30-50KB per call minute, less than loading a single web page.
Jingle uses Android's standard, transparent mechanisms. The primary wake path is a foreground service with a UDP wake - Firebase Cloud Messaging is a fallback on GMS devices - and a visible foreground-service notification is shown while a call is active, so there is no continuous or hidden background activity. No calls are routed through a device unless the user has opted in.
Yes. Partners can use phased rollout, staged releases or limited geography testing before expanding to the wider user base.
Yes. Remote configuration can allow Jingle functionality to be paused, adjusted or disabled without requiring a full app update.
Performance can be monitored through analytics and logs at the Jingle Partner panel.
Jingle continues to operate according to the app's implementation, user consent status and permissions.
Compliance
Yes. Jingle Plug-In is fully compliant with Google Play policies. We mandate transparent user consent screens and adhere to data safety guidelines.
Yes. We do not collect personally identifiable information (PII). We operate strictly with anonymous device identifiers and follow GDPR and CCPA regulations.
The SDK accesses network connection status, battery level, the microphone (required for live call audio, which is processed ephemerally for real-time routing and never recorded), and the country code of the user's verified phone number to route calls to the right region. It requests no location permission and never uses GPS. An optional, skippable contacts permission can show saved-contact names on the incoming-call screen; contact data stays on the device and is never uploaded. The SDK does not access photos, messages, or browsing history.
Yes. Transparency is central to how Jingle works. Before the plug-in is initialized, you present our consent dialog that clearly explains what Jingle does, what data it uses and why, so users make an informed, explicit choice to take part.
Yes, users can opt-out at any time through the app settings if you implement the toggle, or by simply uninstalling the application.
Users receive a clear explanation of what Jingle does, what data is used and why, followed by an explicit consent action before activation.
Yes. Users are able to revoke permissions or disable participation through app or device settings. If required permissions are removed, Jingle functionality will pause.
Jingle data is only used for the described voice network functionality and is not used for third-party advertising purposes.
The integration does not use personal identification and uses only the identifiers required for voice network functionality, reporting and compliance.
