Linkhaven Privacy Policy

Local-first by design.

Linkhaven stores your workspace data locally in your browser on your device. It does not send your boards, templates, themes, images, or local usage statistics to Linkhaven servers. With the default settings it makes no network requests; requests only go to the sites you open, and to icon, chart, news feed or AI sources once you turn those features on.

Last updated: 2026-10-28 Open Linkhaven

1. Scope

This policy applies to the Linkhaven browser extension and to hosted web builds of Linkhaven that use the same local-first storage model.

2. What Linkhaven stores

Linkhaven may store the content you create or import directly inside your browser so the app can function between sessions.

  • Workspaces and workspace names
  • Link cards, groups, pictures, chart and news feed nodes (their feed addresses and display settings), layout positions, and board settings
  • Uploaded images and image gallery items
  • Templates, custom themes, and appearance preferences
  • Local usage statistics such as canvas opens and link opens
  • Import and export metadata needed to restore your data correctly

3. Where that data is stored

Linkhaven stores data locally in browser-managed storage on the current device, including browser storage mechanisms such as IndexedDB and local storage when required for the product to work.

Your Linkhaven data stays isolated to the browser profile and device where you use it, unless you explicitly export it yourself.

4. What Linkhaven does not do

  • It does not require an account or sign-in.
  • It does not upload your workspace content or local usage statistics to Linkhaven servers.
  • It does not include third-party advertising.
  • It does not use third-party analytics or behavioral tracking.
  • It does not sell or share your workspace data with external parties.

5. External requests

With its default settings Linkhaven makes no network requests at all. The requests below belong to website icons, Google favicons, app icons, chart and news feed nodes, Check Links, the Auto dashboard's AI arrangement, and device sync, which are each off by default and only work after you turn them on under Menu → Privacy, which also shows their current status.

  • Website icons. With Website icons on, creating a link card loads the site's icon once from the site itself (/favicon.ico) and keeps it locally. With Google favicons also on, Google's public favicon service is the fallback; it is never asked about local addresses such as IPs or .local names. With both off, cards show a default picture or an image you uploaded.
  • App icons. With App icons on, a card whose name or address matches a self-hosted app (Jellyfin, Radarr, Home Assistant, …) gets that app's icon. The matching happens on your device; only the one icon is loaded from cdn.jsdelivr.net (the dashboard-icons collection) and kept locally. jsDelivr sees your IP address and the icon's name, nothing about your cards.
  • Chart nodes. A chart connects to the feed server address set on the chart (by default a server on your own computer, 127.0.0.1) and sends the symbol and time range it should show.
  • News feed nodes. A feed node loads the RSS or Atom addresses you add, through the feed proxy address set on the node (by default a proxy on your own computer) or directly when you clear the proxy. If Images is on in the feed options, article images load directly from the news sites.
  • Local links. When a card has a local link and you click it, Linkhaven first sends one request to that local address to see whether it answers, then opens it or the card's main link. Nothing is sent before you click.
  • Check Links. When you start it in the Data tab, Linkhaven sends a HEAD request to each link card's address to see whether it still answers.
  • Auto dashboard. With Auto dashboard on, Linkhaven builds a workspace from the pages you open most. It counts link opens on your own cards and, only if you turn on that source and grant the optional browser permission, reads your top sites or history. This data is processed on your device. With AI arrangement also on and your own Anthropic API key entered, the titles and addresses of the candidate pages are sent to the Anthropic API (api.anthropic.com) to group them. Turning the Auto dashboard off gives the browser permissions back.
  • Device sync. With Device sync on and set up, Linkhaven exchanges your workspaces, custom themes and uploaded images either with a Linkhaven sync server or with a WebDAV folder you enter (for example in your own Nextcloud). Everything is encrypted on your device before it is uploaded, with a key from your sync code or sync passphrase; neither is ever sent. A Linkhaven sync server stores only these encrypted files, a random sync id, hashes of the access tokens, each device's public key and encrypted name, when each device last synced (to the hour) and file sizes. Removing a device in the Sync tab deletes its access and re-encrypts your data with a new key. It keeps no access logs and cannot tell whose data it holds. Vaults no device used for 12 months are deleted, and "Disconnect and delete server data" removes yours at once. Your WebDAV login is kept only on your device.

Apart from the page titles and addresses sent for the AI arrangement, none of these requests upload your canvas content, templates, themes, imported bundles, gallery images, or usage statistics. The servers you connect to see your IP address and the address that was requested, as with any web request.

6. Imports and exports

If you choose to export data, Linkhaven creates files on your device only when you explicitly trigger the export action. If you choose to import data, Linkhaven reads the file you selected so it can restore that content into local browser storage.

These import and export actions are user-initiated. Linkhaven makes no automatic cloud backup; the only remote copy is the optional, end-to-end encrypted device sync described above, and only once you set it up.

7. Browser and store providers

Your browser vendor, extension store provider, or hosting provider may collect their own operational, telemetry, or transaction data under their own policies. That data handling is outside the Linkhaven application itself.

8. Changes to this policy

If Linkhaven's data handling changes materially, this page should be updated before or at the same time as the corresponding product release.

9. Contact

For privacy-related questions, use the contact information provided in the Linkhaven store listing, project repository, or release page where Linkhaven is distributed.