Our principles
Consent-first
Participation is explicit and default-off. We require partner apps to disclose participation before anything routes through a user's connection, and to give users a way to stop sharing that is at least as easy to find as the way it started.
Transparent payouts
Earnings follow a transparent, tiered model — country tier, uptime, connection quality, and live demand all factor in, with higher-demand regions earning up to about $0.50 per active user per month (an illustrative top-tier maximum, not a fixed or guaranteed per-user rate). Payouts are drawn from a shared monthly pool and governed by our Terms; the only adjustments we make are for fraudulent, automated, or non-consented activity, and your reporting always shows what you earned and why.
Data minimisation
We don't access personal files, browsing history, messages, photos, contacts, microphone, camera, or stored user content. The SDK routes connections to publicly reachable web content on behalf of vetted business customers. Nothing else leaves the device.
Reviewed demand
Business customers are reviewed and contractually scoped to specific use cases. We say no to demand that doesn't fit, and we keep saying no even when it costs us revenue.
What our network is used for
Approved business customers use GetPassive bandwidth for legitimate, web-facing workloads:
- Market research — collecting publicly available pricing, listings, and product data at scale.
- Ad verification — catching fraud and misdelivery in digital ad networks.
- Brand protection — detecting unauthorised use of brand IP, counterfeit listings, and impersonation.
- SEO and search-quality monitoring — measuring how content appears in search results across regions.
- Cybersecurity research and threat intelligence — observing public infrastructure to identify malware, phishing, and abuse patterns.
- Public content delivery and accessibility checks — verifying that public sites are reachable and rendered correctly from different regions.
- Price comparison — aggregating publicly listed prices for shopping and travel comparison services.
What's not allowed
The following activities are prohibited under our acceptable use policy and result in immediate removal:
- Credential attacks, password stuffing, or account takeover.
- Spam, phishing, or malware distribution.
- Denial-of-service attacks.
- Evasion of law enforcement or sanctions.
- Targeting children's services, or enabling participation for users under 18.
- Any activity that harms users, networks, or third parties.
Customers who violate these boundaries are removed from the network.
How developers ensure consent
GetPassive's SDK does not display a consent screen itself. Developers disclose participation through their own Terms of Service and Privacy Policy, with optional in-app prompts where preferred. Either path is acceptable, provided the disclosure is plain-language, default-off, and as easy to refuse as to accept.
Participation is default-off. Users can revoke from the app's settings at any time. Developers must not enable participation by default and must not enable participation for anyone under 18, and must not use the SDK in apps directed at children. See the public consent template for the recommended in-app copy.
What we don't access
The SDK has no need for — and no access to — personal user content. Specifically, it does not read or transmit:
The SDK routes connections to publicly reachable web content. Nothing else.
Reporting concerns
If you believe the network is being misused, email [email protected] with as much detail as you can share — including timestamps, source/destination patterns, or sample requests where possible. We investigate every report.
Build revenue you don't have to hide.
Consent-first bandwidth monetization for developers who want revenue without eroding user trust.