Simas Razinskas

Simple Pomodoro

Simple Pomodoro — Privacy Policy

Simple Pomodoro is a free iPhone timer with no accounts, no ads and no in-app purchases. It collects no personal data of any kind. There is nothing to disclose here because there is nothing being gathered: the app makes no network requests at all.

Effective:

Data the app collects

None. Simple Pomodoro does not collect, transmit or share personal data. It contains no analytics, no crash reporting and no third-party SDKs, and it never contacts a server — the app works entirely offline.

Data stored on your device

The app stores only what it needs to run, and it stores it locally in its own app container on your device:

  • your timer settings
  • your history of completed focus sessions

Where that data goes

Nowhere. On-device data is never uploaded, never sent to the developer, and never sold or shared with anyone. No one but you can read it.

Notifications and Live Activities

Simple Pomodoro schedules local notifications so you are alerted when a focus session or a break ends, and it uses Live Activities to show the countdown on the Lock Screen and in the Dynamic Island. Both are handled locally by iOS on your device; neither sends anything to a server.

No accounts, no tracking, no ads

There is no login, no user account and no identifier that follows you. The app shows no advertising, contains no in-app purchases, and does no tracking across apps or websites.

Children

The app is safe to use at any age. Because it collects no data at all, it collects nothing from children either.

Deleting your data

Deleting Simple Pomodoro from your device deletes all of its data with it. There is no server-side copy to request, export or erase.

Changes to this policy

If the app ever changes in a way that affects this policy, this page is updated before that version ships, and the effective date above changes with it.

Contact

Questions about this policy? Email Simas Razinskas, the developer of Simple Pomodoro:

Have a system that has to work?

Book a call and we'll map it out: what it should do, where it will break, and the smallest version worth building first.