Back to Calorya

Calorya Privacy Policy

The short version: everything stays on your iPhone.

Effective: 2026-05-11
App: Calorya (com.calorya.app)
Publisher: QnSub Tech
Contact: support-calorya@qnsub.com

This is a plain-English explanation of what Calorya does with your data. The short version: everything stays on your iPhone. QnSub Tech does not run a server, does not have an account system, and does not ship analytics or advertising SDKs.

What Calorya stores

All of the following is stored locally on your device using Apple's SwiftData framework:

  • Profile — your goal, gender, birthday, height, weight, activity level, pace preference, and current daily calorie target.
  • Food and meals — the meals you log and the foods that appear in the picker (a seed list of common dishes plus anything you add).
  • Weight entries — manual weight logs and any reading we OCR from a scale photo (the photo itself is discarded after analysis).
  • Workouts — any workout you log (preset, custom, walk-to-place, or live-tracked).
  • Saved walks — places you've saved to walk to later, with the coordinates needed to reopen them in Apple Maps.
  • Accountability partner — if you set one up: email, optional name, the reward you're staking, the goal magnitude and deadline.
  • App preferences — small flags like your preferred display units, stored in iOS UserDefaults.

Apple Health (HealthKit)

Calorya can optionally read steps, workouts, sleep, and weight from Apple Health to calculate your daily calorie balance, and can optionally write weight entries back to Apple Health so it remains your single source of truth.

  • Permission is requested explicitly during onboarding and can be revoked at any time in iOS Settings → Privacy → Health → Calorya.
  • HealthKit data is never sent off your device by Calorya.
  • HealthKit data is never used for advertising or sold.

Camera

Calorya uses the camera in three places. In every case, the video stream is processed on-device by Apple's Vision framework and no frames are uploaded or retained beyond the immediate analysis:

  1. Scale photo — when you tap "Log weight" the app captures a still of the scale display, reads the number with on-device OCR, and stores only the resulting kilograms value. The photo is discarded.
  2. Meal photo (optional) — if you attach a photo to a custom meal log, it is stored locally as a compressed JPEG attached to the meal row. You can delete the meal at any time.
  3. Live workout tracking — when you start a session in "Track with camera", the live video is run through Apple's body-pose detection in memory only. Nothing is recorded.

Location

Calorya uses your approximate location (CoreLocation, "When in use") only to suggest nearby walking destinations (parks, malls, cafes, tracks). Your location is sent to Apple Maps' MKLocalSearch and MKDirections to compute nearby places and round-trip distances — Apple Maps' privacy policy applies to that step. Your location is never sent to a Calorya server (there isn't one), or stored beyond a short cache used to avoid repeating the search every time you open the screen.

Photos library

You can pick existing photos from your library for custom meal entries. We only read the photos you pick, and only the picked images are imported into the app.

Sponsored placements

Calorya shows one rotating sponsored slot on the home screen. Slots are paid by partners directly (not via your iPhone). When you see a sponsor:

  • It is clearly labelled SPONSORED.
  • Tapping it opens the partner's website (Safari) or App Store listing.
  • Calorya does not share any of your data with the sponsor.
  • Calorya does not track whether you tapped, by user — the app never sends user-level data to any server.
  • The sponsor cannot see your weight, meals, workouts, or any other in-app data.

The sponsor list is fetched as a static JSON file from sponsors.calorya.app. The only data sent in that request is what every HTTPS request includes (your IP and a generic User-Agent). The request does not carry an account, device ID, or any identifier we control.

What we do not do

  • We do not track you across apps or websites.
  • We do not use analytics SDKs (no Google Analytics, no Mixpanel, no Firebase, no Amplitude, etc.).
  • We do not use advertising SDKs or have any third-party SDKs that collect data.
  • We do not sell or share your data with anyone.
  • We do not have a server collecting your data.
  • We do not require you to create an account.

Sharing your data, on purpose

The only time data leaves your device is when you initiate it:

  • Accountability partner updates — if you enable sending in the partner setup, tapping "Send today's update" composes a message and hands it to iOS's share sheet. Whatever you do with it (iMessage, Mail, WhatsApp) is governed by that app's privacy policy. Calorya doesn't transmit anything itself.
  • Apple Health write-back — if you grant permission, Calorya writes new weight entries to Apple Health. Apple's HealthKit is the data store; we just write.

Deleting your data

Because everything is local, uninstalling Calorya deletes everything. iOS will remove the app's data container along with the app. There is nothing on a server to delete.

You can also reset individual things from inside the app:

  • Profile → Log weight (any time, overwrites your current weight entry)
  • Profile → re-edit onboarding (overwrites profile fields)
  • Home → swipe-delete on any meal or workout row

Children

Calorya is not directed to children under 13. Calorie tracking and weight goals are not appropriate for children without professional supervision.

Changes to this policy

If the privacy practices change, we'll update this page and the in-app About screen with the new effective date. Material changes (e.g., adding a backend) will be highlighted at the top.

Contact

Questions or requests: support-calorya@qnsub.com