FileFroggy
Cookies
Last updated 9 August 2026
This website sets no cookies. None. Not analytics, not advertising, not session cookies. There is no consent banner asking you to accept anything, because there is nothing to accept.
Why there is no consent pop-up
Consent banners exist because most sites load trackers that need your permission under the EU ePrivacy Directive, the UK PECR and similar rules. Those rules apply to storing or accessing information on your device for purposes that are not strictly necessary.
This site does none of that. It is a static page: some HTML, one stylesheet, a few images and videos, all served from this domain. There is no tag manager, no advertising network, no embedded video player phoning home, no web font pulled from a third party. Nothing here needs your consent, so nothing asks for it.
The small notice at the bottom of the home page is informational. It tells you the site is clean and then goes away. It does not gate the content and there is no “reject” path, because there is nothing to reject.
The one thing this site stores
When you dismiss that notice, the site writes a single value to your browser's
localStorage so it does not reappear on your next visit:
| Name | Type | Purpose | Expires |
|---|---|---|---|
rl-notice-dismissed |
localStorage | Remembers that you dismissed the notice, so it is shown only once. | Until you clear browser storage |
Its value is the character 1. It contains no identifier, is never read by anyone
but your own browser, and is never transmitted to any server. Under both the ePrivacy Directive
and PECR this qualifies as strictly necessary for a function you explicitly requested — you
asked the notice to go away — and so is exempt from the consent requirement.
You can remove it at any time by clearing site data in your browser. Nothing breaks; the notice simply appears once more.
Third-party content
There is none. Every stylesheet, image and video on this site is served from this domain, so no other company learns that you visited. Outbound links to GitHub are ordinary links — nothing is loaded from GitHub until you choose to click through, at which point that service's own policies apply.
Server logs
Cookies are not the only way a site can see you. This one is hosted on GitHub Pages, and GitHub's servers process the technical information any web server needs to deliver a page — your IP address, the page requested, your user-agent. That is a hosting-layer function rather than a cookie, we do not receive or analyse those logs, and it is covered in more detail in our privacy policy.
The application
The FileFroggy Mac application is not a web page and uses no cookies. It stores its ledger in a local database on your Mac and transmits nothing. See the privacy policy for exactly what it records and how to delete it.
If this ever changes
If this site ever adds analytics or any non-essential storage, this page will be updated before it ships and a real consent mechanism will be added — one that works properly, where declining is as easy as accepting. The revision history of this page is public in the project repository, so that promise is checkable rather than merely stated.