Privacy policy

Last updated 9 August 2026

1. Who is responsible

FileFroggy is an independent software project. The project maintainer is the data controller for the limited processing described below.

The reliable way to reach us about anything in this policy is through the project's issue tracker at github.com/DomTheDeveloper/RecentLedger/issues. For matters you would rather not discuss in public, open an issue asking for a private contact and we will provide one.

2. The website

What this site does not do

• No cookies are set. Not for analytics, not for advertising, not for sessions.
• No analytics service is loaded — no Google Analytics, Plausible, Fathom or equivalent.
• No advertising, remarketing pixels, session recording or fingerprinting.
• No fonts, scripts, images or media are loaded from third-party servers. Every asset is served from this site, so no outside party learns that you visited.
• No account, no sign-up, no newsletter form.

Local storage

If you dismiss the notice at the bottom of the page, a single flag is written to your browser's localStorage so the notice does not reappear. It contains no identifier and is never transmitted anywhere. Clearing your browser storage removes it. This is strictly necessary for a function you requested, so it does not require consent.

Hosting and server logs

This site is hosted on GitHub Pages. Like any web server, GitHub's infrastructure processes technical information necessary to deliver a page — including your IP address, the page requested, and your browser's user-agent string. This happens at the hosting layer and is outside our control; we do not receive, store or analyse those logs.

GitHub's handling of that data is described in the GitHub Privacy Statement, and specifically in their data collection notice for GitHub Pages. The lawful basis for this processing is our legitimate interest in serving and securing the website.

Links to other sites

Pages here link to GitHub. Once you follow such a link you are on that service and its own privacy policy applies. We have no control over, and take no responsibility for, how other sites handle your data.

3. The application

What the app stores, on your machine

• File paths, names and folders you have interacted with.
• What happened and when — created, downloaded, opened, edited, saved, renamed, moved, copied, trashed, restored, deleted.
• For downloaded files, provenance recorded by macOS: the source URL, the referring page, the application that fetched it, and for email attachments the sender's name and address.

This lives in a SQLite database inside your user Application Support folder. It is covered by FileVault if you have it enabled, and by your Time Machine or other backups if those include that folder.

What the app does not do

• No account, sign-in, or user identifier.
• No telemetry, crash reporting or usage analytics.
• No network transmission of your file activity. The ledger is never uploaded, synced or shared with us or anyone else.
• No reading of file contents. FileFroggy records that a file changed, not what is inside it.

Retention and deletion

You choose how long history is kept, and entries older than that are deleted permanently. Deleting the application's database removes the entire ledger. We hold no copy, so there is nothing for you to request from us and nothing for us to delete on your behalf.

Export

Exporting a ledger to CSV, JSON or Markdown writes a file wherever you choose. Once exported, that file is an ordinary document under your control — and worth handling carefully, since it describes your working habits in detail.

4. If you contact us

If you open an issue or otherwise write to us, we necessarily hold what you send — your message and whatever identity you contacted us from — for as long as needed to deal with it. Issues opened on GitHub are public by design, and GitHub processes them under its own policy. The lawful basis is our legitimate interest in answering people who contact us.

5. Your rights

Depending on where you live, you may have rights to access, correct, delete, restrict or object to processing of your personal data, and to data portability. Under the UK and EU GDPR you also have the right to complain to your local supervisory authority. Under the CCPA and similar US state laws you have rights of access and deletion, and a right not to be discriminated against for exercising them.

In practice these rights have very little to attach to here: we operate no database of users, run no tracking, and never receive your file activity. If you have contacted us, you can ask what we hold from that correspondence and ask us to delete it.

We do not sell or share personal information, and never have. There is no opt-out to offer because there is nothing to opt out of.

6. Children

FileFroggy is a professional utility and is not directed at children. We do not knowingly collect personal information from anyone, including children under 13 (or 16 where that is the applicable age).

7. Changes to this policy

If this policy changes, the revised version will be published here with a new date at the top. Because the site is version-controlled in public, the complete history of this document is inspectable in the project repository — you do not have to take our word for what it used to say.

← Back to FileFroggy