Roundbell privacy policy

Last updated 29 October 2026. Roundbell is made by Onibaku (admin@onibaku.co.uk).

Where it runs

Roundbell runs entirely on your Android phone and, if you install it there, your Wear OS watch. There's no Onibaku account and no Onibaku server.

What it stores

Your saved workouts, your cue settings and whether you've bought Pro are kept on your device only, and are excluded from Android backups. Clear them by clearing the app's storage or uninstalling it.

Phone and watch sync

Saved workouts are copied between your own phone and watch using Google's Wearable Data Layer, the system service Wear OS uses to connect your devices. When a workout finishes on the watch, its name and start and end time go to your phone so it can be logged to Health Connect if you've turned that on. Nothing is sent to us.

Health Connect (Pro, optional)

If you turn on Health Connect logging, Roundbell asks for permission to write exercise sessions. After each finished workout it writes one session: the workout's name, type (high-intensity interval training) and its start and end time. Roundbell doesn't read anything from Health Connect. The data stays in Health Connect on your phone; you can delete it there or revoke the permission at any time.

Custom sounds (Pro, optional)

If you choose your own bell sound, Roundbell keeps permission to read that one file and plays it on your device. It isn't copied or uploaded.

Payments

Pro is bought through Google Play, so Google handles the payment under its own privacy policy. We receive only the anonymised sales reports Google Play gives every developer.

What it doesn't do

• No account, sign-in or contact details.
• No ads, analytics, crash reporting or tracking SDKs.
• No microphone, location, contacts, camera or body-sensor access.

Questions: admin@onibaku.co.uk.