Privacy policy

Face data processed on your device

With your camera permission, Bukrah accesses front-camera images during a washing or Practice session. Images can include your face and surroundings. Apple Vision detects face rectangles; Bukrah uses the number of faces and the size of the largest rectangle to guide positioning. A bundled Core ML model produces a washing-confidence score, and a local counter checks for three separate washing movements. Bukrah does not use facial recognition to identify you, create a face template or identity profile, or extract facial landmarks, depth maps, or biometric identity embeddings. It does not verify identity or actual water contact.

Face data use and sharing

Camera images, temporary model inputs, face rectangles, face counts, face-size measurements, and washing-confidence scores are used only on your device to show the preview, guide positioning, count washing movements, and complete the alarm check. They are not sent to the developer, Apple, advertisers, analytics providers, or any other third party by Bukrah. Bukrah does not sell this data, use it for advertising or tracking, or use your camera sessions to train or improve a model. Vision and Core ML processing runs locally, without a developer-operated server.

Face data storage, retention, and deletion

Bukrah does not record video or write camera images, face rectangles, per-frame face counts, face-size measurements, model inputs, or confidence scores to files, databases, logs, or backups. Frames and model inputs exist only in temporary device memory while the camera preview and an in-flight analysis use them; their buffers are released or reused after use. Current numeric measurements and short-lived timing state are overwritten during the session and cleared when the session stops or the app becomes inactive. Capture stops at that point; an already-running analysis may finish, but its stale result is discarded. There is no retained face-image collection to delete and no server-side copy. A non-image wash-count and completion result can be saved in the local journal as explained below.

Local journal, settings, and sounds

Bukrah saves alarm settings, appearance preferences, session-recovery flags, free-trial status, imported audio clips, and up to 30 journal outcomes in its local app storage. Each outcome contains a random record identifier, date, a duration field, the number of completed washes, and a completion description; it contains no camera image, face rectangle, identity template, or per-frame score. Older outcomes are removed as new ones exceed the 30-record limit. Outcomes otherwise remain until you delete the journal in Settings or delete the app. Imported sounds remain until you delete them or the app. Settings persist until changed or the app is deleted. iOS may include these local records in device backups; Bukrah does not access your backups. You manage existing backups through Apple’s device and iCloud settings.

Diagnostics and voluntary support

Up to 100 app-lifecycle and alarm-timing diagnostic events are stored locally, with the oldest removed as new events arrive. They contain no images or per-frame face measurements. Settings > Copy alarm diagnostics copies them to your clipboard only when you choose that action. Bukrah does not automatically send them anywhere. If you paste them into a message or support service, that recipient and service receive the information you choose to share. Deleting the app removes its local diagnostic records.

Permissions and your choices

The camera starts only after you enable it and iOS grants permission. Manage camera and alarm permissions in your device’s Settings. You may use free Practice before setting an alarm and leave Practice using Done. Disabling camera access prevents washing checks. A real alarm has no in-app manual stop: iOS retains its own controls, and unfinished alarms can re-ring every minute, up to thirty times. Place your device securely away from water. Delete journal outcomes in Bukrah Settings and imported sounds in the sound library. Deleting the app removes its local app data; deleting or managing existing device backups is a separate action in Apple’s settings.

Apple services and purchases

Apple handles system alarms, permissions, and App Store purchases. Apple provides product prices and purchase-verification information to Bukrah through StoreKit. Bukrah does not receive your payment-card details. Restore purchases from Lifetime access in Settings. Apple’s purchase and optional device-diagnostic services are governed by Apple’s privacy policy. No face data is included in Bukrah’s StoreKit requests.

No accounts, advertising, or analytics

Bukrah has no user account, advertising SDK, analytics SDK, tracking, or developer-operated cloud service. Its camera processing is entirely on-device. There is no planned secondary use, disclosure, sharing, or off-device retention of your face data. If these practices change, this policy will be updated and any required permission will be requested before the new processing begins.

Support and privacy questions

For app, purchase, or privacy help, open a support question on GitHub. Issues are public: do not include camera images, personal information, payment details, or diagnostic records. GitHub handles information submitted through its service under its own privacy statement.

If the price does not load, check your connection and tap Try App Store again. If purchases are restricted, check Screen Time or device-management settings. If you already bought Lifetime Access, use Restore purchases with the same Apple Account. Practice remains free while a purchase is unavailable.