The anti-Onavo. Last updated: 2026-05-02 · Version 1.0
In 2013 Facebook bought Onavo, marketed as a "free VPN to protect your data." In reality Onavo Protect logged every packet users sent through it — Facebook used this to spy on competing apps (WhatsApp, Snapchat, TikTok) before acquiring or copying them. Apple removed it from the App Store in 2018; the service was shut down in 2019. It is the textbook example of surveillance dressed up as privacy.
LOVE Nodes is the opposite. This page exists so you don't have to take our word for it — you can verify the architecture, the rewards formula, and the open-source server config yourself.
WireGuard does not record packet contents by design. Our hub config uses LogLevel=quiet and stores zero per-flow data. The only thing we count is total bytes/sec for reward purposes.
We never look inside encrypted tunnels. We do not run any deep-packet-inspection middleware, ad classifier, or competitor tracker. There is no equivalent of Onavo's intel pipeline anywhere in this codebase.
We will never sell, broker, license or share user metadata, traffic patterns, IPs, or app usage with advertisers, brokers, or any third party. This is enforced contractually in the Terms and structurally in the schema.
Default resolvers in your .conf are Cloudflare 1.1.1.1 (no-log) and Quad9 9.9.9.9 (Swiss non-profit, no-log, malware filter). You can change these to your own resolver any time.
Node rewards are pegged to electricity (kWh × local price), uptime, and total bandwidth volume — never to which sites or apps you used. There is no economic incentive for us to look.
The Ansible playbooks, edge functions, and reward formulas are all in the repo. Partners can be granted read access to verify (see GitHub: LoveCoin12).
| Aspect | Facebook Onavo (2013–2019) | LOVE Nodes |
|---|---|---|
| Logs traffic content | Yes — full DPI | No — WireGuard, no logging |
| Sells user data / metadata | Yes — for M&A intel & ads | Never. Contractually + structurally. |
| Who owns the node | Facebook servers | Users self-host (peer-to-peer) |
| Reward / revenue model | Surveillance → ad targeting | kWh + uptime + bandwidth (pegged USDL → LOVE) |
| Marketing honesty | Hidden in ToS | Public pledge + open infra (this page) |
| DNS resolver | Facebook-controlled | Cloudflare 1.1.1.1 / Quad9 (user-changeable) |
| 3rd-party SDKs in client | Many (FB, ad networks) | None |
| Removed by Apple App Store? | Yes (2018) | n/a — open desktop client |
We are not pretending to be invisible — to pay you fair rewards, the server needs volumetric counters. These are the only fields stored:
Notably absent: visited domains, app fingerprints, packet contents, query logs, browsing history, social graph, location.
The downloaded WireGuard config opens with a Privacy Pledge header. No magic — what you see is what runs.
Server playbooks live in infra/ansible/ and the desktop daemon in desktop/love-nodes/. Request read access via @LoveCoin12.
Don't trust Cloudflare/Quad9 either? Edit the DNS line in the .conf to point at your local PiHole or NextDNS. Nothing breaks.
Treasury commits 10,000 LOVE as a public bug-bounty pool reserved specifically for credible evidence that LOVE Nodes is logging, inspecting, or selling user traffic in violation of this pledge. Submit via /legal contact channel.
Operated by Wise World 2012 Limited (HK SAR) · © 2026 lovecoin.life · This pledge is binding under our Terms of Service §12.