Built for Google Play Policy Compliance

Built for Google Play from the Ground Up

Stay compliant with Play Store policies using our consent flow templates, data safety templates, and runtime permission handlers.

User Journey Contact Sales
Compliance Engine

Core Compliance Features

Jingle Plug-In automates the complex landscape of Google Play policies so you don't have to.

Prominent Disclosure

Reference designs and template copy for a clear, unavoidable disclosure prior to any permission requests, satisfying the prominent disclosure policy.

Runtime Permissions

Granular permission handling that respects user choice and handles "Never ask again" states gracefully.

Opt-Out, Anytime

A clear, always-available opt-out is built in and required: users can disable Jingle and withdraw consent at any time from in-app settings. Removing consent or a required permission immediately pauses the plug-in.

Foreground Services

Optimized background execution with required persistent notifications compliant with Android 14+.

Data Protection

Built data-compliant by design

Jingle Plug-In is built to meet UK GDPR and GDPR requirements - with consent, data minimisation, encryption and clear user rights at its core. Full detail lives in our Privacy Policy and Data Processing Agreement.

Lawful basis & consent

Processing begins only after an explicit, SMS-verified opt-in. Consent can be withdrawn at any time, and withdrawal pauses all processing.

Data minimisation

Only the minimum needed to route calls: phone number (one-time verification), a pseudonymised device token, country from the verified number, network state and call metadata. No contacts, messages, photos, browsing history, or GPS / precise location.

Encrypted signalling, ephemeral audio

TLS 1.3 encrypts all SIP signalling, and stored data is encrypted at rest with AES-256. Call audio is processed in real time for routing and is never recorded or stored.

Audio is never stored

Call audio is processed ephemerally in real time for routing and is never recorded or stored.

Controller / processor & DPA

The app developer is the data controller; Minutes Network is the processor under a UK GDPR Article 28 Data Processing Agreement, available on request.

Your users’ rights

Access, rectification, erasure and opt-out are supported under UK GDPR / GDPR. Data-protection enquiries: privacy@jingleplugin.com.

Data Safety

Data Safety Form Mapping

Every data type the Jingle Plug-In handles, mapped to its purpose and how it is processed - so your Google Play Data Safety declaration is clear and accurate.

Play Console Mapping

Data Type Collected? Shared? Purpose Required?
Audio Yes Yes App functionality (call routing) Yes (for Jingle)
Country / region (from verified number) Yes Yes App functionality (geographic routing) Yes
App Interactions Yes Yes Analytics (plug-in performance) Yes
Crash Logs Yes Yes Analytics (diagnostics) No (optional)
Device or other IDs Yes Anonymous session token only Yes App functionality Yes

Why "Shared" is yes: Jingle routes this data to Minutes Network, which is a third party relative to your app. Google Play therefore expects these data types to be declared as shared. Audio is shared only as a real-time stream for call routing and is never recorded or stored.

Note: If you declare the optional READ_CONTACTS permission (used to show saved contact names on the incoming-call screen), your Data Safety form must additionally reflect contacts access - even though contact data is read on-device only and never leaves the device.

Pre-Submission

What a Submission Needs

Lighter than it looks. A Google Play submission comes down to a handful of things - and your integration engineer helps you get each one right, so first-time approval is straightforward.

Privacy Policy URL

Ensure the link is active and accessible publicly.

Data Safety Form

Filled according to the mapping table above.

Video Recording

Record a video of the full consent flow.

Disclosure Copy

State what data is collected, why, and that it is shared with Jingle (the named telecom-routing partner). We recommend naming "Jingle Plug-In" for clarity.

Target API 35

Ensure your app targets SDK 35 (Android 15).

Review Credentials

Provide login details for reviewer access.

Integration

Technical Implementation

Manifest configuration and reviewer response templates for a smooth submission.

AndroidManifest.xml 
<!-- Permissions required by the Jingle Plug-In -->
<uses-permission android:name="android.permission.INTERNET" />
<uses-permission android:name="android.permission.RECORD_AUDIO" />
<uses-permission android:name="android.permission.FOREGROUND_SERVICE" />
<uses-permission android:name="android.permission.FOREGROUND_SERVICE_MICROPHONE" />
<uses-permission android:name="android.permission.POST_NOTIFICATIONS" />

<application>
    <!-- Jingle foreground call service (handles the live SIP session) -->
    <service
        android:name="io.minutesnetwork.jingle.CallService"
        android:foregroundServiceType="microphone"
        android:exported="false" />
</application>

Reviewer Response Template

Dear Google Play Review Team, Our application integrates the Jingle Plug-In by Minutes Network™, which terminates international voice calls on opted-in users' devices - the call rings as a normal incoming call the user can answer - as described in our store listing. We have implemented a prominent disclosure that appears prior to runtime permission requests, as shown in the attached video and screenshots. This disclosure clearly states: 1. The data being collected (phone number for one-time verification, a pseudonymised device ID, IP address, country derived from the verified phone number, network type, and call metadata such as duration) 2. The purposes (call routing, call quality, billing and revenue calculation, and fraud prevention) 3. That data is shared only with telecom carrier interconnections and infrastructure providers under data processing agreements, and is never sold or used for advertising. The Jingle Plug-In is only initialized after the user explicitly accepts this disclosure, and users can disable it at any time in the app's settings. Thank you for your review.

Need Help with Compliance?

You won’t navigate Google Play compliance alone. Our integration team supports you through the whole submission - reviewing your consent flow, disclosures and Data Safety form before you go live - so you can submit with confidence.

Get Started Contact Support