Privacy Policy

03 — Culmo

Culmo

Culmo (Google Play package com.mananbohra.culmo) is a workout logger built around a simple promise: your data stays on your device. This section explains what Culmo stores, what it does not do, and the control you have.

What Culmo stores (locally, on your device)

To function as a workout logger, Culmo stores the following in a private database that only Culmo can access:

• Workout logs: exercises, sets, reps, weights, rest times, RPE, notes, and dates.
• Body measurements: the values you choose to record (e.g. body weight, body-fat %, circumferences) and their dates.
• Templates and exercise library, including any custom exercises you create.
• Profile and preferences: an optional display name, an optional profile photo you select, unit choices (kg/lbs, etc.), theme, and timer/sound settings.

This information never leaves your device unless you explicitly export or share it (see below).

Permissions Culmo requests, and why

• Notifications — to show the active-workout notification and rest-timer alerts.
• Foreground service / ignore battery optimizations — only while a workout is active, so the rest timer and workout tracking keep running reliably when the screen is off or the app is in the background. You can revoke this at any time in system settings.
• Photos / files — only when you choose to set a profile picture, or import/export a backup file. Culmo accesses only the file you pick.
• Keep screen on — an optional convenience during workouts; off unless you enable it.
• Health Connect: write exercise — only if you turn on Health Connect in Settings, so Culmo can add your finished workouts there. Culmo requests no permission to read health data.

Culmo does not request location, contacts, microphone, or camera-for-capture permissions.

Exporting and sharing (only when you ask)

Culmo lets you export your data (for example, a JSON backup or summary) and share it using your device's standard share sheet. This happens only when you initiate it, and the data goes wherever you choose to send it — for example, copying a workout to paste into an AI assistant. Once shared, that copy is outside Culmo's control.

Health Connect (optional)

Health Connect is an Android service that stores health and fitness data on your device and lets the apps you choose share it. Culmo's Health Connect sync (available from Culmo 1.0.5) is off by default; you turn it on in Settings → Connected apps, and Android asks for your permission first.

• What Culmo writes: for each finished workout, one exercise session — the type ("strength training"), the workout's name, and its start and end time, plus the technical details Health Connect needs (an internal record ID so Culmo can update or remove the session, and the device type). If you choose "Add past workouts", the same is written for your earlier finished workouts.
• What Culmo never writes: sets, reps, weights, notes, personal records, body measurements or photos.
• What Culmo reads: nothing. Culmo only asks for permission to write exercise data and never reads data from Health Connect.
• Who can see it: data in Health Connect is managed by Android. Other apps can read it only if you grant them permission in Health Connect.
• Keeping it in sync: deleting a workout in Culmo (or using Erase all data) also removes the session Culmo added for it while sync is on.
• Turning it off: switch it off in Culmo's Settings, or remove Culmo's permission in Health Connect. Sessions already added stay in Health Connect until you delete them there (Health Connect → Data and access).

Culmo does not send Health Connect data to us or to any third party, and does not use it for advertising.

Deleting your data

Because everything is local, you have direct control:

• Delete individual workouts, measurements, templates, or exercises within the app.
• Use Erase all data in Settings to wipe Culmo's database from your device.
• Uninstalling the app also removes its local data. Sessions Culmo added to Health Connect are kept by Health Connect; delete them there if you no longer want them.

Culmo keeps your data on your device for as long as the app is installed or until you delete it; we hold no copy and therefore retain nothing on our side.

Purchases (Culmo Pro)

Culmo Pro is an optional paid upgrade. Purchases are processed by Google Play and RevenueCat (a billing-infrastructure provider). To validate a purchase and let you restore it after a reinstall or on a new device, an anonymous app-user identifier and your purchase receipt are shared with RevenueCat. No workout logs, body measurements, exercise data, name, or photo are ever sent — RevenueCat only ever receives the anonymous identifier and your subscription status. Google Play and RevenueCat handle billing data under their own privacy policies.

Children's privacy

Culmo is not directed at children under 13 and does not knowingly collect data from them.

Future cloud features

Culmo is designed to optionally share aggregated daily summaries (e.g. total volume, consistency score) with a companion productivity app ("The Brain"). This feature is not active in this version — no data is transmitted. If it is enabled in a future release, this policy will be updated to describe exactly what aggregated values are sent, and it would never include your individual sets, reps, or exercise-level logs.

04 — Alarm Clock: Heavy Sleepers

Alarm Clock: Heavy Sleepers

Alarm Clock: Heavy Sleepers (Google Play package com.mananbohra.alarmate) is an alarm clock built around missions: small tasks, like a math problem, a QR code to scan or a phrase to say out loud, that you complete to prove you're actually awake. Like everything this studio builds, it is local-first: your alarms, streaks and stats live on your phone, not on a server.

What Alarm Clock: Heavy Sleepers stores (locally, on your device)

To work as an alarm clock, the app keeps the following in private app storage that only it can access:

• Alarms and their settings: times, repeat days, labels, sounds, volume, snooze rules, and each alarm's mission configuration.
• Wake history and streaks: which mornings you woke on time, snoozes, and the statistics built from them.
• Mission content you add: flashcard decks you import, phrases you set for the voice mission, a registered QR or barcode value, an NFC tag identifier, a name and two magnetic-field readings for each spot you register in Magnet Hunt, and, for the photo mission, a small mathematical fingerprint (a "perceptual hash") of your chosen scene. The photo mission never stores a photo. Only the fingerprint is kept; it cannot be turned back into an image.
• Audio files you import as custom alarm sounds, copied into the app's own storage so your alarm still rings if the original file moves.
• Preferences and routines: theme, morning-routine items and any journal lines you write there, reminder settings, and similar choices.
• A local reliability log: timestamps of when alarms were scheduled and when they actually rang, kept on your device to power the in-app Reliability Score, and any "My alarm didn't ring" reports you file (see below).

None of this leaves your device unless you export or share it, apart from your alarms in your phone's own backup (see Backups below).

Permissions Alarm Clock: Heavy Sleepers requests, and why

• Alarms & reminders (exact alarms): to ring at exactly the time you set. This is the core of the app.
• Notifications and full-screen alerts: to show the ringing alarm over your lock screen.
• Run at startup: to re-arm your alarms after your phone restarts.
• Foreground service, wake lock and vibration: to keep the alarm, and the optional gentle wake-up sound before it, playing reliably until you dismiss it.
• Camera: only for the camera missions (QR Code, Photo, Colour Hunt, Big Smile, Make This Face and Dance Party), while you set one up or test it, while that mission is on screen, and in the camera test under Settings, Diagnostics & developer tools. Camera frames are processed on your device (by Google's ML Kit in four of these missions, see below) and are never stored or uploaded.
• Microphone: only for the Voice mission, and only while it is listening. Speech is handled by your device's own speech recognition service (typically Google's); on some devices that service may process audio in the cloud under Google's own policies. Alarm Clock: Heavy Sleepers itself never records, stores, or transmits audio.
• NFC: only for the NFC Tag mission; the scanned tag's identifier is compared on your device against the one you registered.
• Network access: only for the two Google libraries described below: so Firebase Crashlytics can check in when the app starts and send a crash or error report, and so Google's ML Kit can send its technical diagnostics. The app makes no other network calls of its own; the system speech recogniser used by the Voice mission may use the network under Google's policies, as noted above.

Some things need no permission at all. Missions that ask you to move, such as Shake, Squats, Simon Says, Don't Spill It, Room Sweep and Magnet Hunt, read your phone's motion and magnetic-field sensors live; nothing is recorded except the magnetic-field readings for the spots you register in Magnet Hunt, listed above. When you import an alarm sound or a flashcard deck, or restore a backup, you choose the file in Android's own file picker, and the app accesses only the file you pick; it has no access to the rest of your photos or files. Exporting a backup hands the file to Android's share sheet, and it goes only to the app you choose there.

Alarm Clock: Heavy Sleepers does not request location or contacts.

Crash reporting

Alarm Clock: Heavy Sleepers sends crash and error reports to one service, and only this one:

• Firebase Crashlytics: if the app crashes or hits an unexpected error, a report is sent to Google so we can find and fix the bug. A report contains the technical details of the failure (what the code was doing), your device model, OS version, and a random installation identifier. It never contains your alarms, wake history, or anything you typed. Crashlytics also contacts Google each time the app starts, to register that random installation identifier and open a session with the app version and device details, so that a later report can be matched to them. Crash reporting is turned off in development builds.

Crash reports are sent encrypted, are not linked to your identity, and are not used to track you. There is no usage-analytics SDK in Alarm Clock: Heavy Sleepers (the app does not send "feature used" events anywhere; the only other technical reporting is ML Kit's, described next) and no advertising SDK, so no advertising ID is collected. Crashlytics is operated by Google and processes crash data under Google's privacy policy; you can read Firebase's data practices at firebase.google.com/support/privacy.

Camera recognition (Google ML Kit)

The QR Code, Big Smile, Make This Face and Dance Party missions use Google's ML Kit, a library that runs on your device, to find a barcode, a face or a pose in the camera picture. The recognition happens on your phone, and no camera image ever leaves it. Google states that the ML Kit library reports technical diagnostics about itself to Google: your device model, OS version and available hardware acceleration, the app's package name and version, a per-installation identifier that is not meant to identify you, and timings, settings, event types and error codes for the recognition it ran. This is sent encrypted, is not passed on by Google to third parties, and is not something the app can switch off. ML Kit receives no alarms, no wake history and nothing you typed. Google describes this collection at developers.google.com/ml-kit/android-data-disclosure.

Purchases and Google Play

Alarm Clock: Heavy Sleepers Premium is an optional paid upgrade. Purchases are processed entirely by Google Play; the app receives only confirmation that your purchase is active, so it can unlock premium features and restore them after a reinstall. We never see your payment details, and your alarm data is never involved in a purchase. Once your wake-up streak reaches a milestone, the app may also ask Google Play to show its standard rating prompt; that prompt belongs to Google Play, runs under Google's policies, and the app never learns what you answer.

Backups, exporting and sharing

• Android's own backup: your alarms (only your alarms, not your streaks or purchase state) are included in Android's standard device backup to your Google account, controlled by your device's backup settings, so a new phone restores your alarms.
• Export and import: you can export your alarms to a file and share or restore it. This happens only when you start it, and the file goes wherever you choose to send it.
• "My alarm didn't ring" report: if an alarm fails, you can choose to send us a diagnostic report through your device's share sheet. The report contains the app version, your phone's manufacturer and OS version, the status of each permission the app needs, the alarm's time and recent ring history, the app's reliability score and any note you add; you see the text before sending, and nothing is sent unless you send it.

Deleting your data

Everything is local, so you have direct control:

• Delete any alarm, deck, sound, or history entry within the app.
• Clear the app's storage in system settings to wipe everything.
• Uninstalling the app also removes all of its local data.

We hold no copy of your app data, so there is nothing to delete on our side. If you have emailed us a "didn't ring" report, we keep that email only to help you and delete it on request. Crash reports already sent to Google are kept under Firebase's retention policies and deleted automatically after a fixed period; to ask for deletion sooner, contact us. ML Kit's diagnostics are held by Google under its own privacy policy.

Children's privacy

Alarm Clock: Heavy Sleepers is not directed at children under 13 and does not knowingly collect data from them.