Hopwatch

Privacy policy

Hopwatch doesn't collect your data. There's no account, no server of ours, no analytics, no tracking and no ads. Your time stays on your phone, so this page is short.

Last updated 2 October 2026

Who's responsible

Urbs UG (haftungsbeschränkt) publishes Hopwatch and runs this website. It's the controller under the GDPR:

Urbs UG (haftungsbeschränkt)
Stellinger Chaussee 19
22529 Hamburg
Germany

Email: info@urbs.one. More in the Impressum.

Your entries stay on your phone

Your jellies, time entries and settings are stored in a database inside the app on your phone. They never reach us, and we couldn't see them if we wanted to.

If your phone backs up to iCloud or Google, the backup includes Hopwatch's data. That follows your backup settings and Apple's or Google's terms. Deleting the app deletes its data from the phone.

Export and restore

Export JSON in Settings creates a file with your data and opens the share sheet. Where the file goes is up to you, and we don't get a copy. Restore from Export reads only the file you pick.

Notifications and Live Activities

If you allow notifications, Hopwatch schedules its reminders on the phone itself. Nothing goes through a push server. The Live Activity on your Lock Screen is drawn on the phone too.

Apple Intelligence

On iPhones with Apple Intelligence, Hopwatch uses Apple's on-device model, through the Foundation Models framework, to suggest looks for jellies, write the week summary and read entries you type. The model runs on your iPhone. Hopwatch sends none of this anywhere.

App updates through Expo

This is the one time Hopwatch itself goes online. When you open it, it asks Expo's EAS Update service whether there's a newer version of its code, like a fix or a small improvement, and downloads it if there is. Expo is a service of 650 Industries, Inc. in the USA.

The request contains:

Like any request on the internet, it also shows Expo your IP address. It contains none of your jellies or entries.

We do this to ship fixes quickly and keep the app working, which is our legitimate interest (Art. 6(1)(f) GDPR). Expo handles the data for us as a service provider. According to its privacy policy, Expo complies with the EU-U.S. Data Privacy Framework for data that reaches the USA. Details are in Expo's privacy policy.

App Store and Google Play

You get Hopwatch from Apple's App Store or from Google Play, and they process data for that under their own privacy policies. If you've allowed your phone to share analytics or crash reports with app developers, Apple or Google may show us aggregated statistics and crash reports. They don't tell us who you are.

Email

If you write to us, we use your address and message to answer you (Art. 6(1)(b) and (f) GDPR). We delete them once the conversation is done, unless the law makes us keep them.

This website

This website sets no cookies, has no analytics and loads nothing from other servers, not even fonts. It runs on a server we rent from netcup GmbH in Germany. Like most web servers, it writes an access log of each request: your IP address, the time, the page, and what your browser sends along, such as its name and language. We use the log only to keep the site running and secure (Art. 6(1)(f) GDPR) and delete it after at most 15 days.

Your rights

You can ask us what data we have about you, and have it corrected, deleted or restricted, or get a copy to take elsewhere. You can object to processing that relies on our legitimate interest. Write to info@urbs.one. For the data in the app you don't need us. You can see, export and erase it yourself at any time.

You can also complain to a data protection authority. Ours is the Hamburg Commissioner for Data Protection and Freedom of Information (Der Hamburgische Beauftragte für Datenschutz und Informationsfreiheit).

Changes

If Hopwatch ever starts handling data differently, we'll update this page before that version ships and change the date at the top.