Okita privacy policy

Effective 2026-11-12. Last updated 2026-11-12. Covers Okita for Android (com.aripone.okita) and Okita for iPhone.

Okita is an alarm clock made by Aripone LLC ("we"). This policy explains what the app stores, what leaves your phone, and why. Where the Android and iPhone apps differ, it says so.

Your alarms, wake-up workflows and settings are kept on your phone. There is no account and there are no ads. On Android, crash reports and usage stats are off unless you turn them on, and barcode scanning uses Google's ML Kit, which sends Google basic diagnostics. The iPhone app sends nothing over the network. Its only copy off the phone is your own iCloud or computer backup.

What the app keeps on your phone

Your alarms and their wake-up workflows (steps such as missions, check-ins and spoken messages), with their labels, tags and settings.
Your wake-up history and missed-alarm history.
NFC tags and barcodes you register for the scan missions. The app stores the tag's ID or the code's text, never a photo.
Sounds you pick. The app saves which file you chose, and keeps a copy so the alarm can ring after a restart, before you unlock the phone.
Plugins you install (small wake-up games) and workflow templates you save.

None of this is sent to us. If you uninstall the app, your phone deletes it.

What leaves your phone

What	Where it goes	When
A backup of your alarms, workflows, settings, wake-up and missed-alarm history, registered tags and codes, and installed plugins	On Android, your own Google account, through Android's built-in backup. On Android 9 and later, if you have a screen lock, Android encrypts the backup with it before it leaves the phone. Android also uses this backup when you move to a new phone. On iPhone, your own iCloud or computer backup, through iOS's backup. We cannot see either one.	Whenever your phone backs itself up. You can turn this off in your phone's Settings (Android: Backup; iPhone: your name > iCloud > iCloud Backup).
Crash reports (Android only): what the app was doing when it crashed, the phone model and system version, the app version, and a random ID for this installation	Firebase Crashlytics, a Google service that collects crash reports for us. Reports are sent over HTTPS, and Google keeps them for 90 days. The iPhone app sends no crash reports.	Only if you turn on Settings > Share crash reports and usage stats, which stays off until you do. Even then, a report is sent only when the app crashes or stops responding, when a plugin game fails (with the plugin's ID, its version and the reason), and once each time the app starts. Crash data from before you turn the switch on is deleted, not sent. Reports contain no alarms, labels, messages or other text you typed. They can include a plugin's ID and version. For a plugin you made or were sent, the author chose them. You can turn the switch off at any time.
Usage stats (Android only): which screens you open that an alarm was created, edited, switched or deleted, with whether it repeats, whether it has a wake-up routine, which mission types and which kind of sound it uses (never its time or label) how a ring ended, or why one was missed which plugins were installed, tested or removed your answers to permission requests when you finish setup when a plugin fails the app events Google Analytics records on its own a rough location that Google works out from your IP address the phone model, the app version and a random ID for this installation	Google Analytics for Firebase, which counts them for us. They are sent over HTTPS, and no advertising ID is used. They can include a plugin's ID and version. For a plugin you made or were sent, the author chose them. The iPhone app sends no usage stats.	Only if you turn on the same switch, Settings > Share crash reports and usage stats. You can turn it off at any time.
Scanner diagnostics (Android only): device and system details, the app's name and version, performance data such as how long a scan took, error codes, and a random ID for this installation	Google ML Kit, the barcode reader that runs on the phone. Okita uses it only to read barcodes, not text. They are sent over HTTPS. It sends no images and nothing from the codes you scan. Both stay on the phone. The iPhone app reads codes with Apple's built-in camera reader and sends nothing.	When you register or scan a barcode or QR code, or import a plugin or workflow by QR code. There is no switch to turn this off.
Paired Wear OS watch (Android only): upcoming alarm times and labels, the ringing alarm, and spoken messages	Your watch, through Google Play services. We receive none of it.	While a Wear OS watch is paired with your phone.

We do not sell data, share it for advertising, or build profiles. The app does not use the advertising ID.

Spoken messages

Workflow steps that speak text use your phone's text-to-speech engine, which is usually Google's. The app hands the text to that engine on the phone. What the engine then does with it is up to the company that makes the engine.

Plugins

Plugins are small games written in JavaScript. They run in a locked-down web view with no internet access and no access to your files, contacts or other apps, and they see only what the alarm passes them, such as the difficulty level. We make the plugins in the app's catalog, and they ship inside the app, so browsing or installing them sends nothing.

On Android you can also make your own plugins and share them with other people by QR code or file. That happens between your phone and theirs, and we never receive them.

To report a plugin, go to Settings > Plugins, tap ⋮, then Report. Okita opens your own email app with the report filled in: the plugin's name, version, author, ID and code fingerprint, plus your reason and your note. You see all of it and decide whether to send it. If you do, we receive your email address and what the email says, and we use them only to look into the report and reply to you. Okita itself sends nothing.

Permissions

These are the Android names. The iPhone app asks only for alarms, notifications, the camera, NFC and your music library, for the same reasons, and has no power-off guard.

Alarms and reminders, and full-screen notifications: to ring at the exact time and show the alarm screen over the lock screen.
Notifications: to show the ringing alarm, upcoming alarms and check-in questions.
Run at start-up: to set your alarms again after the phone restarts or the time zone changes.
Foreground service, wake lock, turn screen on, vibrate, change audio settings: to keep the alarm sounding, at the volume you chose, and the screen on until you stop it.
Music and audio (optional): so you can pick a song from your phone as the alarm sound. The app reads only the list of audio files and the file you choose.
Camera (optional): to read a barcode or QR code for the scan mission. Pictures are processed on the phone and never saved or sent.
NFC (optional): to read an NFC tag for the tag mission. Only the tag's ID is used.
Internet: for the crash reports and usage stats if you turn them on, and for the scanner diagnostics, as described above. The iPhone app has none of these.
Display over other apps (optional): so the alarm screen can open when notifications are blocked.
Do Not Disturb access (optional): so an alarm can ring through a Do Not Disturb mode that would otherwise silence it.
Accessibility service "Power-off guard" (Android only, optional): off until you agree to it and turn it on.
- While a mission alarm rings, it closes the power menu and other system pop-ups.
- While a mission alarm rings or a wake-up check runs, it also closes Okita's own App info, notification settings and uninstall screens, its launcher menu and its Pause app confirmation, then goes back to the alarm or check-in screen.
- It sees the package and class names of windows that open, and the title of the Pause app confirmation.
- During a run, when you long-press an app icon in the Pixel or AOSP launcher, it compares that icon's name with its own app name, so it can close its own management menu before Pause app can run. It also compares the app name supplied when you tap a Recent apps icon, on Pixel versions that include it in the event. These icon names are not logged, saved or sent.
- Only during a mission alarm or wake-up check, it looks at Settings and package-installer screens to find this app's page.
- During a run, when you tap a Pixel or AOSP launcher control, it checks only the app-name header of the Recent apps menu, so it can close this app's task menu before Pause app runs.
- It does not read task snapshots or the launcher's app list, and it does not retrieve Digital Wellbeing's screen content. Screen text is compared on your phone and is never logged, saved or sent.
- Other apps' pages and this app's pages outside a run are left alone.
- You can turn the guard off at any time in Settings > Accessibility, even during a run.

Children

Okita is for adults 18 and over. It is not made for anyone under 18, and we do not knowingly collect data from them. The app never asks for a name, email address, account or contacts. What leaves the phone is listed above.

Your choices

Turn off backup in your phone's Settings, or delete the backup from your Google account (Android) or from iCloud or your computer (iPhone).
Uninstall the app to delete everything it stored on the phone.

Changes

If this policy changes, we will update this page and its effective date. We will also mention big changes in the app's release notes.

Contact

Send questions or requests to Aripone LLC at support+okita@aripone.com.