Hi everyone, this is my first guide posted on the forum. I wanted to share a project I came across while researching bookmark synchronization for browsers without built-in sync, and I hope it can be useful to others here. If I missed anything, misunderstood any aspect, or formatted something incorrectly, I would really appreciate any feedback or suggestions.
I currently use hardened Chromium-based browsers such as Helium Browser and Cromite on both Linux and Android. These browsers deliberately avoid vendor-managed synchronization services, which leaves bookmark syncing as an unsolved usability gap.
During this research, I discovered floccus (https://floccus.org/), and I would like to share it here for discussion and evaluation by the wider Privacy Guides community.
floccus provides bookmark synchronization without relying on centralized infrastructure, browser vendor accounts, or proprietary ecosystems.
What floccus Does (and What It Does Not Do)
floccus is intentionally minimal by design.
It is not a bookmark manager and does not introduce its own interface for organizing or editing bookmarks. All bookmark management is done using the browserâs native tools.
floccus acts solely as a synchronization layer:
- It synchronizes the browserâs native bookmarks
- It does not alter how bookmarks are organized locally
- Once synchronization is complete, it stays out of the way
This narrow scope reduces complexity and limits unnecessary data processing.
The Synchronization Model
To synchronize bookmarks across devices, floccus relies on a user-chosen backend that all devices can access. This backend acts as a neutral intermediary and is not operated by the floccus project.
This design places trust decisions explicitly in the hands of the user.
Available Backends and Privacy Implications
WebDAV
WebDAV is one of the most privacy-aligned and flexible options.
It is widely supported by self-hosted servers, NAS devices, and privacy-oriented cloud providers. This allows users to retain full administrative control over where bookmark data is stored.
When combined with HTTPS and app-specific credentials, WebDAV offers a relatively simple and auditable synchronization setup.
Git
floccus also supports synchronization via Git repositories.
In this model, bookmarks are stored as files inside a Git repository, which can be hosted on a self-managed Git server or any trusted Git provider.
This approach offers:
- Full transparency and inspectable history
- Offline-first workflows
- Easy backup, versioning, and migration
- No always-on synchronization service
It is particularly suitable for technical users who already rely on Git-based workflows.
Linkwarden
floccus can synchronize bookmarks via Linkwarden.
Linkwarden is an open-source web application that provides bookmark management through a web interface. It can be self-hosted or used via a hosted service.
This option trades some simplicity for convenience and centralized access.
Nextcloud Bookmarks
Another supported backend is Nextcloud using its Bookmarks app.
This option integrates naturally for users who already operate a Nextcloud instance and want to keep bookmark data within an existing self-hosted ecosystem.
floccus on Android
floccus is also available as a standalone Android application and is currently in Open Beta.
The app is available via:
- Google Play
- IzzyOnDroid
- F-Droid
Due to platform limitations, the Android app does not integrate directly with mobile browser bookmark systems. Instead, bookmarks are synchronized and managed within the floccus app itself.
Users can:
- Share links from browsers or other apps into floccus
- Create folders and search bookmarks inside the app
- Open bookmarked links in their preferred browser
This design respects Androidâs security boundaries while still enabling cross-device bookmark access.
Privacy Policy Summary
floccus publishes a narrowly scoped and explicit privacy policy that reflects its minimal design.
Data provided by the user
- Credentials for third-party services (WebDAV servers, Git repositories, Linkwarden, or Nextcloud)
- Access to local bookmarks strictly to perform synchronization
- Any chosen backend will have access to the bookmark data stored on it
Data collected by floccus
- A local debug log of synchronization actions
- Logs remain on the userâs device
- Logs are only shared manually at the userâs discretion
Data sharing
- No bookmark data, credentials, or logs are received by the floccus authors or publisher
- floccus does not operate servers or act as a data processor
- Data handling is entirely determined by the selected backend
Closing Note to the Privacy Guides Community
I am sharing floccus here primarily to gather feedback and discussion from the Privacy Guides community.
If considered appropriate, floccus might also be worth evaluating as a potential recommendation on the Privacy Guides website for users of de-Googled or hardened browsers. That said, I am not familiar with the recommendation or review process, and this is merely a suggestion for forum moderators and site maintainers to consider if it aligns with existing criteria.
Conclusion
floccus addresses a narrowly defined problem with a transparent and decentralized architecture.
By separating synchronization from bookmark management and avoiding centralized services, it offers a practical solution for users who intentionally avoid vendor-managed sync while still requiring cross-device usability.
When paired with user-controlled backends such as WebDAV, Git, Nextcloud, or Linkwarden, floccus aligns well with Privacy Guides principles of user control, minimized trust, and transparency.