How it works

How consent-first bandwidth sharing works.

Bandwidth sharing lets an app route small amounts of a device's unused internet capacity to vetted businesses — for public-web tasks like price monitoring and ad verification. In Clearhop, nothing moves until the user explicitly opts in.

sdk_session · traceLIVE
[11:02:41]wi-fi · charging · idle — conditions met
[11:02:44]consent check → grant #0043 found
[11:02:45]session open · share capped
[11:02:47]request in · target allowed by AUP
[11:02:47]routed via EU gateway · logged
[11:03:12]charger unplugged → session paused
[11:03:12]receipt written · 0 personal data

Not a checkbox. A state the user controls.

Consent has a lifecycle: shown, granted, declined, revoked. Every transition is recorded — and the SDK obeys the current state, not the one from last week.

Support this app — no ads

Allow the app to use a small amount of your unused internet bandwidth.

AllowDon't allow
sharing stopped · receipt written
01 · shown
Dialog shown

The user sees the benefit and the conditions. Nothing runs yet.

no state · sdk inactive
02 · granted
Consent granted

A receipt is written. Sharing may run — only within the stated conditions.

record written · sharing allowed
03 · revoked
Consent revoked

One tap in settings. Honored on the device within seconds.

honored in 1.2s · record written
02b · declined
Consent declined

The SDK does not initialise, does not retry, does not ask again on next launch.

record written · nothing runs

Runs only when it costs the user nothing.

Exact thresholds live in the SDK configuration — figures publish after the build.

Network
Wi-Fi only
Power
Charging only
Device
Idle only
Bandwidth
Small share, capped

Every decision leaves a receipt.

A grant and a withdrawal are the same kind of record. That is what makes the consent state auditable rather than assumed.

Consent receipt contains
Timestamp2026-08-12T11:02:44Z
Policy versionaup 1.2 · pp 1.4
Scopebandwidth_share
Withdrawalsame record type
Choicegranted
Never collected
Page content or traffic bodies
Browsing history
Files, photos, contacts, messages
Precise location
Anything tied to a personal identity

Not “we comply”. Here is what compliance looks like.

Valid consent must be freely given, specific, informed, unambiguous and withdrawable. Each of those is a design decision in the dialog below.

11:02wi-fi · charging
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

annotated · numbers match the principles

01
Informed — the benefit is in the user's words

“Support this app — no ads” states what the user gets in exchange. A purpose that is disclosed but not understandable does not make consent informed.

02
Specific — conditions on the same screen

Wi-Fi only, charging only, no personal data, scope named. Conditions that appear after the tap are not conditions the user agreed to.

03
Freely given — two buttons of equal weight

Same size, same position, same tap target, no pre-selection. A decline that is harder to reach than an accept is the single most common reason a consent flow fails review.

04
Unambiguous — nothing runs before the tap

The SDK stays inactive until a grant exists. On decline it does not initialise, does not retry, and does not ask again on the next launch.

05
Withdrawable — one tap, in settings

Withdrawal has to be as easy as granting. The revocation is written to the log and honored on the device within seconds, not at the next session.

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 →

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