Consent and the Value Exchange
Sharing bandwidth can be a genuinely good trade when the person making it has visibility into their side of the trade.
Bandwidth, not data.
Much of the web is not accessible to machines and agents when using a normal data center to route traffic. Companies pay to read public web pages from a home connection instead so they have access like a human would, but at scale. Software can route that traffic through a little of your spare connection while you are not using it.
This is what pays for the tool, instead of ads, tracking, or a subscription you forget to cancel.
Told up front and nothing pre-ticked.
The request appears at install, on its own screen, before anything is running and not as a clause inside a license agreement. Nothing is ticked on your behalf, and the installer will not continue until you tick it yourself.
A switch you can reach.
The sharing has an on/off switch in the app's own settings, where you can find it without asking anyone for permission.
A clean uninstall.
Uninstalling the app removes the sharing with it. No separate uninstaller, no leftover service, nothing running afterwards.
Four things to check.
Each of the four has a familiar way of being skipped. Recognising the skip is the whole skill.
Up front
Its own screen at install. Not a clause on page nine of a license agreement.
What runs through it, and what does not.
Used for
Prices and listings
Checking prices, stock and product pages the way a shopper in that country sees them.
Ads monitoring
Confirming an ad and its landing page render the way they should in each market.
Search results
Tracking how results and rankings differ from one location to the next.
Pages for AI
Fetching live public pages for AI systems to read, retrieve from and train on.
Not used for
Anything of yours
Your home network, your loopback interface and cloud-metadata endpoints are unreachable from a customer session.
Malicious infrastructure
Malware, phishing, cryptojacking, denial-of-service tooling and intrusion services are blocked at the network layer.
Money and accounts
Banks, payment processors, card networks, and cryptocurrency exchanges, wallets and mining pools.
Restricted content
Adult content, gambling, weapons, extremist material and remote-access services.
A switch on our side, too.
The four pillars are worth something only if something happens when an app ignores them. Every partner app reaches the network through our SDK, and every one of them can be switched off from our side.
The details, in full.
Massive carries ordinary web traffic over standard web ports. Higher-risk destinations are blocked at the network layer before any request reaches your device, including malicious infrastructure, financial and cryptocurrency services, adult content, gambling, weapons, extremist content, and remote-access services. Mail and remote-administration ports are blocked outright, since those enable spam and credential attacks. Denial-of-service, malware, CSAM, spam, credential stuffing, unauthorized scanning, and any unlawful activity are prohibited regardless of destination. Details at joinmassive.com/blocked-destinations.
Every device joins by informed, affirmative opt-in and can opt out in one click. We collect only what running the network requires and never browsing history, file contents, or personal communications. A customer session can never reach a device's own home network, loopback, or cloud-metadata endpoints, blocking enforced server-side across all traffic. Per-device bandwidth caps, rate limits, and anomaly detection run continuously, with offending sessions throttled or suspended automatically. Customers are vetted through identity, use-case, payment, and sanctions checks before they get production access. Details at joinmassive.com/best-practices.
Something not right? We want to hear it.
Report an app that took the bandwidth without asking, or send us privacy feedback directly. Both forms reach a person on our team.