Every question, answered plainly.

It depends on three things you already know — daily active users, where they are, and how many opt in — and one thing we publish: the payout range per shared gigabyte. The calculator on the revenue page runs these numbers with every assumption visible and editable. What we won't do is quote a single headline figure: for this model, any single number is either a best-case hour or a lie.

Monthly, per consenting active device. Payouts start once your balance passes $50; payment methods and exact terms are confirmed in the partnership agreement during onboarding.

Because demand for bandwidth moves across the year, and a single rate would describe the most optimistic hour of the best month. The range covers realistic demand scenarios. Any calculator that shows one big number is quietly assuming 100% opt-in and peak pricing — ours assumes 30% and says so.

Three inputs, in order of weight: geography of your audience (US and EU traffic is in higher demand than emerging markets), the share of users who opt in, and platform. Final commercial terms are set individually in the agreement — never silently changed mid-contract.

One dialog, written in plain language: what sharing means, the conditions it runs under, and two equally weighted buttons — Allow and Don't allow. No pre-ticked boxes, no dark patterns, no repeat nagging. The exact dialog is shown on the how-it-works page.

No. Sharing runs only on Wi-Fi, only while the device is charging, and only when it is idle — so it never touches mobile data plans, never drains a battery in use, and never competes with your app for the connection. Outside those conditions the SDK does nothing.

Nothing. The app works exactly the same, every feature included, and the SDK stays inactive. A declined record is written with the same care as a granted one — it proves the user was asked, not pushed.

Yes — one tap, at any time. Sharing stops immediately, mid-session if necessary, and the revocation is written to the same consent record. No confirmation mazes, no retention tricks.

No. That is the point of the model: revenue without ads. The SDK has no visible interface beyond the consent dialog — no banners, no interstitials, no notifications.

Store policies require exactly what the SDK already does: explicit user consent, clear disclosure, no hidden background activity. The integration kit includes the disclosure texts for both stores, and we review your submission materials with you before you ship. The final decision is always the store's — our job is to make sure nothing in the SDK gives a reviewer a reason to say no.

The kit ships with ready-made entries for Play's Data Safety form and Apple's privacy labels, matching exactly what the SDK does: no personal data collected, IP address processed for routing, traffic totals for accounting. You paste them in and your listing stays accurate.

NextGen Connectivity OÜ, an Estonian company operating under EU law, is the controller for sharing-related processing. Your app remains the controller of everything it already does. The exact split is written out in the agreement and the privacy policy.

Explicit consent — GDPR Article 6(1)(a). Freely given, informed, revocable at any time, and recorded in both directions: granted and declined.

Yes. The SDK is not for apps directed at children, and the consent flow is designed for adult audiences. How this applies to a mixed-age audience is part of the compliance review during onboarding — before integration, not after.

To vetted businesses running public-web tasks — price monitoring, ad verification, brand protection, market research. Every request enters through our gateway in the EU, is checked against the acceptable-use policy, and is logged. Nothing routes device-to-device.

Nine categories, published in full — from financial infrastructure and government domains to bulk account creation and attack traffic. It is not a statement of intent: prohibited requests are dropped at the gateway before they ever reach a device.

Every buyer passes KYC verification through Sumsub and a use-case screening before getting access, and signs the same acceptable-use policy we publish. Vetting doesn't end at signup: gateway logs are monitored, and violations end access.

The report goes to people, not a void. Every request through the gateway is attributable to a buyer, so reports are investigated against logs, and confirmed violations end the buyer's access. The abuse address is in the footer of every page.