BuckDNS · Product information
Privacy Notice
BuckDNS Privacy Notice — version 2026-10-04 Installation check-ins are optional and disabled by default, including when upgrading an installation without a saved preference. Enable or disable them in Settings → Privacy Controls. When enabled, BuckDNS sends a random installation ID, application version, operating system (Linux or Windows), and installation date at startup, after upgrades, and daily when connectivity permits. It does not send DNS queries, browsing history, client identities, local zones, local IP addresses, or network configuration to this service. Disabling check-ins stops future reports after the preference is saved; a request already sent cannot be recalled. Automatic update checks are enabled by default and can be disabled in Settings → Updates. Automatic and manual update checks fetch signed public release information without sending an installation ID or installation date. They do not register an installation. Turning automatic update traffic OFF disables check-ins as well and stops all automatic requests to this service: no version pings, telemetry, anonymous check-ins or background retries. Check-ins can only be enabled while automatic update traffic is on. Turning automatic update traffic back on leaves check-ins off. Manual checks and downloads contact the service only when requested. DNS continues working with both controls disabled. A stable random ID lets us distinguish installations that opt in. We record the first and most recent check-in time. Installation records expire after 365 days without a check-in; aggregate counts may be retained. These counts do not measure all installations or establish current uptime. Opting out does not delete reports already received. To request removal of a reporting record, contact [email protected] with the installation ID shown in Privacy Controls. Proof of control may be required before removing a record. Connections necessarily expose a public IP address to network infrastructure, including hosting and delivery providers. The installation-statistics database does not store IP addresses or browser identifiers. Operational infrastructure may process connection information for delivery and security. The stable installation ID is not anonymous. Installer delivery requests are counted by platform and release; these are download requests, not confirmed installations or unique people. No advertising cookies or tracking pixels are used by the reporting dashboard or update service. Reported installation data is not sold or used for advertising. Local query history, application logs, domain statistics and cached answers can contain sensitive network activity. Settings → Privacy Controls provides storage and retention controls. Disabling storage does not erase existing files, backups, exported reports or operating-system logs. Diagnostic queries run only when requested; diagnostic output is displayed locally and is not automatically uploaded to the update service. DNS resolution contacts the selected forwarding providers or authoritative servers. DoH and DoT encrypt transport to the selected provider; that provider can still see the requested names. Direct recursion is not encrypted. QNAME minimization limits the names disclosed during recursion. Emergency DNS follows the configured fallback, including unencrypted recursion when selected. Enabled list subscriptions contact their configured source URLs; automatic refresh can be disabled per subscription. Cluster communication shares configured settings, zones and signing material between paired servers. These necessary or configured network operations are separate from installation reporting. Contact: [email protected]