Privacy Policy — Kalorie

Last updated: 14 August 2026

Kalorie (“the app”) is developed by Almas Apps LLC (“we”, “us”). This policy explains what the app does and does not do with your information. In short: the app does not collect, transmit, or share any personal data. It is designed to work entirely offline.

Information we collect

None. The app has no user accounts, no sign-in, no analytics of our own, and no tracking. It contains no advertising SDK and displays no ads.

One third-party library in the app can collect, and it cannot transmit — so we state it rather than round it down. Selling the optional paid features requires Google’s Play Billing library, and every published version of it brings Google’s own diagnostics transport (transport-backend-cct) along with it. That transport asks for the Internet permission at build time and this app refuses it — the build’s manifest-merger report records the request as REJECTED — so it has no socket to send anything through, whatever it gathers. This is the reason the app’s own promise card says “nothing in it can transmit” rather than “there is no such library in it”: the second sentence stopped being true when the app became able to charge for anything, and the first one is both stronger and checkable.

If advertising is ever introduced, this page and the app’s Play Data safety declaration will be updated in or before the release that introduces it — not afterwards. An ad network would require the Internet permission the app currently removes, so it is not a change that could happen quietly.

Your food diary and health information

Everything you enter — logged meals, calorie and macro targets, body-related settings, custom foods, and favorites — is stored only on your device, in the app’s private storage. We never see it. It is not backed up to our servers, because we do not operate any servers. The food database itself ships inside the app, so searching for a food never leaves your phone.

Android’s own automatic backup is switched off for this app, on purpose. Android can normally copy an app’s private data to the owner’s Google Drive, and can copy it to a new handset during a phone-to-phone transfer — both without the app being involved and without asking it. For a diary of what you eat and what you weigh, that is a copy leaving your device by a route we neither control nor can see, so the app declines it: it sets allowBackup="false" and excludes every data domain from both cloud backup and device transfer.

The consequence is worth stating plainly, because it is a real cost and it falls on you: replacing or wiping your phone loses your history unless you have exported a backup file yourself. The app’s own backup — below — is the way to carry it across, it is free, and it can run automatically into a folder you choose.

No Internet access

This is enforced technically, not just promised: the app does not request the Internet permission (it is explicitly removed from the app’s manifest via tools:node="remove"). Android will not allow the app to open a network connection, so your data physically cannot be sent anywhere.

Permissions we request

Five. None of them is Internet, storage or location. This section said “none” until 9 August 2026 and “three” until 14 August 2026; each figure stopped being true when a feature was added — barcode scanning and the fasting alert first, then the two that came with selling the paid features — and each is corrected here rather than left to age.

• Camera — for scanning a barcode, and requested only when you tap the scanner. Frames are analysed on your device and are never stored or transmitted. With no Internet permission they physically cannot be sent anywhere. Refuse it and the whole app works except the scanner.
• Notifications — requested only if you switch on the alert that tells you a fast has reached the time you set. It fires once per fast and says nothing else. Refuse it and fasts still record normally.
• Run at startup — so that a fast which was running when you restarted your phone still gets its one alert. There is no prompt for this one and nothing to grant or refuse. It reads two values from the app’s own settings, re-books a single alarm, and does nothing else: it opens no database, starts no service, and collects nothing.
• Billing — lets the app ask the Google Play Store app, on the same phone, whether you own the optional paid features. It is not a network permission: it talks to another app on your device, and Play does the rest under its own policy. There is no prompt for this one.
• Network state — comes with Google’s billing library, which the app cannot sell anything without. It allows reading whether a connection exists; it does not allow using one, and this app has no permission to use one. There is no prompt for this one either.

You can verify this list yourself against the installed app in Android’s Settings, or against the published package with aapt2 dump permissions. One caveat worth stating, because we found it ourselves: an app installed from Play also carries com.android.vending.CHECK_LICENSE, which Google adds during distribution and which appears in no file we build. It lets Play confirm the app was obtained legitimately. So a phone may show six where our own package shows five, and neither number is Internet.

Backups and exports — the only way data leaves

The app can write two kinds of file: a backup containing everything (diary, your own foods, notes, weigh-ins, water, fasts and settings), and CSV exports of your diary, daily totals and custom foods. It can also render a day as a shareable image or a stats report as a PDF.

Every one of these is written through Android’s own file picker to a location you choose, and the app never learns where that is. If you pick a cloud folder, the app for that service does the uploading, in its own process and under its own permissions and privacy policy — this app cannot, having no network access. If you turn on automatic backups, the app writes to the one folder you picked, on your device, on the same terms.

Once a file leaves the app this way it is yours to manage, and what happens to it afterwards is outside our control and this policy.

Purchases

The app offers optional paid features. Any purchase is processed entirely by Google Play, which is the seller and the payment processor. We never see or receive your card details, billing address or any other payment information — Google tells the app only whether this Google account owns the purchase, and that answer is stored on your device like everything else. There is still no account to create with us and nothing to sign in to.

The terms that govern a purchase are in the Terms of Service.

Deleting your data

You can delete individual entries and custom foods inside the app. To remove everything at once, use Settings → Danger zone, which deletes all of your data from the device. Android’s “Clear storage” and uninstalling the app both do the same thing. Because we hold no copy of your data, there is nothing for you to request deletion of from us — and nothing we could delete on your behalf if you asked.

Google Play

The app is distributed through Google Play. Google may collect its own information about app installs and, if you have opted in on your device, crash and diagnostic reports. That collection is governed by Google’s Privacy Policy, not by us, and we do not receive your personal data from it.

Children

The app is intended for adults and is not directed at children. It does not knowingly collect information from anyone, including children — it does not collect information at all.

Changes to this policy

If this policy changes, we will update this page and the “Last updated” date above.

Contact

Questions about this policy? Email us at almasappsllc@gmail.com.