<!-- coderabbit-ai-generated:v1 -->
<!-- coderabbit-ai-generated-section:v1:2fc818703e062b5a9b2d607afee4b25ce5b73b63d69f2148847a3c156fe59dc1 -->
Last updated: 2026-11-15
<!-- /coderabbit-ai-generated:v1 -->
Effective date: 2026-08-08
Boxing is an open-source browser extension that provides a hierarchical, infinite-canvas bookmark organizer. This privacy policy explains what data we collect, how we use it, and how we protect it. Its scope covers the Boxing extension and its demo mirror; services operated by third parties (icon providers, GitHub, your WebDAV host) are governed by their own policies and are out of scope of this document.
Boxing does not collect, transmit, or sell any personal data to any server operated by the developer.
The full source code is available at https://github.com/Xxx91n/boxing under the Apache-2.0 license. You can audit every line of code yourself.
Data stored locally on your device:
Data we do NOT collect:
Your data is used solely to provide the extension's functionality:
No data ever leaves your device unless you explicitly configure optional cloud backup (see below), or as part of the automatic favicon and version-check requests disclosed in Network Connections.
Boxing is local-first: your bookmarks, layout, and settings stay on your device unless you enable backup. The extension does, however, make the following automatic or user-triggered outbound requests:
<!-- coderabbit-ai-generated:v1 -->
<!-- coderabbit-ai-generated-section:v1:64d3ba3d131fae4d4a600eb88ca4742a1f72931c693dff66e9bf3cc1270b00a7 -->
Favicon retrieval (automatic, on by default). For an uncached icon or a cache refresh, Boxing requests all five third-party icon services and the bookmark site’s own https://<host>/favicon.ico in parallel. The services are DuckDuckGo (icons.duckduckgo.com), Google (www.google.com/s2/favicons, which can redirect to t*.gstatic.com), favicon.im (favicon.im), icon.horse (icon.horse/icon/), and Yandex (favicon.yandex.net/favicon/v2/). The first successful response is used and cached; the other requests are not cancelled. A session winner does not restrict later requests to one service. Failed lookups are retried when displayed after 7 days. Each new-tab load also retries up to 3 failed lookups older than 7 days in the background after the page has painted, including icons outside the current view. These requests include only the bookmark site’s hostname, never its title, full URL, or other bookmark data. As with any browser request, browser-controlled metadata (such as your network address, referrer, or cookies) may also be transmitted; Boxing does not and cannot control those fields.
<!-- /coderabbit-ai-generated:v1 -->
Version check (automatic). The About screen periodically queries the GitHub Releases API (api.github.com/repos/Xxx91n/boxing/releases/latest) to show whether a newer version is available, with a fallback to https://boxing.xxx91n.com/demo/version.json. This request is anonymous and does not include any local data.
User-configured backup (optional, off by default). If you enable cloud backup, Boxing contacts the WebDAV server you configure and/or the GitHub Gist API (api.github.com/gists) as described under Data Storage. These connections go directly from your browser to the servers you choose.
All primary data is stored locally using chrome.storage.local, which persists across browser sessions and is scoped to the extension. This data never leaves your device.
Boxing supports optional cloud backup via WebDAV or GitHub Gist. These features are disabled by default and require explicit user configuration:
WebDAV URLs must be public HTTPS endpoints by default. The extension refuses literal private, loopback, and link-local hostnames — localhost, 127.0.0.0/8, 10.0.0.0/8, 192.168.0.0/16, 169.254.0.0/16 (including the cloud metadata address 169.254.169.254), 172.16.0.0/12, *.local, and *.internal — in the settings UI and again in the extension's background proxy before any request leaves the browser. These checks inspect the hostname string only; they do not resolve DNS, so a public-looking hostname that resolves to a private address is not covered by this rule. The reason for the default refusal: a WebDAV URL you enter is later fetched by the extension, and permitting private addresses would turn a mistyped or hand-supplied URL into a request originating from inside your network (SSRF-style exposure) — router admin pages, NAS interfaces, cloud metadata endpoints. Also refused: non-HTTPS URLs, URLs longer than 2048 characters (checked on the URL you enter — the derived backup-file URL is checked the same way; see the known gap tracked in issue #108), and URLs with an embedded username/password.
Self-hosted WebDAV on your LAN or on localhost is refused by default and can be allowed by an explicit opt-in: Settings → Sync → WebDAV → *Allow private / local network hosts (advanced)*. The checkbox ships off. Turning it on relaxes only the private-host refusal — HTTPS remains required, and the no-embedded-credentials rule and 2048-character URL limit still apply. Enable it only for a server you own, and prefer a name you control on a public HTTPS endpoint wherever that option exists.
In both cases, the data path is directly from your browser to your chosen cloud provider. Boxing's developer has no access to your data, your credentials, or your cloud accounts.
chrome.storage.local — other extensions cannot access it.chrome.storage.local, and is never included in the layout, JSON exports, WebDAV/Gist backups, or snapshots — an export or backup file read in isolation cannot unlock your credentials. It does not protect them from anyone who can read your browser profile (the key sits in the same storage area as the ciphertext) or who has the running extension. There is no passphrase prompt on this path and no user-supplied key material in it; do not rely on this as strong encryption.boxingBackup: 1 envelope — PBKDF2-SHA-256 (310,000 iterations, per-file 16-byte salt) → AES-GCM-256 with a per-file 12-byte IV. We never transmit or store that passphrase anywhere: it is not written to your profile, the layout, a snapshot, a sync payload or a log, and it is cleared from the dialog the moment it closes. Consequences we state rather than soften: lose the passphrase and the file stays unreadable (there is no recovery path and no passphrase sync), and the sealed file is readable by anyone who does hold it, so treat the file and the passphrase together as the secret. This protection covers exported files only — automatic backups and sync traffic keep their own existing protocol, and the per-install credential key above is never used to seal one, which is why restoring a backup on another install still asks you to re-enter your WebDAV/GitHub credentials.We do not sell or share your data with anyone. Your bookmarks, layout, and settings stay on your device unless you explicitly configure cloud backup. The automatic favicon and version-check requests in Network Connections send only the minimal technical data described there (a bookmark site's hostname for favicon lookup, or an anonymous version-check request) to the third-party icon services and the GitHub Releases API.
Boxing is not directed at children under 13. We do not knowingly collect any data from anyone, including children. If you believe a child has provided information to us, please be aware that we do not retain or have access to any such data — all data is stored locally on the user's own device.
We may update this privacy policy from time to time. Changes will be posted to this page with an updated date. Since Boxing does not collect data, changes to the policy typically reflect updates to the extension's features.
For privacy questions or concerns, please open an issue on our GitHub repository.
Boxing is licensed under the Apache-2.0 license. The complete source code is available for independent audit at https://github.com/Xxx91n/boxing.