Consent-first bandwidth SDK

Revenue that survives every review.

Legal review. App store review. Antivirus review. Clearhop monetizes opted-in bandwidth — and publishes the assumptions, limits and terms that other SDKs keep private.

Request accessor read the acceptable-use policy →
11:02wi-fi · charging
nothing runs — app works as before
Support this app — no ads

Allow the app to use a small amount of your unused internet bandwidth. Only on Wi-Fi, only while charging.

no personal data · turn off anytime in settings

AllowDon't allow

The exact dialog your users see. Two equal buttons — by policy, not by accident.

The facts, before the pitch.

Consent basis, jurisdiction, vetting, use policy — public and verifiable. The rest of the page assumes you've seen them.

Consent basis
GDPR 6(1)(a)
Entity
EU · Estonia
Partner vetting
KYC · Sumsub
Use policy
Public AUP

Four steps, one gate.

Prohibited destinations are dropped at our gateway, in the EU — not on the user's device, and not on trust.

01
Integrate the SDK

Async, off the UI thread, inactive until consent exists.

02
The user opts in

One dialog, two equal buttons, a written record either way.

03
Idle bandwidth is shared

Wi-Fi only, charging only. Filtered and logged at the EU gateway.

04
You get paid per device

Per consenting active device, monthly, terms set in the agreement.

■ prohibited destinations dropped at the gatewayread the full mechanics →

What this network never touches

Every request is checked against the same list you are reading. Public, versioned, referenced in every agreement.

Acceptable use categories and their status
No.CategoryExamplesStatus
01Public web dataPrice monitoring, ad verification, brand protection, market researchPERMITTED
02Rate-limited targetsHigh-volume requests to a single destinationRESTRICTED
03Financial infrastructureBanks, payment systems, card networks, crypto exchangesPROHIBITED
04Government & military.gov, .mil, law enforcement, public administrationPROHIBITED
05Healthcare & educationMedical databases, .edu, student information systemsPROHIBITED

Run the numbers yourself.

254K
1Klog scale5M
Audience geography
30%

Indicative, based on published assumptions — including the opt-in rate other calculators quietly set to 100%.

estimate · not_an_offerINDICATIVE
Opted-in devices~76,112
Monthly$26,000 – $47,000
Yearly$310,000 – $565,000
opt-in 30% · us/eu heavyexact quote → 1 business day

What it costs your team.

The SDK is in a closed pilot. Access follows the application — there is no self-serve download and we do not pretend otherwise.

AndroidWindowsiOS · soonmacOS · soonSmart TV · soon
You receive
SDK package and integration guideConsent flow, ready to displayTest access before launchAn engineer on the integration
You implement
Show the consent dialog before initUpdate your EULA and privacy policyLink to our policies from yours
Onboarding
Apply → KYC → agreementIntegration and testLaunch and first payout cycle

Asked before every deal.

What publishers ask before the first call. Longer answers live on the FAQ page.

Clearhop is a bandwidth-sharing SDK for Android, Windows and other platforms. It lets users of your app share their unused internet bandwidth with vetted business customers — for public-web tasks like price comparison, ad verification, and brand protection. The SDK runs only for users who explicitly opt in via a standalone consent dialog, stays inactive without consent, and you're paid monthly for every consented active device.

Store review is the stores' decision, so no vendor can honestly guarantee approval. What we control is everything reviewers look at: explicit opt-in before any activity, a standalone consent dialog with the benefit stated and two equal buttons, and a documented data-practices disclosure for your store listing. You review the exact consent flow before integrating, and our team supports you through the store review.

No personal data. The SDK doesn't read screens, messages, files, or browsing history. It routes encrypted requests from vetted business customers through the device's idle connection and records the consent state — granted, declined, or revoked. Sharing runs only on Wi-Fi and only while charging by default, so it doesn't touch mobile data or battery.

It depends on where your users are, your platform, and how many opt in. Instead of a single headline rate, we publish indicative ranges by geography and an open calculator on the revenue page — with every assumption stated, including the opt-in rate. Final terms are set individually in the partner agreement, and founding partners lock elevated rates.

Nothing changes for them. The consent dialog has two equal buttons by design, and a decline means the SDK never runs — the app works exactly as before. A user who opted in can revoke consent at any time from the same place it was given, and the revocation is honored on the device within seconds, not at the next session.

Businesses that pass KYC verification (via Sumsub) and use-case screening against our public Acceptable Use Policy. Permitted uses are public-web tasks like price monitoring, ad verification and brand protection. Prohibited categories — financial infrastructure, government, healthcare and education systems — are blocked at our EU gateway, not left to trust.

Typically a few hours to a day. The SDK ships after your application is reviewed — there is no public download — with native libraries per platform, an integration guide, a ready-to-display consent flow, test access before launch, and an engineer assigned to your integration.

Monthly, per opted-in active device, at the rates fixed in your partner agreement. The payment schedule, method and minimum payout are all part of the agreement — no thresholds hidden in an FAQ, no surprise deductions.

Founding partners — closed pilot

First in, best terms.

A limited set of founding partners get elevated rates, a direct line to the team, and a say in the SDK roadmap.

Request access