Consent

SDK End-User Consent Template

Required opt-in screen wording for developers integrating GetPassive, plus the matching paragraph for your Terms and Privacy Policy.

Version 1.2 · Effective 11 October 2026

Every integration needs both: (1) an in-app opt-in screen, shown before the SDK starts, with an option to accept and an option to decline of equal prominence, and (2) a paragraph in your Terms of Service and Privacy Policy describing the feature. Sharing stays off until the user accepts. On devices without a screen (TVs, IoT devices, media players), show the opt-in screen in your companion app or setup flow before sharing starts.

Required: in-app opt-in screen

Help support this app

This app uses GetPassive to share a small amount of your unused internet bandwidth when the app is running. We do not collect your name, accounts, files, messages, or browsing history — only your device’s IP address and basic connection data are used. GetPassive's business customers use it to reach websites for purposes such as price and market research, ad verification, brand protection and SEO monitoring.

You can opt out at any time in app settings.

Learn more

Short version: settings screen

Bandwidth sharing is active. Your unused bandwidth is shared via GetPassive. [Manage / Turn off]

Implementation notes for developers

For the opt-in screen:

In your Terms and Privacy Policy:

In either case:

Copy-paste text

This app uses GetPassive to share a small amount of your unused internet bandwidth when the app is running. We do not collect your name, accounts, files, messages, or browsing history — only your device’s IP address and basic connection data are used. GetPassive's business customers use it to reach websites for purposes such as price and market research, ad verification, brand protection and SEO monitoring. You can opt out at any time in app settings. Learn more: https://getpassive.io/legal/privacy.html

Questions: [email protected]

Build revenue you don't have to hide.

Consent-first bandwidth monetization for developers who want revenue without eroding user trust.