Skip to content
Log inDashboard

Privacy of your node

The self-hosted node runs in two modes, enrolled and standalone. This page says exactly what leaves your hardware in each, so you can choose. The privacy policy is the binding text; this page is the same facts, arranged by node, and quotes its section on nodes at the end.

In both modes, the node resolves and filters on your hardware:

  • Every query your devices send to the node, and its answer. Nothing about them is sent to opdns.
  • The node’s query log, in its SQLite file in the data directory, for the retention you set (Logs on your node).
  • Local names and private reverse lookups (home.arpa, DHCP leases, private-address PTR records), answered locally and never forwarded to the internet (Local names).
  • Its configuration and keys: the node token, the profile it last received, learnt signing keys, list files.

Your node’s own lookups to the internet go from its Unbound to the authoritative servers directly (and to the root servers for its copy of the root zone), as any resolver’s do. They do not go through opdns.

The node keeps one outbound connection to the opdns link service. Over it, opdns learns:

What Why
the node’s id and its public IP address, connection times to know the node is online, and to place it on your own Analytics globe
versions: node, Unbound, profile, lists to push updates the node has not applied
uptime, last sync time, clock offset, whether Unbound is healthy, the link’s round trip the node’s status in your dashboard
the ids of the profile-signing keys the node trusts to check it can verify the profiles it is sent
SQLite file size, oldest record time, pending and dropped record counts the log health shown in your dashboard

The public IP address is not stored: opdns keeps the approximate location looked up from it (country, and city when known), shown only to you on the node’s entry.

It never sends the queries it resolves or the logs it keeps, with one exception that you start: when you open Logs or Analytics in the cloud dashboard for a profile whose logs live on the node, the request goes to the node and the answer comes back through opdns to your browser. It is encrypted on each hop and not stored on the way; opdns’ servers can read it in transit. Countries for destination addresses are added on the way, because the node has no GeoIP data.

Logs travel the other way too, if you choose: queries your devices send to opdns’ cloud addresses (away from home, say) are logged by the cloud as for any profile, and with the log destination set to your node, those records wait in a queue for the node (at most 24 hours, or less if you set it) instead of being stored in the cloud (Settings).

No account, no link, no profile in the cloud. The node downloads the public list artifact; opdns sees each download’s IP address and time, kept in operational logs for 14 days. That is all.

It also means opdns’s operator blocks (legal takedowns and abusive-source blocks) do not reach a standalone node: they apply to the opdns resolver and to enrolled nodes only. A standalone node filters with its lists and its own rules, and its operator is responsible for what it serves.

  • Your node’s data is yours: delete the data directory (or the SQLite file) to erase its logs. opdns cannot reach it, and deleting your account does not touch it.
  • Unenrolling or revoking the node in the dashboard closes the link at once; the node keeps resolving with its last profile until you stop it.
  • Deleting your account revokes the node, purges any records queued for it, and deletes what the cloud held about it.
  • Look at the node’s status page or opdns-node status for the link state and log health; the same facts are all the cloud sees.
  • To keep queries off opdns entirely, point your devices at the node only, not at the cloud addresses, and run it standalone or set the log destination to the node.
  • Back up the data directory if you want to keep your logs (Upgrade and back up).

The privacy policy, section 7, reads:

The self-hosted node is the same resolver, running on your hardware.

  • Queries your node resolves never reach us. Logs your node produces stay in its SQLite file. They leave the node only as answers to your own dashboard queries (described below).
  • Enrolled mode. The node keeps one outbound WebSocket open to link.opdns.net. Over it we learn the node’s id, versions, uptime, last sync time, clock offset, whether its Unbound is healthy, the link’s round trip, the ids of the profile-signing keys it trusts, its log health (SQLite file size, oldest record time, pending and dropped record counts) and connection times, and, as with any connection, the node’s public IP address. We do not store that address: we store the approximate location looked up from it (country, and city when known), shown only to you on the node’s entry. We send it notices of profile and list updates. For profiles whose destination is self-hosted or both, we also send it the logs our cloud PoPs generated for that profile.
  • Logs for a self-hosted destination still pass through us. When your devices send queries to our cloud addresses, our PoPs answer them and log them as described in section 4. The records travel on the logs stream, and we hold them in a per-profile queue until your node acknowledges them (at most 24 hours; you can choose 12 hours, 1 hour, or not to queue them at all, in which case records made while the node is offline are dropped). If the node stays offline longer, the undelivered records are lost. They are not moved to ClickHouse.
  • Dashboard queries relay through the cloud. When you open logs or analytics in the cloud dashboard for a profile whose logs live on a node, the request goes to the node over the link, and the result comes back through our servers to your browser. TLS protects each hop, but our servers can read the result in transit. We do not store it.
  • Standalone mode. No account and no link. We see only downloads of the public list artifact (IP address and time), which stay in operational logs for 14 days.