← puff

♡ privacy.txt

Privacy policy

Puff for Chrome · last updated 30 September 2026

The short version

Everything Puff knows stays in your browser on this computer. Puff has no server, no account, no analytics and no ads. It never sends anything anywhere.

What Puff notices

  • How long you have been active at your computer, using Chrome's idle signal (active, idle or locked).
  • How often you click, type and scroll on web pages. Only the counts and the time of the last one are kept, never which keys or what you clicked.
  • That you pressed save (⌘S / Ctrl+S) or submitted a form, and when you switch tabs. Only that it happened, never what was in it.

Puff uses these to decide when a break might be welcome and to show how long you have worked today.

What Puff stores when you take a break

When you choose take a break, Puff saves the title and address of the page you are on, and the optional note you write, so it can bring you back afterwards. This is the only time Puff reads a page title or address. You can clear it by finishing the break.

What Puff never reads

  • What you type, or anything on the pages you visit.
  • Tab titles and addresses, except the one page you save for a break.
  • Your browsing history, passwords, form contents or files.

Where it goes

All of the above is kept in Chrome's local extension storage (chrome.storage.local) on your computer. It is not sold, shared, transferred or sent to Puff's makers or anyone else. Removing the extension deletes it.

Puff stays quiet and collects nothing on video calls, payment and checkout pages, and in full screen.

Why Puff asks for its permissions

  • Access to websites: to show the cloud on the page you are working on and count clicks, typing and scrolling there.
  • tabs: to know which tab is active, and to read the title and address of the one page you save for a break.
  • idle: to know whether you are at your computer, including when you work outside the browser.
  • storage: to keep your settings and today's totals on this computer.
  • alarms: to check every thirty seconds whether it is a good moment for a break.

Changes and contact

If this policy changes, the date above changes with it. Questions: open an issue on GitHub.