Privacy stance (practical, not legal)

Link Garden exists partly to reduce dependence on large platforms and closed ecosystems. The data model is simple: Markdown files and YAML frontmatter you can inspect, back up, and move without vendor lock-in.

Publishing is your choice. You can keep everything local, export only public items, or include broader scopes when you explicitly decide to do that.

The safest default is local-only use with private visibility. If you publish, treat it as public internet content and avoid sharing anything sensitive.

Do not publish private bookmarks publicly. If a link, note, or title would be risky when indexed or shared, keep it in private scope.

Practical privacy tips

• Keep `default_visibility: private` in `config.yaml` unless you intentionally want a broader default.
• Use `link-garden export --scope public` for anything that may be shared.
• Only use `--scope all` with `--dangerous-all` when you explicitly need a private backup export.
• Run `link-garden doctor` before publishing exported HTML.
• Keep `serve` bound to localhost unless you have a reverse proxy, auth, TLS, and firewall controls.
• Assume bookmark titles and notes can reveal sensitive context even if URLs look harmless.
• Store backups in private locations; do not sync private exports to public buckets.
• Review old bookmarks periodically and archive or redact entries you no longer want exposed.