A connection is shared. A computer is not.
Other people's traffic goes out through a slice of someone's internet connection. Nothing reads what they do with the rest of it. This page is the whole of what is recorded and the whole of what is enforced — if either changes, this page changes first.
What we can and cannot see
We never see
- What you browse, watch or search for
- Your files, photos or messages
- Anything you type — we have no access to your device
We do record
- How many gigabytes each device shared, and under which publisher id
- Its IP address, and the city and network it connects from, so traffic exits nearby
- What kind of device it is — operating system, processor, hostname and SDK version
- When it connected and disconnected
Read the privacy policy for the full version.
Four things that are true whatever anyone promises.
Each of these is a mechanism, not a policy — enforced in the code that runs, on the device or at the gateway, whether or not anybody is watching.
The local network stays out of reach
The exit resolves every destination itself and refuses anything that is not a routable public address — no localhost, no 192.168.*, no router admin page, no cloud metadata service. It then connects to the address it checked and never re-resolves the name, so a host cannot answer public once and private the second time. Nothing reaches a printer, a NAS or a router behind the front door.
Not a spam relay
Mail submission ports are refused at the gateway, before a request is ever handed to a device. Spam relaying is the dominant abuse of networks like this one, so it is refused by default rather than by configuration.
A publisher id is public by design
It says which account earns the bandwidth and grants access to nothing else. It ships inside third-party apps and is handed out as a QR code, so committing one to a repository — or finding one in a decompiled binary — leaks no credential.
Every request is logged
The account behind it, the destination, and the decision taken — allowed, denied or rate-limited — recorded for abuse investigation. Traffic through the network is accountable rather than anonymous.
Depends which side you are on.
Everything above is about your device and your connection. You choose when it runs, you can stop at any moment, and the only thing we learn is how much was shared, from roughly where, and by what kind of machine.
Let your phone pay youIf you are shipping an appEverything above is what your users get, and what you can tell them truthfully. The SDK cannot start itself, has no interface of its own, and sends us nothing about what happens inside your app.
Monetise without adsRead it, then decide.
No card, no contract, and nothing runs until you say so. Stop whenever you like and the earnings you have settled stay yours.