How the core tools work
Our password and 2FA tools are intended to run client-side. Sensitive values such as passwords, secrets, and generated codes are processed inside your browser and are not intentionally transmitted to fbuff servers as part of the core tool flow.
Browser storage and device data
We may store limited on-device preferences, such as recently opened tools or future consent settings, using browser storage technologies like localStorage. This helps the interface remember lightweight preferences without creating an account.
You can clear that information at any time through your browser settings. Clearing local storage may reset tool preferences and recommendations.
Search, external links, and optional integrations
Some discovery features can connect directly from your browser to third-party services if those integrations are enabled by the site operator, such as a custom search provider. When that happens, the third party may receive technical information like your IP address, browser details, referrer, and the search query you submit.
External links, including GitHub and any third-party resources, are governed by the privacy practices of those services once you leave fbuff.
Legal and regional compliance
fbuff is intended to support privacy obligations commonly associated with the GDPR, UK GDPR, ePrivacy rules, the Swiss FADP, and similar privacy frameworks. Where regional laws require notice or consent before non-essential tracking technologies are used, our policy is to obtain that consent before enabling those technologies.
Your choices
You may stop using the tools at any time, clear browser storage, and manage cookies or similar technologies through your browser. If you deploy or customize this project, you are responsible for updating this policy to reflect your own data flows and contact details.