Art Pomodoro

Privacy Policy

Last updated: August 18, 2026

No personal data collection

Art Pomodoro does not collect, transmit, or sell any personal data. The extension has no user account, no server of its own, and no analytics or tracking tool (no Google Analytics, no pixel, no telemetry).

Data stored locally

The only data saved by the extension is:

  • Journal entries (text written during breaks, linked to the artwork shown and its date);
  • Timer state (current phase, any custom duration);
  • Break-screen display preferences (e.g. whether the music player is collapsed).

This data is stored only via the chrome.storage.local API, on the user's own device. It never leaves that device, is never sent to any server, and is deleted if the user uninstalls the extension or manually clears their journal entries.

External services used

During a break, the extension makes two kinds of network calls, both to public third-party services, without authentication or any user identifier:

  • The Metropolitan Museum of Art — Collection API (collectionapi.metmuseum.org), to fetch a random artwork and its metadata (title, artist, image, description). See the Met's privacy policy.
  • Wikimedia Commons (upload.wikimedia.org), to stream a public-domain classical music recording. See the Wikimedia Foundation's privacy policy.

These requests carry no information identifying the user beyond what any browser sends by default to any website (IP address, user agent).

Artwork and music licensing

  • Artworks come from the Metropolitan Museum of Art's public-domain collection (Open Access).
  • Classical music tracks come from Wikimedia Commons. Most are Musopen recordings released under a CC0 (public domain) license. Two Mozart recordings, credited to the "European Archive," are public domain through the expiry of neighboring rights in the European Union rather than an explicit CC0 dedication — they remain free to use.

Why the extension asks for broad permissions

  • host_permissions: <all_urls> and scripting: the break is triggered by a timer running in the background, independently of whichever tab is active at that moment. The extension therefore needs to be able to display the break screen over any site, on whatever tab happens to be active — it is never a click on that specific site that triggers it.
  • alarms: to reliably schedule the end of work and break phases, even if the browser has been idle in between.
  • storage: to save the timer state and journal entries locally (see above).

None of these permissions are used to read, modify, or transmit the content of visited pages — the extension only overlays its own break screen on top.

Contact

For any question about this policy, contact: angela.binot.pro@gmail.com